News
SpaceX's in-flight rocket engine failure threatens NASA astronaut launch debut
An in-flight rocket engine failure during SpaceX’s March 18th Starlink launch could pose a threat to the company’s imminent NASA astronaut launch debut according to a statement provided by the space agency yesterday.
SpaceX and NASA are currently working around the clock to prepare a Falcon 9 rocket and Crew Dragon spacecraft for the company’s inaugural astronaut launch, a flight known as Demonstration Mission 2 (Demo-2/DM-2). All launch vehicle and spacecraft hardware – including booster B1058, an expendable upper stage, a spacecraft trunk, and the Crew Dragon capsule itself – are already believed to be at SpaceX’s Florida launch and processing facilities.
Prior to March 18th, the biggest gating items were believed to be a few final parachute tests and a whole lot of paperwork and reviews, as well as some important but less showstopping astronaut training. Unfortunately, SpaceX has suffered two unforeseen issues of varying severity in the last few days, both of which are now all but guaranteed to impact Crew Dragon’s astronaut launch debut schedule.
“According to the CCtCap contracts, SpaceX is required to make available to NASA all data and resulting reports. SpaceX, with NASA’s concurrence, would need to implement any corrective actions found during the investigation related to its commercial crew work prior to its flight test with astronauts to the International Space Station. NASA and SpaceX are holding the current mid-to-late May launch timeframe, and would adjust the date based on review of the data, if appropriate.”
NASA — March 25th, 2020

On March 18th, less than three minutes after liftoff and shortly before stage separation was scheduled, Falcon 9 booster B1048 – on its historic fifth launch attempt – suffered an engine failure visible on SpaceX’s official webcast. By all appearances, Falcon 9’s autonomous flight computer accounted for the engine’s failure, shutdown, and the resultant loss of thrust by burning B1048’s eight remaining engines for several seconds longer than planned.


While that extra few seconds of burn time likely ensured that the rocket’s upper stage was able to make it to the correct orbit after stage separation, roughly five minutes after B1048’s extremely rapid engine failure, contact was lost. For the first time ever, there were no landing burn-related call-outs from SpaceX launch operators, the first sign that something was seriously wrong. A few minutes later, SpaceX’s webcast hosts acknowledged that the booster had been lost, perhaps lacking the propellant it needed to attempt a landing.
For reference, Merlin 1D engines likely consume some ~270 kg (600 lb) of fuel each second. Falcon 9’s landing propellant reserves are believed to be on the order of 50+ metric tons (110,000 lb). Excluding the failed engine, eight Merlin 1Ds burning at full thrust for an additional 5 seconds would consume 20% of the propellant needed for landing; 10 seconds and it would use 40%.
The anomaly was Merlin 1D engine’s first in-flight failure ever. The 2012 failure of one of an original Falcon 9 V1.0’s rocket’s nine Merlin 1C engines is SpaceX’s only other in-flight failure.
It’s likely that B1048’s engine failure was primarily related to the fact that the booster was SpaceX’s pathfinder for a fifth-flight reusability milestone, making it the most reused rocket booster ever launched. NASA currently requires all of its Crew Dragon missions to launch on new Falcon 9 rockets, hopefully mitigating direct corollaries between the Starlink L6 anomaly and astronaut launches. Regardless, the space agency says that the company will now have to complete its internal failure review and implement necessary hardware, software, or rule changes before it’s allowed to launch NASA astronauts.

That investigation could take a matter of weeks, possibly even less, but it’s entirely possible that it could take months – let alone fixing the problems that allowed the in-flight Merlin 1D engine failure to happen in the first place. Ultimately, it will almost certainly make even the first flights of Falcon 9 and Heavy rocket boosters safer, but it could substantially delay SpaceX’s Demo-2 astronaut launch debut. Still targeted no earlier than (NET) mid-to-late May 2020, it’s safe to say that it’s reasonable to expect that schedule to slip over the next 4-6 weeks. Stay tuned for updates.
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.”
