News
SpaceX aborts Starship launch after Raptors produce too much thrust
Update #3: SpaceX CEO Elon Musk says that Starship prototype SN10 automatically aborted a 2:15 pm CST (UTC-6) launch attempt after the rocket determined that its three Raptor engines were producing too much thrust.
Instead of scrubbing for the day, Musk says that SpaceX will instead increase the flight computer’s thrust limits and try again as early as 4:30 pm CST – still well before today’s window closes at 6:30 pm. SpaceX ended its webcast but will start a second webcast a few minutes prior to the next launch attempt.
Update #2: As of Wednesday morning, SpaceX has officially confirmed that Starship is on track for a third high-altitude launch and ‘bellyflop‘-style landing attempt sometime later today.
As of 11am CST (UTC-6), FAA approval is in hand, weather is encouraging, Starship prototype serial number 10’s (SN10) flaps have been unchained, and SpaceX has cleared the launch site – all signs that the rocket’s launch attempt is imminent. Much like SN8 and SN9 coverage, SpaceX says it will make a public livestream of SN10’s launch available to the public “a few minutes” before liftoff. Stay tuned and follow along with NASASpaceflight’s live coverage in the meantime.
Update: SpaceX has asked Boca Chica Village residents to prepare to evacuate the area as early as Wednesday morning for Starship’s third high-altitude launch and landing attempt.
The odds of things going so wrong that a Starship launch could actually end with a prototype impacting at or near the Village and the handful of non-employee holdouts still residing there are minuscule. However, FAA safety regulations and SpaceX’s contingent launch license mean that evacuations are now a routine part of Starship’s high-altitude flight tests since Starship SN8 took the first step beyond short hops. While undeniably inconvenient for the few remaining residents, today’s evacuation notice – short of an official SpaceX.com confirmation – does serve as the ultimate sign that Starship SN10’s first launch attempt is firmly scheduled on Wednesday, March 3rd.
With FAA approval in hand, weather rapidly improving, and the latest rocket prototype seemingly raring to go, the stars are aligning for SpaceX’s third high-altitude Starship launch and first triple-engine landing attempt.
As of March 1st, publicly-available FAA “temporary flight restrictions” (TFRs) and weather forecasts both agree that SpaceX is currently preparing to launch Starship serial number 10 (SN10) as early as Wednesday afternoon CST (UTC-6), March 3rd. Barring surprises, that gives SpaceX a healthy three-day period to account for any potential technical or weather-related delays.
Originally scheduled as early as the last week of February, unspecified delays pushed Starship SN10’s launch debut schedule into March. In general, the vehicle’s path to flight has been much smoother than Starship SN8 and SN9, both of which ran into hardware bugs and opaque FAA licensing issues. With Starship SN10, the FAA approved SpaceX’s “modified” launch license well before the company was ready for flight – and even before the rocket had attempted its first static fire.
Unlike Starships SN8 and SN9, both of which took anywhere from 6-10 weeks to go from rolling off the factory floor to preparing for their first launch attempts, SN10’s first launch attempt appears likely to occur less than five weeks after the rocket arrived at the launch site. The sequential improvements in efficiency and reliability between those three prototypes is a fundamental part (or goal, at least) of SpaceX’s iterative development process.
Still, Starship SN10’s preflight flow wasn’t completely free of drama and SpaceX ultimately put the rocket through a second triple-Raptor static fire after the first test revealed an issue with one of those engines. SpaceX swapped that faulty engine out in record time and fired up SN10 again less than 48 hours after test #1, seemingly producing more satisfactory results the second time around.
Unlike its predecessors, SN10 will also debut a new triple-engine approach to landing, aiming to increase redundancy and boost the odds of a successful touchdown even if one of the Starship’s three Raptors fail during a last-second flip maneuver. Building on the failures of SN8 and SN9, it’s safe to say that SN10 has the best shot yet at sticking the landing.
TFRs show that two earlier launch windows on Monday and Tuesday (March 1st and 2nd) were canceled, leaving only the Wednesday, March 3rd airspace closure request still open. Wednesday was then backed up with two alternate windows on Thursday and Friday not long after.
Hardware-wise, Starship SN10’s cherry-on-top (an explosives-based flight termination system or FTS) was installed on February 28th. In the event that Starship loses control and strays past a certain point outside of its approved trajectory, that FTS would explode, breaching the rocket’s propellant tank, triggering vehicle breakup, and thus preventing it from harming the local populace. All told, SpaceX confirmation of a Wednesday launch attempt – and another official webcast – should be imminent. Stay tuned!
Tesla has scaled back driver monitoring to be less naggy with the latest version of the Full Self-Driving (Supervised) suite, which is version 14.3.3.
The latest version is already earning praise from owners, who are reporting that the suite is far less invasive when it comes to keeping drivers from taking their eyes off the road. The first to mention it was notable Tesla community member on X known as Zack, or BLKMDL3.
14.3.3 nags less too https://t.co/IuiWzuYO6O
— Elon Musk (@elonmusk) May 18, 2026
Musk confirmed that v14.3.3 was made to nag drivers significantly less, something that Tesla has worked toward in the past and has said with previous versions that it is less likely to push drivers to look ahead, at least after looking away for a few seconds.
This refinement aligns with Tesla’s ongoing push toward unsupervised FSD. The update also brings faster Actual Smart Summon (now up to 8 mph), reliable “Hey Grok” voice commands, richer visualizations, smoother Mad Max acceleration, and an intervention streak counter that rewards consistent use. Reviewers describe the drive as more human-like and confident, with fewer twitches or unnecessary maneuvers.
Musk has repeatedly signaled this direction. In late 2025, he stated that FSD would allow phone use “depending on context of surrounding traffic,” noting safety data would justify relaxing rules so drivers could text in low-risk scenarios like stop-and-go traffic.
We tested this, and even still, the cell phone monitoring really seems to be less active in terms of alerting drivers:
Tesla Full Self-Driving v14.2.1 texting and driving: we tested it
Earlier, ahead of v14, Musk promised the system would “nag the driver much less” once safety metrics improved.
In 2023, he confirmed the steering wheel torque nag would be “gradually reduced, proportionate to improved safety,” shifting reliance to the cabin camera. Subsequent updates like v13.2.9 and v12.4 further loosened monitoring, cracking down on workarounds while easing legitimate distractions.
These steps reflect Tesla’s data-driven approach: FSD’s safety record—reportedly averaging millions of miles per crash—now outpaces human drivers in many scenarios, giving the company confidence to dial back interventions. Reduced nags improve usability and trust, encouraging more drivers to rely on the system rather than disengaging out of frustration.
However, there are certainly still some concerns. In many states, it is illegal to handle a cell phone in any way, requiring the use of hands-free devices. In Pennsylvania, it is illegal to use your cell phone at stop lights, which is definitely a step further than using it while the car is actively in motion.
v14.3.3 represents tangible progress. Making FSD less adversarial and more seamless is definitely a step forward, but drivers need to be aware of the dangers of distracted driving. FSD is extremely capable, but it is in no way fully autonomous, nor does its performance warrant owners to take their attention off the road.
Tesla has officially expanded its Full Self-Driving (FSD) suite in Europe once again, as it will now be offered to customer vehicles in Lithuania, marking a significant milestone as the second European Union country to offer the system.
Tesla confirmed FSD’s rollout in Lithuania this morning:
FSD Supervised now rolling out to Teslas in Lithuania 🇱🇹!
Making European roads safer, one by one pic.twitter.com/Uuj0bNG7pP
— Tesla Europe, Middle East & Africa (@teslaeurope) May 20, 2026
Tesla showed several clips of Full Self-Driving navigation in Lithuania to mark the announcement, while Lithuanian Transport Minister Juras Taminskas highlighted the system’s potential to assist with lane-keeping, speed adjustment, and traffic tasks on longer drives, while emphasizing that drivers must stay alert and ready to intervene.
Just a few weeks ago, Tesla officially entered Europe with Full Self-Driving in the Netherlands. The expansion of FSD on the continent is now officially underway.
Full Self-Driving’s European Journey
Europe has long posed one of the toughest regulatory challenges for Tesla’s autonomy ambitions due to stringent safety standards under the United Nations Economic Commission for Europe (UNECE) framework, particularly UN Regulation 171 for Driver Control Assistance Systems.
The Netherlands’ RDW authority granted the pioneering approval after over 18 months of rigorous testing, including 1.6 million kilometers on European roads and extensive data submissions.
This approval enables mutual recognition across the EU, allowing other member states to adopt it nationally without full re-testing. Lithuania quickly leveraged this mechanism, becoming the second adopter. Tesla positions FSD Supervised as a tool to incrementally improve road safety, with the company claiming it reduces incidents when used properly.
Bottlenecks slowing broader European deployment include fragmented national regulations, varying levels of regulatory skepticism, and requirements for robust driver monitoring. Some EU officials have raised concerns about performance in adverse conditions like icy roads or speeding scenarios, alongside frustrations over Tesla’s public advocacy approach.
Additional hurdles involve data privacy, liability frameworks, and the need for EU-wide harmonization. While countries like Belgium appear to be fast-tracking adoption, larger markets such as Germany, France, and Italy are expected to follow in the coming months, with potential EU-wide progress targeted for later in 2026.
Tesla Full Self-Driving Across the World
As of May, Full Self-Driving (Supervised) is available in approximately ten countries.
In North America, it has been live for years in the United States, Canada, Mexico, and Puerto Rico. Asia-Pacific additions include Australia, New Zealand, and South Korea, while China utilizes what Tesla calls “City Autopilot.” In Europe, the Netherlands and now Lithuania join the list, with more countries mulling the possibility of also approving FSD.
Tesla offers FSD via monthly subscriptions (around €99 in Europe) or one-time purchases (with deadlines approaching in many markets), shifting toward recurring revenue models. Today is the final day Europeans will be able to purchase the suite outright.
This expansion underscores Tesla’s push for global autonomy, starting with supervised and building toward greater capabilities. With Lithuania now online, momentum is building across Europe, though regulatory caution will continue shaping the pace. Owners in approved regions report smoother highway and urban driving, but the system remains Level 2, which requires human oversight.
Elon Musk
Tesla ditches India after years of broken promises
Tesla has ditched its plans to build a factory in India after years of failed negotiations.
Tesla’s long-running effort to establish a manufacturing presence in India is officially over. India’s Minister of Heavy Industries H.D. Kumaraswamy confirmed on May 19, 2026 that Tesla has informed authorities it will not proceed with a manufacturing facility in the country.
Tesla first signaled serious interest in India around 2021, when it began hiring local staff and lobbying the Indian government for lower import tariffs. The ask was straightforward: reduce duties enough for Tesla to test the market with imported vehicles before committing capital to a local factory. India’s position was equally firm, with an ask of Tesla to commit to manufacturing first, then receive tariff relief. Neither side moved, and the talks quietly collapsed.
Tesla to open first India experience center in Mumbai on July 15
India had offered a policy that would reduce import duties from 110% down to 15% on EVs priced above $35,000, provided companies committed at least $500 million toward local manufacturing investment within three years. Tesla declined to participate. The tariff standoff was only part of the problem. Analysts pointed to significant gaps in India’s local supply chain, inadequate industrial infrastructure, and a mismatch between Tesla’s premium pricing and the purchasing power of India’s automotive market as additional factors that made the investment difficult to justify.
First signs of an unraveling relationship came in April 2024, when Musk abruptly cancelled a planned trip to India where he was set to meet Prime Minister Modi and announce Tesla’s market entry. By July 2024, Fortune reported that Tesla executives had stopped contacting Indian government officials entirely. The government at that point understood Tesla had capital constraints and no plans to invest.
The more fundamental issue is that Tesla’s existing factories are currently operating at approximately 60% capacity, making a commitment to building new manufacturing capacity in a new market difficult to defend to investors. Tesla will continue selling imported Model Y vehicles through its existing showrooms in Mumbai, Delhi, Gurugram, and Bengaluru, but local production is no longer part of the plan.
Tesla scales back driver monitoring with latest Full Self-Driving release
Tesla Full Self-Driving expands in Europe, entering its second country
