News
Boeing's astronaut capsule flies off course, fate uncertain after launch debut
Roughly 30 minutes after lifting off for the first time on a United Launch Alliance (ULA) Atlas V rocket, Boeing’s Starliner crew capsule suffered a major failure when it attempted to raise its orbit with onboard engines.
A few hours after the failure came to light, NASA and Boeing held a press conference to update members of the media on the situation, with the space agency offering some candid – if a bit odd – insight into Starliner’s anomalous launch debut. Before the spacecraft’s software threw a wrench into the gears, the plan was for Starliner to separate from ULA’s Atlas V Centaur upper stage and use its own thrusters to reach orbit and begin the trek up Earth’s gravity well to the International Space Station (ISS).
While it will likely take weeks or even months for Boeing and NASA to determine exactly what went wrong during the mission, preliminary information has already begun to paint a fairly detailed picture.
Around 15 minutes after liftoff, Starliner separated from the rocket as intended but it appears that things began to go awry almost immediately afterward. Most notably, according to NASA administrator Jim Bridenstine’s tweets and later comments, a very early look at the telemetry suggests that Starliner’s internal clock was somehow tricked into believing that the time was either earlier or later than it actually was.
Thinking that it was in the midst of a lengthy thruster firing meant to raise its orbit and send the spacecraft on its way to the space station, Starliner was thus focused on ensuring that it was pointed as accurately as possible. Although the space station is the size of a football field, in the vastness of space, rendezvousing with it is a bit like threading a needle. While firing thrusters to do so, spacecraft thus need to point themselves as accurately as possible.
While coasting before or after one of those orbit-boosting thruster firings, Starliner thought it was actually burning towards the space station and was thus very carefully controlling its orientation with a dozen or so smaller thrusters. In short, those unintentional thruster firings burned through a ton of Starliner’s limited propellant supply – enough to make it impossible (or nearly so) for the spacecraft to rendezvous and dock the ISS, a central purpose of this particular launch.

This ultimately means that Starliner is leaning heavily on the “test” aspect of this Orbital Flight Test (OFT), uncovering failure modes and bugs that Boeing was clearly unable to tease out with ground testing and simulation. While in a totally different ballpark, SpaceX similar Crew Dragon spacecraft suffered its own major failure earlier this year, although that capsule explosion occurred during intentional ground testing, whereas Starliner’s software failed during its high-profile launch debut and has severely curtailed the scope of the spacecraft’s first orbital flight test.
In fact, Bridenstine was unable to rule out the possibility that Boeing will have to attempt a second uncrewed orbital flight test (OFT) before Starliner will be qualified to launch the space agency’s astronauts. Although early signs suggest that Boeing will still be able to attempt to deorbit and recover the spacecraft a day or two from now, the fact that Starliner will not be able to perform critical demonstrations of its ISS rendezvous and docking capabilities will make it far harder for NASA to rationally certify the spacecraft for astronaut launches.

SpaceX’s Crew Dragon, for reference, completed a more or less flawless launch, orbit raise, and rendezvous before docking with the ISS. It’s almost impossible to imagine NASA giving SpaceX permission to proceed immediately into its first astronaut launch if Crew Dragon had failed to reach the proper orbit or dock with the space station.
Regardless, it’s far too early to tell whether Boeing will have to repeat Starliner’s OFT. If Starliner performs absolutely perfectly between now and its planned soft-landing in New Mexico, there might be a chance that NASA will still allow Boeing to effectively cut corners to its astronaut launch debut, but only time will tell.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.”
