Connect with us

News

SpaceX Starship static fire success sets rocket up for hop debut

After weeks of unfortunate delays, Starship SN5 has finally completed a Raptor engine static fire, setting it up for a hop debut just a few days from now. (LabPadre)

Published

on

At long last, SpaceX’s fifth Starship prototype has successfully ignited its lone Raptor engine in a test known as a static fire, paving the way for the first flight of a full-scale Starship as early as this weekend.

After almost three weeks of delays and several aborted attempts, SpaceX managed to fix a variety of relatively minor hardware bugs described by CEO Elon Musk on July 28th. The first static fire attempt was originally scheduled as early as July 10th and wound up gradually slipping a few days at a time to July 25th. Thus began another series of delays after static fire attempts – with varying progress from each – were aborted on July 25th, 27th (x2), and the morning of the 30th.

Thankfully, though those aborts and scrubs and delays have finally come to an end – at least for the moment. If things go according to plan over the next several days and teams are able to rectify a critical issue discovered earlier this week, Starship SN5 could become the first full-scale of its kind to lift off (intentionally) just a few days from now.

Elon Musk released this unique photo of Starship SN5’s first static fire – apparently taken by drone – shortly after the test wrapped up. (SpaceX/Elon Musk)

Prior to Starship SN5’s successful July 30th static fire, Musk revealed in a tweet that the rocket’s second attempt was aborted on July 27th after Hurricane Hanna damaged a connector, presumably related to telemetry and control. SpaceX fixed the issue and managed to stretch its test window by a few hours, allowing for a second attempt later that night.

Unfortunately, Starship’s static fire was scrubbed again by what Musk later described as a crucial fuel valve that failed to open, as well as “some odd [behavior]” observed in a pump related to the Raptor engine’s steering hardware. To complete the static fire as SpaceX later would two days later, the finicky “fuel spin pump” would have to have been fully fixed, but Raptor’s thrust vector control (TVC) pump issues could have plausibly been put off.

Advertisement

Given that SpaceX spent approximately 2.5 days inspecting and repairing Starship after the third static fire abort, it’s likely that they had time to fix whatever bugs were plaguing Raptor’s TVC hydraulic system. Regardless, Raptor’s TVC will need to be operating flawlessly before SpaceX goes ahead with the first full-scale Starship flight test. The 150m (~500 ft) hop will be the first time a Starship prototype roughly the same size – and built out of the same materials – as an orbital-class ship will attempt controlled flight.

Prior to July 30th’s static fire, SpaceX had already filed a few temporary flight restrictions (TFRs) – used to warn aviators of keep-out zones – with the FAA for hop test attempts on August 2nd and 3rd. SpaceX will likely need 12-24 hours to analyze the data, inspect Starship, and determine a timeline for the first hop attempt, but there is at least a slight chance that the company will push for Starship SN5 to fly as early as this Sunday. Stay tuned as things play out and the hop test gets a more concrete date.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Advertisement

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla has to fix a big problem with its old headlights, NHTSA says

Published

on

tesla model 3 first generation headlight
Credit: Tesla Asia/Twitter

Tesla had a petition protesting a recall to fix a potential issue with 2017-2023 Model Y and Model 3 vehicles’ headlights was denied, as the National Highway Traffic Safety Administration (NHTSA) disagreed with the company’s opinion of things.

The recall covers approximately 19,917 Model Y and Model 3 vehicles built from 2017 to 2023. Tesla initially submitted a noncompliance report for the headlights on these vehicles on March 15, 2024. Tesla then petitioned for an exemption from the fix, which violated FMVSS No. 108 (40 CFR 571.108), arguing that the “noncompliance is inconsequential as it relates to motor vehicle safety.

The NHTSA disagreed, stating that Tesla’s conclusion that the headlights do not increase any risk was not an opinion it shared. The agency said it disagreed with Tesla’s assumption that glare is not increased to surrounding traffic. This issue could be highlighted even more in certain weather conditions.

Tesla will be required to remedy the issue, the NHTSA ruled:

“In consideration of the foregoing, NHTSA has decided that Tesla has not met its burden of persuasion that the subject FMVSS No. 108 noncompliance is inconsequential to motor vehicle safety. Accordingly, Tesla’s petition is hereby denied, and Tesla is consequently obligated to provide notification of and free remedy for that noncompliance under 49 U.S.C. 30118 and 30120.”

The issue here appears to be the angle of the headlights and the brightness they emit during operation. The NHTSA report states that:

