News
SpaceX's in-flight rocket engine failure threatens NASA astronaut launch debut
An in-flight rocket engine failure during SpaceX’s March 18th Starlink launch could pose a threat to the company’s imminent NASA astronaut launch debut according to a statement provided by the space agency yesterday.
SpaceX and NASA are currently working around the clock to prepare a Falcon 9 rocket and Crew Dragon spacecraft for the company’s inaugural astronaut launch, a flight known as Demonstration Mission 2 (Demo-2/DM-2). All launch vehicle and spacecraft hardware – including booster B1058, an expendable upper stage, a spacecraft trunk, and the Crew Dragon capsule itself – are already believed to be at SpaceX’s Florida launch and processing facilities.
Prior to March 18th, the biggest gating items were believed to be a few final parachute tests and a whole lot of paperwork and reviews, as well as some important but less showstopping astronaut training. Unfortunately, SpaceX has suffered two unforeseen issues of varying severity in the last few days, both of which are now all but guaranteed to impact Crew Dragon’s astronaut launch debut schedule.
“According to the CCtCap contracts, SpaceX is required to make available to NASA all data and resulting reports. SpaceX, with NASA’s concurrence, would need to implement any corrective actions found during the investigation related to its commercial crew work prior to its flight test with astronauts to the International Space Station. NASA and SpaceX are holding the current mid-to-late May launch timeframe, and would adjust the date based on review of the data, if appropriate.”
NASA — March 25th, 2020
On March 18th, less than three minutes after liftoff and shortly before stage separation was scheduled, Falcon 9 booster B1048 – on its historic fifth launch attempt – suffered an engine failure visible on SpaceX’s official webcast. By all appearances, Falcon 9’s autonomous flight computer accounted for the engine’s failure, shutdown, and the resultant loss of thrust by burning B1048’s eight remaining engines for several seconds longer than planned.
While that extra few seconds of burn time likely ensured that the rocket’s upper stage was able to make it to the correct orbit after stage separation, roughly five minutes after B1048’s extremely rapid engine failure, contact was lost. For the first time ever, there were no landing burn-related call-outs from SpaceX launch operators, the first sign that something was seriously wrong. A few minutes later, SpaceX’s webcast hosts acknowledged that the booster had been lost, perhaps lacking the propellant it needed to attempt a landing.
For reference, Merlin 1D engines likely consume some ~270 kg (600 lb) of fuel each second. Falcon 9’s landing propellant reserves are believed to be on the order of 50+ metric tons (110,000 lb). Excluding the failed engine, eight Merlin 1Ds burning at full thrust for an additional 5 seconds would consume 20% of the propellant needed for landing; 10 seconds and it would use 40%.
The anomaly was Merlin 1D engine’s first in-flight failure ever. The 2012 failure of one of an original Falcon 9 V1.0’s rocket’s nine Merlin 1C engines is SpaceX’s only other in-flight failure.
It’s likely that B1048’s engine failure was primarily related to the fact that the booster was SpaceX’s pathfinder for a fifth-flight reusability milestone, making it the most reused rocket booster ever launched. NASA currently requires all of its Crew Dragon missions to launch on new Falcon 9 rockets, hopefully mitigating direct corollaries between the Starlink L6 anomaly and astronaut launches. Regardless, the space agency says that the company will now have to complete its internal failure review and implement necessary hardware, software, or rule changes before it’s allowed to launch NASA astronauts.
That investigation could take a matter of weeks, possibly even less, but it’s entirely possible that it could take months – let alone fixing the problems that allowed the in-flight Merlin 1D engine failure to happen in the first place. Ultimately, it will almost certainly make even the first flights of Falcon 9 and Heavy rocket boosters safer, but it could substantially delay SpaceX’s Demo-2 astronaut launch debut. Still targeted no earlier than (NET) mid-to-late May 2020, it’s safe to say that it’s reasonable to expect that schedule to slip over the next 4-6 weeks. Stay tuned for updates.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
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 crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
