News
SpaceX rocket performs first last-second launch abort in years, delaying Starlink mission
A Falcon 9 rocket has performed SpaceX’s first last-second launch abort in years, shutting down the booster’s main engines and preventing liftoff just milliseconds after ignition.
Scheduled to lift off at 9:22 am EDT (13:22 UTC) on March 15th, SpaceX will now wait until no earlier than (NET) 8:21 am EDT (12:21 UTC) on Wednesday, March 18th for the sixth 60-satellite Starlink mission’s next launch attempt. Featuring an exceptionally flight-proven Falcon 9 booster and marking the second time ever SpaceX has reused a payload fairing, yesterday’s launch abort is also unique in its own right.
Notably, shortly after the launch countdown froze and Falcon 9 shut down at T-00:00:00, a launch operator – on-console either in Florida or at SpaceX’s Hawthorne, CA headquarters – revealed that the rocket had triggered a “launch abort on engine high power”. To explain that decision, a little background on how SpaceX launches its rockets and what exactly abort conditions are is necessary.
Software has always been a central part of SpaceX’s launch vehicles, treated more like a first-class citizen in design and engineering instead of the reluctant necessity other launch providers have frequently relegated it to. For anyone that’s watched numerous SpaceX launch webcasts, some might recognize the familiar “vehicle is in startup” callout that made around T-1 minute to liftoff. Standard on most modern launch vehicles, SpaceX’s Falcon rockets use onboard computers to take over their countdowns shortly before launch.
This is mainly done to allow the vehicle to simultaneously analyze thousands of channels of telemetry far faster and more reliably than humans ever could. During today’s launch attempt, that meant that Falcon 9 saw something it didn’t like just milliseconds before it was scheduled to command the release of the pad’s hold-down clamps and lift off.
Per one of SpaceX’s on-console engineers, the specific issue Falcon 9’s computer flagged was an “engine high power” alert. Soon after, SpaceX provided an update on Twitter, stating that the abort was “triggered due to out-of-family data during [an] engine power check” – putting the blame more on the sensors and software used to determine engine thrust than the engine hardware itself. An actual hardware or software failure that caused one or several booster engines to exceed their design limits could have potentially damaged B1048’s Merlin 1Ds, likely requiring weeks of repairs or a full swap with a different booster.
Given that Falcon 9 B1048 has already performed four orbital-class launches, hardware issues would not come as a major shock, but the successful static fire test it completed on Saturday made that far less likely. SpaceX’s confirmation that it was looking at an “out-of-family” reading thankfully means that only one of several thrust sensors showed the Falcon 9 booster producing too much thrust.
With any luck, post-ignition launch aborts will continue to be extremely rare for SpaceX’s Falcon launch vehicle family. The last such abort occurred in February 2016, more than four years and several booster ‘Block’ iterations ago.
Starlink L6 (V1 L5) is now scheduled to launch on Wednesday, March 18th, giving SpaceX workers some 72 hours to inspect Falcon 9 B1048’s engines, replace thrust sensors, tweak software, and prepare for a second launch attempt. Drone ship Of Course I Still Love You (OCISLY), fairing recovery ships GO Ms. Tree and GO Ms. Chief, and another support vessel or two remain on station in the Atlantic Ocean and will have to wait a bit longer for their next rocket recovery attempts.
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
