News
What’s causing SpaceX’s Falcon Heavy delays?
Although uncertainty in the schedule remains, SpaceX’s Falcon Heavy rocket appears to be nearly ready for its first engine ignition test (called a ‘static fire’) sometime within the next week or so.
An attempt at 1 PM EST today, January 16, was canceled for unspecified reasons, although Kennedy Space Center reportedly maintained the usual roadblock to prevent vehicles from driving past, implying that SpaceX still intends to conduct propellant loading tests with Falcon Heavy. It was noted earlier this morning by spaceflight journalist Chris Bergin that things were “a bit too quiet” if a test was indeed planned for today, and his intuition appears to have been correct. It still remains the case that Falcon Heavy is an experimental and untested rocket to an extent, and these delays are to be expected as SpaceX works out the inevitable kinks and bugs that arise during the extensive testing big launch vehicle has been and is still being put through.
KSC is in roadblock stance, so they will still do some testing it would seem, but we will have to wait for the Static Fire itself. https://t.co/DxzsRn85NR
— NSF – NASASpaceflight.com (@NASASpaceflight) January 16, 2018
Due to range requirements in support of an upcoming launch of the United Launch Alliance’s (ULA) Atlas 5 rocket, currently NET Thursday, SpaceX has postponed the static fire of Falcon Heavy without a replacement date. It is unlikely that another attempt will occur before the upcoming weekend, but SpaceX should have at least a solid week of uninterrupted range support once ULA’s launch occurs, hopefully without delay. Godspeed to ULA, in the meantime.
The crazy complexity of rocketry
Most recently, and perhaps somewhat related to Falcon Heavy’s static fire delays, SpaceX completed as many as two complete wet dress rehearsals (WDRs), which saw Falcon Heavy topped off with full tanks of its cryogenic (super cool) liquid oxygen (LOX) and rocket-grade jet fuel (RP-1). In essence, the rocket became equivalent to several hundred tons of carefully stabilized explosive. Nominally, these rehearsals appear entirely uneventful to an outside observer, with little more than ice formation and the occasional bursts of propellant tank vents to suggest that something important is occurring. However, anomalies like the failure of Falcon 9 during the Amos-6 static fire provide a staggering demonstration of just how explosive and sensitive a rocket’s fuel is, and Falcon Heavy has approximately three times the fuel capacity of Falcon 9. Empty, Falcon 9’s mass has been estimated to be around 30 metric tons, a minuscule amount of structure in the face of the more than 500 metric tons of propellant the vehicle carries at liftoff.
These propellant loading tests can also be challenging for reasons aside from their highly explosive nature. Due to basic realities of the physical nature of metal, the predominate ingredient for Falcon 9’s load-bearing structures, metallic structures shrink under extreme cold (and expand under heating). In the case of Falcon 9’s massive 45 meters (150 foot) tall first stage, the scale of this contraction can be on the order of several inches or more, particularly given SpaceX’s predilection towards cooling their propellant as much as possible to increase its energy density. For Falcon 9, these issues (thermodynamic loads) are less severe. However, add in three relatively different first stage boosters linked together with several extremely strong supports at both their tops and bottoms and that dynamic loading can become a fickle beast. The expansion or compression of materials due to temperature changes can create absolutely astounding amounts of pressure – if you’ve ever forgotten a glass bottled drink in the freezer and discovered it violently exploded at some future point, you’ll have experienced this yourself.
With several inches of freedom and the possibility that each Falcon Heavy booster might contract or expand slightly differently, these forces could understandably wreak havoc with the high precision necessary for the huge rocket to properly connect with the launch pad’s ground systems that transmit propellant, fluids, and telemetry back and forth. Information from two reliable Kennedy Space Center sources experienced with the reality of operating rockets, as well as NASASpaceflight.com, suggested that issues with dynamic loads (such as those created by thermal contraction/expansion) are a likely explanation for the delays, further evidenced by their observations that much of the pad crew’s attention appeared to be focused at the base of Transporter/Erector/Launcher (TEL). The TEL base hosts the clamps that hold the rocket down during static fires and launches, as well as the Tail Service Masts (TSMs) that connect with the Falcon 9/Heavy to transport propellant and data to the first stage(s). These connection points are both relatively tiny, mechanically sensitive, and absolutely critical for the successful operation of the rocket, and thus are a logical point of failure in the event of off-nominal or unpredicted levels of dynamic stresses.
-
- The white bars in this photo are half of Falcon Heavy’s seperation mechanism. A number of actuators take the place of the more common solid rocket motors used with vehicles like the Delta IV Heavy. (SpaceX)
-
- Falcon Heavy’s three boosters and 27 Merlin 1D engines on full display. (SpaceX)
-
- Falcon Heavy. Modeled and rendered by NASASpaceflight forum user WBY1984. (WBY1984)
Test, launch, land, repeat.
All things considered, these difficulties demonstrate that even after months (even years) of relentless modeling, testing, remodeling, and retesting, rockets (and especially huge rockets like Falcon Heavy) are immensely complex, and even tiny mistakes can lead the vehicle to stray from its expected behavior. Quite simply, the reality of engineering only truly comes into play once hardware is fully in the loop, and it’s in this state that SpaceX has demonstrated again and again a distinct and elegant ability to learn from their hardware, rather than attempt to salve uncertainty with a neurotic and counterproductive level of statistical analysis, modelling, and documentation. The agile launch company still dabbles in those aspects when beneficial or necessary, but testing comes first in its importance.
The conclusion here, then, is that Falcon Heavy’s delays betray this aspect of SpaceX – a launch company that loves its fans, but also understands the need for cautious testing when it comes to new and untried rocket hardware. Whether Falcon Heavy succeeds or fails, SpaceX will learn from the proceedings, and they will be better off for it (although maybe less so financially…).
Follow along live as launch photographer Tom Cross and I cover these exciting proceedings as close to live as possible.
Teslarati – Instagram – Twitter
Tom Cross – Instagram
Eric Ralph – Twitter
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.
Tesla Full Self-Driving release in the EU gets delayed
SpaceX readies Starship Flight 14 for a historic journey into uncharted territory
