News
SpaceX loses record-breaking rocket booster after sixth successful Starlink launch
SpaceX has suffered its second rocket landing failure of 2020 despite the fact that both lost Falcon 9 boosters successfully launched 60 Starlink satellites, an anomaly that CEO Elon Musk says will need a “thorough investigation”.
After a rare last-second launch abort on March 15th and a three-day range-related delay, Falcon 9 booster B1048 lifted off with 60 upgraded Starlink v1.0 satellites on its fifth orbital-class mission. At least for the first two and half minutes, the booster performed precisely as intended, carrying a fueled upper stage and its ~16 metric ton (36,000 lb) payload to an altitude of 55 km (34 mi) and a velocity of 1.8 km/s (1.1 mi/s). However, about 10 seconds before the booster reached main engine cut-off (MECO) and stage separation, something went wrong.
While there is some ambiguity in his response, according to Musk, at least one of Falcon 9 B1048’s nine Merlin 1D engines performed an early shutdown before MECO. The rocket’s computer immediately accounted for the anomaly, extending the remaining eight-engine booster burn 5-7 seconds beyond the nominal timeline to ensure mission success. While the booster’s loss is still disappointing and the premature engine shutdown more than a little concerning, it’s critical to remember that mission success was ensured. Just 15 minutes after liftoff, the rocket’s upper stage successfully spun up and deployed another 60 Starlink satellites, bringing SpaceX’s operational constellation to an incredible ~350 satellites.
Based on live views available from SpaceX’s launch webcast, it appears that Falcon 9’s “early engine shutdown” is more of a euphemism for a fairly violent engine failure that triggered an instantaneous cutoff, preventing damage elsewhere. While SpaceX would certainly rather avoid in-flight engine failures, Falcon 9’s nine Merlin 1D booster engines are installed inside an aluminum ‘octaweb’ structure that transmits their thrust to the rest of the rocket but also effectively quarantines each engine in a blast-proof bunker.
Nevertheless, the rocket’s highly-attuned software and affected octaweb engine bunker did their jobs, instantly shutting the failing engine down while also preventing the explosion and resulting shrapnel from damaging the rest of the rocket. More likely than not, B1048’s autonomous decision to always put mission success before booster recovery lead the booster to expend a majority of the propellant needed for its landing attempt to make up for the 10 or so seconds operating at only ~89% thrust.
As a result, B1048 may have simultaneous subjected itself to a much more extreme atmospheric reentry and run out of propellant before it could complete (or maybe even start) its drone ship landing burn. There’s also a chance that the engine that failed was one of the three engines required for reentry and landing burns, an asymmetry that would be impossible to overcome on the fly. Ultimately, the booster likely impacted the ocean at a near-supersonic velocity, smashing it into aluminum confetti. Thankfully, the late B1048 had a record-breakingly productive career as an orbital-class booster, placing dozens of tons of payload into orbit over five successful launches. Its loss is regrettable but the booster has more than earned its keep.
Aside from two twice-flown Falcon Heavy Block 5 side boosters of unknown status and 2-3 new boosters assigned to critical NASA and US Air Force missions, SpaceX’s fleet is now down to just three flightworthy Falcon 9 boosters. This could dramatically limit its options for near-term commercial flights, as none of those rockets – even assuming flawless launch and landing debuts – will likely be ready for their first reuses until May or June. Meanwhile, B1051 and B1049 have three and four missions under their respective belt and both completed their last launches just 50-70 days ago, while B1059 flew for the second time just two weeks ago. Despite the fact that it successfully completed its fifth mission, B1048’s in-flight engine failure will almost certainly delay upcoming launches, although the degree of those delays is up for debate.
Up next for SpaceX is SAOCOM 1B, an Argentinian radar satellite set to become the first payload launched into a polar orbit from the US East Coast in half a century. Before B1048’s anomaly, the mission was scheduled to launch no earlier than March 30th and could use any of unassigned boosters described above
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