“Tesla’s headlamp supplier, Marelli Automotive Lighting, tested 25 right-hand and 25 left-hand lamps, and for this sample, found the maximum photometric intensity measured in the 10°U to 90°U and 90°L to 90°R zone was between 136.2 cd and 230.1 cd for the right-hand lamps and between 117.5 cd and 160.3 cd for the left-hand lamps. According to Tesla, these tests revealed that the photometric intensity of the right-hand and left-hand headlamp lower beam on the subject vehicles may measure as much as 230.1 cd in the 10°U to 90°U and 90°L to 90°R zone, exceeding the maximum photometric intensity by 105.1 cd. Additionally, Tesla states that a left-hand lamp tested by a Transport Canada recognized laboratory measured a maximum of 171.27 cd in the 10°U to 90°U and 90°L to 90°R zone. Despite these measurements exceeding the allowed photometric maximum of 125 cd, Tesla believes that the subject noncompliance is inconsequential to motor vehicle safety.”

Tesla also argued at some points that the headlights had not been deemed responsible for any complaints, accidents, or injuries related to the noncompliance.

Continue Reading

Lifestyle

NTSB findings on fatal Tesla crash tell a very different story

The NTSB confirmed the driver, not Tesla’s FSD, caused the fatal Texas house crash.

Published

on

By

The National Transportation Safety Board released preliminary findings Wednesday confirming that a Tesla driver, not the vehicle’s software, caused a fatal crash in Katy, Texas in June. The driver, 44-year-old Michael Butler, had engaged Full Self-Driving Supervised mode on Rose Hollow Lane, a residential street with a 30 mph speed limit, before manually overriding the system by pressing the accelerator pedal all the way to 100%. Data recovered from the 2025 Tesla Model 3 showed the vehicle was traveling over 70 miles per hour when it struck a home and killed 76-year-old Martha Avila, who was inside. Weather was clear, the road was dry, and it was daylight.

Texas man charged in fatal Tesla crash where he blamed Autopilot

Butler told authorities he had passed out at the wheel. But security camera footage obtained by the NTSB told a different story, and showed the car accelerating through an intersection before leaving the road entirely. Police also found that Butler’s phone had Google searches including the terms “Tesla FSD not aggressive enough 2026” and “Tesla FSD too timid,” raising serious questions about how he was using the system before the crash. Butler has since been charged with manslaughter. The victim’s family has filed a lawsuit against both Butler and Tesla, alleging negligence.

The NTSB findings aligned directly with what Tesla VP of AI Software Ashok Elluswamy had already stated publicly on X in the weeks after the crash, writing that “the driver manually overrode self-driving by pressing the accelerator all the way to 100%.” The data confirmed his account.

Continue Reading

Investor's Corner

Lucid CEO dispels any rumors of bankruptcy: ‘So far from the facts’

Published

on

Credit: Lucid

Lucid CEO Silvio Napoli responded to rumors of an imminent bankruptcy that was reportedly being mulled after a report stated the automaker was working with the firm AlixPartners to iron out its next steps.

The company felt a massive loss on Wall Street yesterday, as the report essentially pushed the stock down as much as 55 percent on Tuesday.

The report, published initially by Eletric-Vehicles.com, claimed Lucid was essentially in dire straits and was told by AlixPartners, a commonly used restructuring advisor, to either take shares private or file for Chapter 11 bankruptcy protection.

Lucid denies rumors of bankruptcy after over 40% stock drop

Lucid’s head of Communications, Nick Twork, immediately challenged the report and stated the company “has sufficient liquidity to carry its operations well into next year.”

Now, the company’s CEO is chiming in as well, stating that the report is “so far from the facts that they require a direct response.”

Napoli said:

“Lucid is not considering bankruptcy or a transaction to take the company private. Those reports are false. The Board did not explore either scenario. Period.

As disclosed in our most recent quarterly filing, Lucid has sufficient liquidity to fund its operations well into next year.

We work with outside advisors to improve operational performance and execution. They are not advising Lucid on a take-private transaction or bankruptcy, and any suggestion that they have recommended either course of action to management or the Board is false.

My priority is clear: turn this company around. That is where the leadership team and I are focused.

I look forward to providing a full update during our quarterly earnings call on August 4th.”

It seems pretty clear that Lucid is confident things will be okay, and, to be honest, they should not have much to worry about, especially considering the company has been backed by the Saudi Public Investment Fund (PIF) for years. It has solid financial backing, and its sales, while weak, are pretty much right on par with a company of this age.

Lucid also sent a Cease & Desist letter to the publication for their report.

Lucid shares have rebounded nicely and are up nearly 21 percent at the time of publication. As soon as the company dispelled the rumors of bankruptcy yesterday, the stock began to climb back toward more reasonable levels.

Continue Reading