News
SpaceX Starship aborts Raptor engine test, briefly catches fire
Update: On March 15th, SpaceX got within milliseconds of Starship serial number 11’s (SN11) first Raptor engine test but suffered an abort just before full ignition, briefly leaving the rocket on fire.
Around 12:26 pm CDT, after an otherwise nominal static fire flow, Starship SN11 momentarily ignited one or two of its three Raptor engines’ preburners, referring to a central component that burns cryogenic liquid propellant into gas that’s ready for combustion. As with all preburner tests, intentional or otherwise, the end result looked a bit like a weak static fire and produced a small but visible amount of flame and thrust. Unlike intentional preburner tests, the static fire abort seemingly ignited something hidden inside Starship SN11’s and appeared to burn for at least another 30-40 seconds.
Raptor has proven itself to be an extremely durable engine, up to and including surviving visible onboard fires during actual Starship flight tests. Nevertheless, depending on the source of SN11’s post-abort fire and what it may or may not have burned or damaged, it’s no surprise that SpaceX ended testing for the day instead of quickly trying again, which it’s done several times prior. If the fire was largely harmless, SpaceX has already distributed notices suggesting a second attempt could happen as early as 6am to 12pm CDT (UTC-5) on Tuesday, March 16th. If more time is needed, SpaceX has the rest of the week to conduct any necessary repairs or swap out SN11’s Raptor engines.
Public documents show that SpaceX has plans to static fire and launch its latest Starship prototype within a two-day period that could begin later today.
SpaceX shipped Starship SN11 from its Boca Chica, Texas rocket factory to test and launch facilities a mile down the road on March 8th, less than five days after Starship SN10 exploded minutes after touchdown. The very next day, SpaceX completed ambient-temperature proof testing, filling Starship with benign nitrogen gas to check for leaks and verify system health. Two days after that, Starship SN11 appeared to complete a several-hour cryogenic proof test – swapping nitrogen gas for its supercool liquid form – without issue.
Despite the seemingly successful ‘cryo proof,’ something prevented a subsequent static fire test planned on March 12th before any attempt could be made, delaying the next attempt until after the approaching weekend. An agreement between SpaceX, Cameron County, and the state of Texas currently prevents road closures (and thus rocket testing) on weekends falling between Labor Day and Memorial Day, rules meant to preserve some level of public access to Boca Chica Beach.
As a result, unless SpaceX is already ready to launch (it has waivers for three such weekend closures for launch attempts), the company has to wait until Monday even if a minor issue fixable in hours or a day or so scrubs Friday test plans. While inconvenient, it’s worth noting that the existence of that public beach and the strong regulations that protect its public domain is likely one of the only reasons the general public can still get as close as they can to SpaceX’s Boca Chica ‘Starbase’.
For whatever reason, that road closure agreement does still mean that SpaceX will (in theory) be able to test and launch any day of the week from May 31st to September 6th, save for a few holidays, effectively boosting the number of opportunities by 40% for those 14 weeks. Until then, SpaceX is doing everything it can to take full advantage of the five days a week it is allowed to test Starship prototypes. N
Notably, although Starships SN8 and SN9 both hit a few weeks of technical and regulatory snags while preparing for their high-altitude launch attempts, SpaceX has been gradually speeding up that process over time. Starship SN10, the first prototype of its kind to land in one piece, took just 33 days to go from pad arrival to liftoff and spent just 8 days between its first static fire and launch attempts. The same feats took Starship SN8 77 and 50 days, respectively, with SN9 splitting the difference at 43 days from transport to liftoff and 28 days between its first static fire and launch attempts.
Road closure requests, a safety warning for residents, and a Temporary Flight Restriction (TFR) filed with the FAA all suggest that SpaceX’s current plan is to attempt Starship SN11’s first triple-Raptor static fire between 6am and 12pm CDT on Monday, March 15th. If that test goes almost perfectly, SpaceX wants to turn the rocket around for a 10 km (6.2 mi) launch attempt on Tuesday, March 16th – the very next day. Given the past performance of high-altitude Starship prototypes, that target is decidedly ambitious and likely to incur delays, but it still reveals the true scope of SpaceX’s goals even at this early stage of development.
If Starship SN11 does manage to launch within a few days of its first static fire attempt, SpaceX would still crush SN10’s 33-day record by a factor of three. Stay tuned for updates on Monday’s possible Starship static fire and rapid Tuesday turnaround attempt
Elon Musk
SpaceX’s Starship FL launch site will witness scenes once reserved for sci-fi films
A Starship that launches from the Florida site could touch down on the same site years later.
The Department of the Air Force (DAF) has released its Final Environmental Impact Statement for SpaceX’s efforts to launch and land Starship and its Super Heavy booster at Cape Canaveral Space Force Station’s SLC-37.
According to the Impact Statement, Starship could launch up to 76 times per year on the site, with Super Heavy boosters returning within minutes of liftoff and Starship upper stages landing back on the same pad in a timeframe that was once only possible in sci-fi movies.
Booster in Minutes, Ship in (possibly) years
The EIS explicitly referenced a never-before-seen operational concept: Super Heavy boosters will launch, reach orbit, and be caught by the tower chopsticks roughly seven minutes after liftoff. Meanwhile, the Starship upper stage will complete its mission, whether a short orbital test, lunar landing, or a multi-year Mars cargo run, and return to the exact same SLC-37 pad upon mission completion.
“The Super Heavy booster landings would occur within a few minutes of launch, while the Starship landings would occur upon completion of the Starship missions, which could last hours or years,” the EIS read.
This means a Starship that departs the Florida site in, say, 2027, could touch down on the same site in 2030 or later, right beside a brand-new stack preparing for its own journey, as noted in a Talk Of Titusville report. The 214-page document treats these multi-year round trips as standard procedure, effectively turning the location into one of the world’s first true interplanetary spaceports.
Noise and emissions flagged but deemed manageable
While the project received a clean bill of health overall, the EIS identified two areas requiring ongoing mitigation. Sonic booms from Super Heavy booster and Starship returns will cause significant community annoyance” particularly during nighttime operations, though structural damage is not expected. Nitrogen oxide emissions during launches will also exceed federal de minimis thresholds, prompting an adaptive management plan with real-time monitoring.
Other impacts, such as traffic, wildlife (including southeastern beach mouse and Florida scrub-jay), wetlands, and historic sites, were deemed manageable under existing permits and mitigation strategies. The Air Force is expected to issue its Record of Decision within weeks, followed by FAA concurrence, setting the stage for rapid redevelopment of the former site into a dual-tower Starship complex.
SpaceX Starship Environmental Impact Statement by Simon Alvarez
News
Tesla Full Self-Driving (FSD) testing gains major ground in Spain
Based on information posted by the Dirección General de Tráfico (DGT), it appears that Tesla is already busy testing FSD in the country.
Tesla’s Full Self-Driving (Supervised) program is accelerating across Europe, with Spain emerging as a key testing hub under the country’s new ES-AV framework program.
Based on information posted by the Dirección General de Tráfico (DGT), it appears that Tesla is already busy testing FSD in the country.
Spain’s ES-AV framework
Spain’s DGT launched the ES-AV Program in July 2025 to standardize testing for automated vehicles from prototypes to pre-homologation stages. The DGT described the purpose of the program on its official website.
“The program is designed to complement and enhance oversight, regulation, research, and transparency efforts, as well as to support innovation and advancements in automotive technology and industry. This framework also aims to capitalize on the opportunity to position Spain as a pioneer and leader in automated vehicle technology, seeking to provide solutions that help overcome or alleviate certain shortcomings or negative externalities of the current transportation system,” the DGT wrote.
The program identifies three testing phases based on technological maturity and the scope of a company’s operations. Each phase has a set of minimum eligibility requirements, and applicants must indicate which phase they wish to participate in, at least based on their specific technological development.

