News
SpaceX Starlink launch ambitions just saved a space station resupply mission from bigger delays
SpaceX’s ambitious 2020 Starlink launch goals have unintentionally saved a Cargo Dragon spacecraft mission from much longer delays after a major part of its Falcon 9 rocket had to be replaced at the last second.
Known as SpaceX’s 20th NASA Commercial Resupply Services (CRS-20) mission, SpaceX’s Cargo Dragon spacecraft was initially scheduled to launch supplies to the International Space Station (ISS) as early as March 2nd, 2020, a date that recently slipped four days to 11:50 pm EDT (04:50 UTC), March 6th. Simultaneously, a separate Falcon 9 Starlink mission – assigned to a different launch pad – found itself delayed from March 4th to March 11th.
A day or so after news of the CRS-20 launch delay first broke, NASA published a blog post noting that SpaceX had taken the extraordinary step of fully replacing the mission’s Falcon 9 second stage, the part of the rocket (pictured underneath Dragon in the photo above) tasked with taking payloads from the edge of space into Earth orbit (or beyond). Triggered by a faulty component in its space-optimized Merlin Vacuum engine, the fact that SpaceX chose to replace the upper stage and still only delayed CRS-20’s launch by four days suggests that its ambitious Starlink launch plans are already creating positive side effects for commercial customers.
"SpaceX identified a valve motor on the second stage engine behaving not as expected and determined the safest and most expedient path to launch is to utilize the next second stage in line that was already at the Cape and ready for flight."https://t.co/E9dokEAf0n— Michael Baylor (@MichaelBaylor_) February 25, 2020
As of late, multi-day hardware-related launch delays have been rather rare for SpaceX, who has instead suffered numerous weather-related scrubs over the course of completing its Fall 2019 and Winter 2020 launch manifest. SpaceX’s February 17th Starlink-4 mission did suffer a minor second stage valve-related delay that was fixed in about 24 hours, but things have otherwise been quite smooth for Falcon 9.
Given all that goes into building and testing Falcon 9 second stages, there are very few good explanations (aside from pure luck) that would allow for a given SpaceX launch to entirely replace its assigned second stage a week before liftoff and only slip a handful of days. Nevertheless, with CRS-20, SpaceX is attempting to do exactly that.
“SpaceX identified a valve motor on the second stage engine behaving not as expected and determined the safest and most expedient path to launch is to utilize the next second stage in line that was already at the Cape and ready for flight. The new second stage has already completed the same preflight inspections with all hardware behaving as expected. The updated target launch date provides the time required to complete preflight integration and final checkouts.”
NASA.gov — February 25th, 2020
The specific lead times SpaceX’s Falcon rocket family parts require is almost totally unknown but it’s safe to say that the process of building a Falcon upper stage from scratch, performing acceptance testing in Texas, and shipping said stage to the launch pad takes months from start to finish. For SpaceX to be able to attempt to minimize CRS-20’s delays to just four days while still fully swapping out its upper stage, the company would have quite literally had to have had another Falcon stage just sitting around in Florida.
As it turns out, per NASA’s official statement, that is precisely what transpired. A separate second stage was already in Florida and “ready for flight”, giving SpaceX the luxury of selecting the safest option theoretically available. Beyond the hardware already being ready to go in Florida, the stage reassignment almost certainly also hinged upon the mission it was assigned to being somewhat nonessential – a label that SpaceX would be hard-pressed to affix to any of its customers’ launches. An internal Starlink mission, however, would be a perfect opportunity, allowing SpaceX to avoid both picking favorites and seriously impacting (aside from the ~4-day CRS-20 delay) its paying customers.
To be clear, SpaceX was thus able to swap out CRS-20’s upper stage at the last second with only a minor schedule impact almost exclusively because of it’s ambitious plans for 20-24 Starlink launches this year. If the company wasn’t pursuing a more than biweekly 2020 launch cadence, it’s much more likely that CRS-20 would have had to make do with its second stage or wait for a new one to be built, potentially delaying the launch by one or two weeks, if not longer.
In simple terms, the launch cadence SpaceX is targeting (and needs) for its Starlink constellation is already exhibiting signs of a future where its high-performance orbital-class rockets have been almost entirely commodified.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
News
Tesla Full Self-Driving release in the EU gets delayed
Tesla Full Self-Driving’s release in Europe is set to be delayed by at least a few months.
The European Union will not vote on Tesla’s Full Self-Driving (Supervised) on October 6. The draft agenda for the 119th meeting of the Technical Committee on Motor Vehicles lists only a 25-minute “continuation of discussions” on the Netherlands’ Article 39 request, not a decision. The next scheduled TCMV session is in December, which is now the earliest date a bloc-wide vote could occur.
Tesla Europe had pointed to October 6 as a possible EU-wide vote after the Dutch vehicle authority RDW granted the first European type approval on April 10.
That approval, under UN Regulation 171 plus an Article 39 exemption in EU Regulation 2018/858, is the legal file other member states have been recognizing one by one. The same committee has already discussed the request twice without voting.
Elon Musk’s reply to the delay was a single word: “Sigh.”
Sigh
— Elon Musk (@elonmusk) September 25, 2026
Seven EU countries have now cleared FSD Supervised on their own roads: the Netherlands, Lithuania, Estonia, Denmark, Belgium, Slovenia, and Czechia. Those seven states represent about 53 million people, or roughly 12 percent of the EU population. An EU-wide authorization still needs a qualified majority: at least 15 of 27 member states representing 65 percent of the bloc’s population, about 292 million people.
Germany, France, Italy, and Spain remain the decisive markets. France has already rejected the current system; several other governments have flagged speed-limit compliance as the main sticking point.
The safety case Tesla is putting in front of those governments is now public. On September 1, Tesla Europe said FSD Supervised was in use by more than 70,000 customers, covering over 1 million kilometers a day, and was 4.1 times less likely to be involved in a crash than manual driving across 100 million kilometers on EU public roads.
An earlier mid-year cut of the same fleet data, covering 65 million kilometers in five approved countries, put the collision advantage at 5.2 times, with zero highway collisions over 41.9 million kilometers. Tesla also reported far fewer automatic emergency braking events, harsh accelerations, and hard swerves than in comparable manual Tesla driving. Those figures are company-reported, not independently audited.
Tesla Full Self-Driving is taking over Europe: fourth country gets FSD approval
The public-health backdrop is harder to dispute. European countries recorded about 19,400 road deaths in 2025, or roughly 53 a day, most of them attributed to human error. FSD Supervised is not unsupervised autonomy; the driver remains legally responsible. But the software is already legal and in daily use across seven member states.
Until TCMV votes, the rest of the EU remains a patchwork: available in Prague and Amsterdam, locked behind review in Paris and Berlin. December is now the next chance to close that gap.
News
SpaceX readies Starship Flight 14 for a historic journey into uncharted territory
SpaceX finished Starship’s Flight 14 rehearsal, clearing the way for its first orbital flight Monday.
SpaceX has cleared one of the last hurdles before Starship’s first trip to orbit. The company posted on X Thursday afternoon that its launch rehearsal for Flight 14 was complete, keeping the mission on track for Monday, September 28. The launch window opens at 7:15 a.m. CT at Starbase, Texas, and runs for 75 minutes.
A wet dress rehearsal is essentially launch day without the launch. Crews fill Booster 21 and Ship 41 with thousands of tons of extremely cold propellant, run the countdown nearly to ignition, then drain everything back out. It lets engineers catch leaks or equipment problems before anything leaves the pad. SpaceX still needs a launch license from the FAA before the stack, which stands 407 feet tall, can fly.
Flight 14 matters because of where it is going. All 13 previous Starship flights followed a suborbital path, which works like throwing a ball extremely high and far: the vehicle reaches space, but it is always on a course that brings it back down within about an hour. This time, Ship 41 will perform a short engine firing called an orbital insertion burn roughly 25 minutes after liftoff, giving it enough speed to keep falling around Earth instead of back into it. SpaceX plans about six laps at an altitude near 275 kilometers (171 miles) over nearly 10 hours, as Teslarati detailed when the mission was first announced.
Launch rehearsal complete ahead of Starship Flight 14 pic.twitter.com/h5LBYyBqi4
— SpaceX (@SpaceX) September 24, 2026
Getting into orbit also means Starship has to prove it can get back out. The ship must relight a single Raptor engine in space to slow down for reentry. SpaceX says it will only attempt the orbital insertion burn after flight controllers confirm the hardware needed for that return burn has enough backup, and its flight plan includes health checks that could shorten the mission to two or five orbits.
Flight 14 is also the first to put working satellites into service. Flight 13 carried 20 Starlink V3 satellites in July, but they came back down with the ship because that mission never reached orbit. This time, 26 V3 satellites are meant to stay up and join the constellation within a few weeks. Together they add about 26 terabits per second of network capacity, which SpaceX says is roughly 10 times what a single Falcon 9 launch of older V2 Mini satellites adds. Three of them carry cameras that will photograph Starship’s heat shield in orbit to check for tile damage before reentry.
The hardware has changed too. Ship 41 flies with extra fasteners on tiles in the most vulnerable areas, fixes for gaps where superheated plasma slipped behind tiles, and curved tiles designed to reduce heating between them. Two tiles recovered from Ship 40 will fly again, the first reuse of any part of a Starship heat shield. Booster 21 carries better engine filtering and new relight software after ice clogged three center engines on the previous booster, leaving only eight of 13 engines to restart for its landing burn.
Ship 41 is targeting a splashdown in the Pacific Ocean west of Chile, a new recovery zone after several Indian Ocean landings, while Booster 21 aims for the Gulf. Neither will be caught by the tower on this flight. Elon Musk said in August that a ship catch was likely “in a few months.”
Elon Musk
Google just picked SpaceX for its first step into orbital AI
Google will launch its first Project Suncatcher AI satellite on SpaceX’s Transporter-18 rideshare next week.
Google is about to put its own AI chips into orbit for the first time, and it is paying SpaceX to get them there.
The company said Thursday that the first in-orbit test of Project Suncatcher, its research effort to find out whether space can host large-scale AI computing, will fly next week on SpaceX’s Transporter-18 rideshare mission.
The satellite, called MVP, is about the size of a refrigerator and carries four of Google’s Tensor Processing Units, the same chips Google runs in its ground data centers. Google originally planned to launch two custom satellites in 2027, but chose to move faster by integrating its chips into a satellite.
MVP’s solar panels supply about one kilowatt of power, and Google will run Gemini models on the TPUs only in bursts of roughly 15 minutes before the chips shut down so the radiators can shed heat. In a blog post, Google said its Trillium TPUs survived vibration testing that mimicked sustained launch loads of up to 10g, with individual components seeing 50 to 100g, and handled a radiation dose greater than a five year mission would deliver.
SpaceX and Google mull massive partnership on Musk’s orbital data dream: report
Next week’s flight, slated for October 1, follows a relationship that became public in May, when Teslarati reported that Google was in talks with SpaceX for a launch deal tied to orbital data centers. Google also holds a stake of roughly 6% in SpaceX.
The two companies are chasing the same idea from very different starting points. SpaceX’s own orbital compute program is built around the AI1 satellite, a roughly 70 meter structure derived from Starlink V3 hardware that is designed for 150 kW of peak compute, about 150 times the power MVP will draw. Elon Musk has brushed off concerns about crowding orbit with those satellites, and SpaceX is building its Gigasat factory in Bastrop, Texas, to produce them, targeting an annualized rate of about 1 GW of space compute by the end of 2027.
Musk also posted on X on Thursday that “the amount of compute in space will obviously round up to 100% of all compute.”
Google has been more cautious in public. Its research estimates that launch prices need to fall below about $200 per kilogram before an orbital data center can compete with a ground facility on energy cost, a threshold the company believes could be reached around the mid 2030s. The Suncatcher team has said it expects the effort to remain a project rather than a product for years, which leaves the first real test of its hardware riding on a rocket from the company with the most aggressive timeline in the field.