Connect with us

News

SpaceX Starship engine test aborted twice in one day by hurricane damage and bugs

Starship SN5 was forced to abort a planned Raptor engine test twice in one day. (NASASpaceflight - bocachicagal)

Published

on

SpaceX has been unable to catch a break in the last few weeks and CEO Elon Musk says that a Starship Raptor engine test was delayed twice in one day by minor hardware bugs and damage caused by Hurricane Hanna.

Although it quickly devolved into a tropical storm and largely missed the southernmost tip of Texas, where SpaceX has built its Starship factory and test facilities, Hanna caused significant damage just a few dozen miles to the north. Above all else, the flooding caused by Hanna has by far been the worst part of the storm. Boca Chica managed to dodge the bulk of that element but was still hit by heavy rain that lasted for a day or two, drenching everything that wasn’t covered and nearly flooding the only access road.

According to Musk, an unspecified “connector” related to Starship SN5 or the pad supporting it was damaged by Hanna’s glancing encounter with SpaceX’s facilities. The connector was ultimately fixed around 7-8 pm CDT per unofficial webcasts showing technicians working around the rocket after they returned to the pad, but SpaceX’s test window technically closed at 8 pm CDT (01:00 UTC).

Nevertheless, SpaceX must have been able to work with local sheriffs to extend that road closure into the night, and – as promised by CEO Elon Musk – testing restarted around 9:30 pm CDT. About an hour and a half later, Starship SN5 appeared to make it all the way through a partial wet dress rehearsal before its Raptor engine test fire was aborted a second time. Based on four static fires completed by Starship SN4 in May 2020, the rocket could have been just a few minutes away from ignition.

Advertisement

According to Musk, Starship SN5’s fuel (methane) “spin valve” – presumably a valve that opens to allow methane gas to spin up Raptor’s fuel turbopump – failed to open when it was supposed to. To ensure Raptor’s health after three inactive weeks spent installed on Starship out in the elements, SpaceX likely planned what is known as a “spin prime” test directly prior to the static fire. If Raptor successfully spun up its turbopumps, SpaceX would proceed directly into static fire operations without having to detank Starship.

During SN5’s second July 27th static fire attempt, Raptor was unable to start that spin prime test, forcing SpaceX to stand down to diagnose and fix the problem. Musk says that SpaceX will attempt to static fire Starship SN5 again tomorrow (July 28th) – assuming the issue can be quickly rectified.

Raptor SN27 was installed on Starship SN5 around July 3rd or 4th. (NASASpaceflight – bocachicagal)
Starship SN5 was forced to wait several weeks after its first cryogenic proof test to begin more challenging tests with a Raptor engine and real methane/oxygen propellant. (NASASpaceflight – bocachicagal)

Musk further noted that some “odd…behavior” was observed in the hydraulic pump powering Raptor SN27’s thrust vector control (TVC). Used to steer a rocket engine, Raptor doesn’t technically need functioning TVC to perform a static fire test on the ground, but it’s an issue that will have to be completely fixed before Starship SN5 is allowed to attempt its first flight test. If July 28th finally sees SN5 successfully ignite its Raptor engine, there’s a chance – however slim – that SpaceX will be able to turn the Starship around for its first hop just a few days later.

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

Elon Musk

Tesla Semi’s official battery capacity leaked by California regulators

A California regulatory filing just confirmed the exact battery size inside each Tesla Semi variant.

Published

on

By

A regulatory filing published by the California Air Resources Board in April 2026 has put official numbers on what Tesla Semi owners and fleet buyers have long wanted confirmed: the exact battery capacities of both the Long Range and Standard Range Semi truck variants. CARB is California’s independent air quality regulator, and it certifies zero-emission powertrains before they can be sold or operated in the state. When a manufacturer submits a vehicle for certification, the resulting executive order becomes a public document, making it one of the most reliable sources for confirmed production specs on any EV.

The document lists two certified powertrain configurations. The Long Range Semi carries a usable battery capacity of 822 kWh, while the Standard Range version comes in at 548 kWh. Both use lithium-ion NCMA chemistry and share the same peak and steady-state motor output ratings of 800 kW and 525 kW respectively. Cross-referencing Tesla’s published efficiency figure of approximately 1.7 kWh per mile under full load, the 822 kWh pack supports roughly 480 miles of real-world range, which aligns closely with Tesla’s advertised 500-mile figure for the Long Range trim. The 548 kWh Standard Range pack works out to approximately 320 miles, again consistent with Tesla’s stated 325-mile target.

Here is a direct comparison of the two versions based on the CARB filing and published specs:

Tesla Semi Spec Long Range Standard Range
Battery Capacity 822 kWh 548 kWh
Battery Chemistry NCMA Li-Ion NCMA Li-Ion
Peak Motor Power 800 kW 525 kW
Estimated Range ~500 miles ~325 miles
Efficiency ~1.7 kWh/mile ~1.7 kWh/mile
Est. Price ~$290,000 ~$260,000
GVW Rating 82,000 lbs 82,000 lbs

The timing of this certification is not incidental. On April 29, 2026, Semi Programme Director Dan Priestley confirmed on X that high-volume production is now ramping at Tesla’s dedicated 1.7-million-square-foot facility in Sparks, Nevada. A key advantage of the Nevada location is vertical integration: the 4680 battery cells powering the Semi are manufactured in the same complex, eliminating the supply chain bottleneck that had delayed the program for years.

Tesla’s long-term goal is to reach a production capacity of 50,000 trucks annually at the Nevada factory, which would represent roughly 20 percent of the entire North American Class 8 market. With CARB certification now in hand and the production line running, the regulatory and manufacturing groundwork for that target is in place.

Continue Reading

News

