News
[Update: Scrubbed] SpaceX Starship to attempt same-day static fire and launch
Update: Starship SN11 did manage a timely static fire around 8am CDT but after hours of work, SpaceX appears to have scrubbed a Friday, March 26th launch attempt.
SpaceX’s website has yet to be updated and Friday’s FAA TFR is still active but a road closure meant to last until 7:30 pm CDT to cover the static fire and launch was retracted after the highway was reopened around 2:45 pm. It’s unclear what caused the scrub but weather or technical issues from the static fire are two likely candidates. SpaceX still has TFRs active on Saturday and Sunday, but the company hasn’t tested or flown on a weekend in months.
Lacking only an official confirmation, SpaceX appears to be readying the fourth full-size Starship prototype to attempt a Raptor static fire test and launch on the same day.
That hopeful day in question happens to be today – Friday, March 26th. If all goes according to plan, Starship serial number SN11 will fire up its three Raptors, verifying their health after an engine was apparently swapped out on Wednesday. Possibly just an hour or two later, after detanking and retanking liquid oxygen and methane propellant, the Starship prototype could lift off on SpaceX’s fourth high-altitude test flight.
Late on March 24th, SpaceX rolled Raptor engine SN46 from its Boca Chica factory to the launch pad, where Starship SN11 is installed on one of two suborbital launch mounts. The engine move and subsequent installation came as a surprise, as nobody managed to catch an implied Starship SN11 engine removal in the two or three days prior (extremely thick fog being the likeliest cause).
The implied issue with the Raptor that was removed is likely to blame for a several-day launch delay that followed Starship’s seemingly successful Monday static fire. After that test, SN11’s launch was initially scheduled as early as Tuesday or Wednesday, only to slip day by day as the week proceeded. SN11 first rolled to the launch pad on March 8th, just 18 days ago, so launch delays don’t come as a huge surprise given that the current factory-to-launch record for a three-engine Starship is 33 days, three static fires, and one engine swap.
If SN11 manages a same-day static fire and launch on March 26th, it will still crush that record by almost 50%. To an extent, the feat also isn’t unprecedented. On March 3rd, Starship SN10 aborted its first true launch attempt milliseconds after Raptor ignition when the rocket’s flight computer detected indications that they were producing too much thrust. Amazingly, instead of scrubbing the launch attempt, SpaceX loosened Starship SN10’s thrust limit parameters and tried again, successfully lifting off just three hours after the abort.
Despite the abort and immediate hands-free recycle, Starship SN10 subsequently became the first prototype of its kind to launch to 10 km (6.2 mi), free-fall back to earth, and land in one piece. Minutes later, a fire and harder landing than expected conspired to make SN10 explode, but the test flight was arguably still a massive success. Simultaneously, the flight indicated that Starships are technically capable of successfully flying hours after a post-ignition launch abort, demonstrating an extraordinary level of robustness for clustered high-performance rocket engines.
As such, while it’s probably reasonable to assume that Starship SN11 wont launch today, SN10 proved that there is nonzero chance of a static fire and launch hours apart. Additionally, given just how close SN10 go to unequivocal success (i.e. a soft and survivable landing), Starship SN11 has the best chance yet at at launching, landing, and making it through the ordeal without exploding.
Starship SN11’s third static fire and first launch attempt are both currently scheduled sometime between 7am and 7:30pm CDT (UTC-5). Stay tuned for updates as we wait for SpaceX’s official confirmation and an evacuation notice of Boca Chica Village residents.
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.”