Tesla FSD tests
As noted by Tesla watcher Kees Roelandschap on X, the DGT’s new framework effectively gives the green flight for nationwide FSD testing. So far, Tesla Spain has a total of 19 vehicles authorized to test FSD on the country’s roads, though it would not be surprising if this fleet grows in the coming months.
The start date for the program is listed at November 27, 2025 to November 26, 2027. The DGT also noted that unlimited FSD tests could be done across Spain on any national route. And since Tesla is already in Phase 3 of the ES-AV Program, onboard safety operators are optional. Remote monitoring would also be allowed.
Tesla’s FSD tests in Spain could help the company gain a lot of real-world data on the country’s roads. Considering the scope of tests that are allowed for the electric vehicle maker, it seems like Spain would be one of the European countries that would be friendly to FSD’s operations. So far, Tesla’s FSD push in Europe is notable, with the company holding FSD demonstrations in Germany, France, and Italy. Tesla is also pushing for national approval in the Netherlands in early 2026.
News
Tesla FSD V14.2.1 is earning rave reviews from users in diverse conditions
Tesla’s Full Self-Driving (Supervised) software continues its rapid evolution, with the latest V14.2.1 update drawing widespread praise.
Tesla’s Full Self-Driving (Supervised) software continues its rapid evolution, with the latest V14.2.1 update drawing widespread praise for its smoother performance and smarter decision-making.
Videos and firsthand accounts from Tesla owners highlight V14.2.1 as an update that improves navigation responsiveness, sign recognition, and overall fluidity, among other things. Some drivers have even described it as “more alive than ever,” hinting at the system eventually feeling “sentient,” as Elon Musk has predicted.
FSD V14.2.1 first impressions
Early adopters are buzzing about how V14.2.1 feels less intrusive while staying vigilant. In a post shared on X, Tesla owner @LactoseLunatic described the update as a “huge leap forward,” adding that the system remains “incredibly assertive but still safe.”
Another Tesla driver, Devin Olsenn, who logged ~600 km on V14.2.1, reported no safety disengagements, with the car feeling “more alive than ever.” The Tesla owner noted that his wife now defaults to using FSD V14, as the system is already very smooth and refined.
Adverse weather and regulatory zones are testing grounds where V14.2.1 shines, at least according to testers in snow areas. Tesla watcher Sawyer Merritt shared a video of his first snowy drive on unplowed rural roads in New Hampshire, where FSD did great and erred on the side of caution. As per Merritt, FSD V14.2.1 was “extra cautious” but it performed well overall.
Sign recognition and freeway prowess
Sign recognition also seemed to show improvements with FSD V14.2.1. Longtime FSD tester Chuck Cook highlighted a clip from his upcoming first-impressions video, showcasing improved school zone behavior. “I think it read the signs better,” he observed, though in standard mode, it didn’t fully drop to 15 mph within the short timeframe. This nuance points to V14.2.1’s growing awareness of temporal rules, a step toward fewer false positives in dynamic environments.
FSD V14.2.1 also seems to excel in high-stress highway scenarios. Fellow FSD tester @BLKMDL3 posted a video of FSD V14.2.1 managing a multi-lane freeway closure due to a police chase-related accident. “Perfectly handles all lanes of the freeway merging into one,” the Tesla owner noted in his post on X.
FSD V14.2.1 was released on Thanksgiving, much to the pleasant surprise of Tesla owners. The update’s release notes are almost identical to the system’s previous iteration, save for one line item read, “Camera visibility can lead to increased attention monitoring sensitivity.”