Tesla crushes NHTSA’s brand-new ADAS safety tests – first vehicle to ever pass

Published

on

Credit: Tesla

Tesla became the first company to pass the United States government’s new Advanced Driver Assistance Systems (ADAS) testing with the Model Y, completing each of the new tests with a passing performance.

In a landmark announcement on May 7, the National Highway Traffic Safety Administration (NHTSA) declared the 2026 Tesla Model Y the first vehicle to pass its newly ADAS benchmark under the New Car Assessment Program (NCAP).

Model Y vehicles manufactured on or after November 12, 2025, met rigorous pass/fail criteria for four newly added tests—pedestrian automatic emergency braking, lane keeping assistance, blind spot warning, and blind spot intervention—while also satisfying the program’s original four ADAS requirements: forward collision warning, crash imminent braking, dynamic brake support, and lane departure warning.

NHTSA administration Jonathan Morrison hailed the achievement as a milestone:

“Today’s announcement marks a significant step forward in our efforts to provide consumers with the most comprehensive safety ratings ever. By successfully passing these new tests, the 2026 Tesla Model Y demonstrates the lifesaving potential of driver assistance technologies and sets a high bar for the industry. We hope to see many more manufacturers develop vehicles that can meet these requirements.”

The updates to NCAP, finalized in late 2024 and effective for 2026 models, reflect growing recognition that ADAS features are no longer optional luxuries but essential tools for preventing crashes.

Pedestrian automatic emergency braking, for instance, targets one of the fastest-rising causes of roadway fatalities, while blind spot intervention and lane keeping assistance address common sources of side-swipes and run-off-road incidents. By incorporating objective, performance-based evaluations rather than mere presence of the technology, NHTSA aims to give buyers clearer data on real-world effectiveness.

This milestone arrives at a pivotal moment when vehicle autonomy is transitioning from science fiction to everyday reality.

Tesla’s Full Self-Driving (FSD) software and the impending rollout of robotaxis underscore a broader industry shift toward higher levels of automation. Yet regulators and consumers remain cautious: safety data must keep pace with technological ambition.

The Model Y’s perfect score on these ADAS benchmarks validates that current driver-assist systems—when engineered rigorously—can dramatically reduce human error, which still accounts for the vast majority of crashes.

For Tesla, the result reinforces its long-standing claim of building the safest vehicles on the road. More importantly, it signals to the entire auto sector that meeting elevated federal standards is achievable and expected.

As autonomy edges closer to Level 3 and beyond, where drivers may disengage more fully, such independent verification becomes critical. It builds public trust, informs purchasing decisions, and accelerates the development of systems that could one day eliminate tens of thousands of annual traffic deaths.

In an era when software-defined vehicles promise transformative mobility, the 2026 Model Y’s NHTSA triumph is more than a manufacturer accolade—it is a regulatory green light that autonomy’s future must be built on proven, testable safety foundations. The bar has been raised. The industry, and the roads we share, will be safer for it.

Continue Reading

News

Tesla to fix 219k vehicles in recall with simple software update

Published

on

Credit: Tesla

Tesla is going to fix the nearly 219,000 vehicles that it recalled due to an issue with the rearview camera with a simple software update, giving owners no need to travel to a service center to resolve the problem.

Tesla is formally recalling 218,868 U.S. vehicles after regulators discovered a software glitch that can delay the rearview camera image by up to 11 seconds when drivers shift into reverse.

The affected models include certain 2024-2025 Model 3 and Model Y, as well as 2023-2025 Model S and Model X vehicles running software version 2026.8.6 and equipped with Hardware 3 computers. The National Highway Traffic Safety Administration (NHTSA) determined the lag violates Federal Motor Vehicle Safety Standard 111 on rear visibility and could increase crash risk.

Yet this is no ordinary recall. Owners do not need to schedule a service-center visit, hand over keys, or wait for parts.

Tesla fans call for recall terminology update, but the NHTSA isn’t convinced it’s needed

Tesla identified the issue on April 10, halted further deployment of the faulty firmware the same day, and began pushing a corrective over-the-air (OTA) software update on April 11.

By the time the NHTSA posted the recall notice on May 6, more than 99.92 percent of the affected fleet had already received the fix. Tesla reports no crashes, injuries, or fatalities linked to the glitch.

The episode underscores a deeper problem with regulatory language. For decades, “recall” meant hauling a vehicle to a dealership for hardware repairs or replacements. That definition no longer fits software-defined cars. When a fix arrives wirelessly in minutes — identical to an iPhone update — the term evokes unnecessary alarm and misleads the public about the actual risk and remedy.

Elon Musk has repeatedly called for exactly this change. After earlier NHTSA actions, he stated plainly: “The terminology is outdated & inaccurate. This is a tiny over-the-air software update.” On another occasion, he added that labeling OTA fixes as recalls is “anachronistic and just flat wrong.”

Musk’s point is simple: regulators must evolve their vocabulary to match the technology. Traditional recalls involve physical intervention and downtime; OTA updates do not. Retaining the old label distorts consumer perception, inflates perceived defect rates, and slows the industry’s shift to faster, safer software iteration.

Tesla’s rapid, remote remedy demonstrates the safety advantage of over-the-air capability. Problems that once required weeks of dealer appointments are now resolved in hours, often before most owners notice. As more automakers adopt software-first designs, the entire regulatory framework needs to catch up.

Updating “recall” terminology would align language with reality, reduce public confusion, and recognize that modern vehicles are no longer static hardware — they are continuously improving computers on wheels.

For the 219,000 Tesla owners involved, the process is already complete. The camera works, the car is safe, and no one left their driveway. That is the new standard — and the vocabulary should reflect it.

Continue Reading