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 Robotaxi ride-hailing without a Safety Monitor is proving to be a difficult task, according to some riders who made the journey to Austin to attempt to ride in one of its vehicles that has zero supervision.
Last week, Tesla officially removed Safety Monitors from some — not all — of its Robotaxi vehicles in Austin, Texas, answering skeptics who said the vehicles still needed supervision to operate safely and efficiently.
BREAKING: Tesla launches public Robotaxi rides in Austin with no Safety Monitor
Tesla aimed to remove Safety Monitors before the end of 2025, and it did, but only to company employees. It made the move last week to open the rides to the public, just a couple of weeks late to its original goal, but the accomplishment was impressive, nonetheless.
However, the small number of Robotaxis that are operating without Safety Monitors has proven difficult to hail for a ride. David Moss, who has gained notoriety recently as the person who has traveled over 10,000 miles in his Tesla on Full Self-Driving v14 without any interventions, made it to Austin last week.
He has tried to get a ride in a Safety Monitor-less Robotaxi for the better part of four days, and after 38 attempts, he still has yet to grab one:
Wow just wow!
It’s 8:30PM, 29° out ice storm hailing & Tesla Robotaxi service has turned back on!
Waymo is offline & vast majority of humans are home in the storm
Ride 38 was still supervised but by far most impressive yet pic.twitter.com/1aUnJkcYm8
— David Moss (@DavidMoss) January 25, 2026
Tesla said last week that it was rolling out a controlled test of the Safety Monitor-less Robotaxis. Ashok Elluswamy, who heads the AI program at Tesla, confirmed that the company was “starting with a few unsupervised vehicles mixed in with the broader Robotaxi fleet with Safety Monitors,” and that “the ratio will increase over time.”
This is a good strategy that prioritizes safety and keeps the company’s controlled rollout at the forefront of the Robotaxi rollout.
However, it will be interesting to see how quickly the company can scale these completely monitor-less rides. It has proven to be extremely difficult to get one, but that is understandable considering only a handful of the cars in the entire Austin fleet are operating with no supervision within the vehicle.
Tesla has given its biggest hint that Full Self-Driving in Europe is imminent, as a new feature seems to show that the company is preparing for frequent border crossings.
Tesla owner and influencer BLKMDL3, also known as Zack, recently took his Tesla to the border of California and Mexico at Tijuana, and at the international crossing, Full Self-Driving showed an interesting message: “Upcoming country border — FSD (Supervised) will become unavailable.”
FSD now shows a new message when approaching an international border crossing.
Stayed engaged the whole way as we crossed the border and worked great in Mexico! pic.twitter.com/bDzyLnyq0g
— Zack (@BLKMDL3) January 26, 2026
Due to regulatory approvals, once a Tesla operating on Full Self-Driving enters a new country, it is required to comply with the laws and regulations that are applicable to that territory. Even if legal, it seems Tesla will shut off FSD temporarily, confirming it is in a location where operation is approved.
This is something that will be extremely important in Europe, as crossing borders there is like crossing states in the U.S.; it’s pretty frequent compared to life in America, Canada, and Mexico.
Tesla has been working to get FSD approved in Europe for several years, and it has been getting close to being able to offer it to owners on the continent. However, it is still working through a lot of the red tape that is necessary for European regulators to approve use of the system on their continent.
This feature seems to be one that would be extremely useful in Europe, considering the fact that crossing borders into other countries is much more frequent than here in the U.S., and would cater to an area where approvals would differ.
Tesla has been testing FSD in Spain, France, England, and other European countries, and plans to continue expanding this effort. European owners have been fighting for a very long time to utilize the functionality, but the red tape has been the biggest bottleneck in the process.
Tesla Europe builds momentum with expanding FSD demos and regional launches
Tesla operates Full Self-Driving in the United States, China, Canada, Mexico, Puerto Rico, Australia, New Zealand, and South Korea.
Elon Musk
SpaceX Starship V3 gets launch date update from Elon Musk
The first flight of Starship Version 3 and its new Raptor V3 engines could happen as early as March.
Elon Musk has announced that SpaceX’s next Starship launch, Flight 12, is expected in about six weeks. This suggests that the first flight of Starship Version 3 and its new Raptor V3 engines could happen as early as March.
In a post on X, Elon Musk stated that the next Starship launch is in six weeks. He accompanied his announcement with a photo that seemed to have been taken when Starship’s upper stage was just about to separate from the Super Heavy Booster. Musk did not state whether SpaceX will attempt to catch the Super Heavy Booster during the upcoming flight.
The upcoming flight will mark the debut of Starship V3. The upgraded design includes the new Raptor V3 engine, which is expected to have nearly twice the thrust of the original Raptor 1, at a fraction of the cost and with significantly reduced weight. The Starship V3 platform is also expected to be optimized for manufacturability.
The Starship V3 Flight 12 launch timeline comes as SpaceX pursues an aggressive development cadence for the fully reusable launch system. Previous iterations of Starship have racked up a mixed but notable string of test flights, including multiple integrated flight tests in 2025.
Interestingly enough, SpaceX has teased an aggressive timeframe for Starship V3’s first flight. Way back in late November, SpaceX noted on X that it will be aiming to launch Starship V3’s maiden flight in the first quarter of 2026. This was despite setbacks like a structural anomaly on the first V3 booster during ground testing.
“Starship’s twelfth flight test remains targeted for the first quarter of 2026,” the company wrote in its post on X.
Tesla Robotaxi ride-hailing without a Safety Monitor proves to be difficult
Tesla gives its biggest hint that Full Self-Driving in Europe is imminent
