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
News
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
AT&T, Verizon and T-Mobile want 290 MHz cut from an FCC satellite plan before Thursday.
AT&T, Verizon and T-Mobile are asking the Federal Communications Commission to pull nearly 300 MHz of spectrum out of a proposal that would let satellite companies like SpaceX offer cell service directly to ordinary phones. The request lands one day before the agency votes on it.
The FCC will vote Thursday, October 29, on a notice of proposed rulemaking that would make an additional 482 MHz available for direct to device service, expanding the number of eligible bands from five to 13, according to the FCC fact sheet. It would also scrap the rule requiring a satellite operator to lease spectrum from carriers, replacing it with a certification that the operator has coexistence agreements in place or holds the terrestrial license itself.
That second path matters for SpaceX. As Teslarati reported earlier this month, SpaceX agreed to buy Grain Management’s nationwide 800 MHz portfolio to turn Starlink Mobile into a full US carrier, adding to the spectrum it already bought from EchoStar.
The carriers want two bands removed, 2.5 GHz and 3.45 GHz, which make up 290 MHz of the 482 MHz on the table. Through industry group CTIA, they argued that about 300 million users depend on those bands and that satellite operations in them are not technically feasible. T-Mobile, which calls 2.5 GHz the foundation of its Ultra Capacity 5G network, said in its own filing that satellite interference could wipe out up to 96% of a cell site’s uplink coverage area and cut uplink speeds by 88% to 99%.
Executives from all three carriers met with FCC staff on October 20, and T-Mobile CEO Srini Gopalan met separately with FCC Chairman Brendan Carr. T-Mobile’s role stands out because it is still SpaceX’s US launch partner for Starlink Mobile. The three carriers have also teamed up on their own satellite joint venture to pool spectrum, a move widely seen as a response to Starlink.
SpaceX is asking for the opposite. In an October 23 filing after meetings with FCC staff and commissioners’ offices, the company asked regulators to add the 902 to 928 MHz band to the proposal. “Doing so now saves time later,” SpaceX wrote. The company also asked the FCC to modernize interference rules and align satellite deployment requirements with those for terrestrial cell networks, saying the goal is to let satellite and ground networks work together so Americans stay connected wherever they are.
The carriers have not been shy about how they view SpaceX as a competitor. On Verizon’s third quarter earnings call Monday, its chief executive said Starlink Mobile “just can’t compete with a terrestrial network” and estimated SpaceX would need four to six years and $300 billion to $500 billion to build a full US carrier network.
Thursday’s vote will not settle which bands survive. Adopting the notice opens a public comment period, with final rules to come later in the proceeding. The FCC already considered and rejected 2.5 GHz for satellite coverage once, in 2024. SpaceX also is not the only satellite player watching: the FCC approved Amazon’s $11.6 billion acquisition of Globalstar on October 27, giving its planned direct to device fleet its own mobile satellite spectrum.
A Tesla Semi caught fire in Hayward, California, which caused both directions of traffic to shut down for hours before being completely reopened early on Wednesday, the California Highway Patrol said.
The fire occurred just after 5:30 local time in Hayward on Tuesday, as the Semi caught fire in the southbound lanes of I-880 before CHP officials made the decision to shut down both lanes of traffic due to potential risks from hazardous chemical smoke.
There were no injuries reported.
🚨 A Tesla Semi reportedly caught fire, with California Highway Patrol confirming. The Semi was on I-880 SB
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year
— TESLARATI (@Teslarati) October 28, 2026
The cause of the fire is currently unknown, as neither Tesla nor the CHP have not determined a cause.
However, some images taken before the Semi was completely destroyed by the fire seem to indicate this might have been an older unit, as it appears to be one of the designs that Tesla shipped as part of its pilot program, before revising it and starting mass production just a month ago.
@Tslachan From on of the videos looks like it’s an old Semi (not the refresh version that recently started production) https://t.co/KzwmR2kXow
— Area Under The Curve 🎗️ (@AreaUnderCurve) October 28, 2026
At the time of publication, CHP had not returned our request for a comment for additional details, including the Semi involved and any potential collaboration on an investigation between the CHP and Tesla. We will update this story when we hear back from them.
The southbound lanes were reopened at 3:30 a.m. on Wednesday, with the northbound lanes opening last night a few hours after the fire began. The CHP did state that the lithium batteries were “incredibly difficult to extinguish,” according to NBC Bay Area.
The truck’s driver said that the Semi caught fire, but he did not have an explanation.
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year.
Tesla’s launch of the “Emergency Drive Away” function a few months back offered owners a safe option to evacuate an area if they were in reasonable danger. The function finally got its first use in the real world, but it appears it was by mistake.
A video shared by u/Joshalander in the r/TeslaLounge subreddit recorded the instance from his vehicle and said the incident took place in Austin this past weekend during the city’s F1 Race.
“Was charging around 6 AM this past Sunday in Austin before heading to the F1 race and heard a pop. Looked over and saw the new emergency drive-away feature in action. Genuinely felt bad for the dude when he got out and realized what happened, since he looked exhausted and only seemed to half-read the prompts.”
🚨 Here’s the first look at Tesla’s Emergency Drive Away function in action:
Apparently this driver accidentally enabled it and drove forward; you can see the Supercharger pull with the car.
Tesla said previously this would cost up to $25k if not used properly. https://t.co/B4qQRrsO6B
— TESLARATI (@Teslarati) October 28, 2026
Emergency Drive Away unlatches the Supercharger connector from the vehicle, but still causes damage to both the car and the Supercharger. Tesla has said that it will cost up to $25,000 in repairs to have everything fixed back to normal.
Additionally, the company said that if it were not used in an emergency situation, the driver of the vehicle who activated the Emergency Drive Away feature would be responsible for all repair costs.
Tesla constitutes the following situations as reasonable justifications for activating the feature:
- You face an immediate threat to your life or personal safety.
- You must leave the area immediately.
- Exiting the vehicle is unsafe.
- Unplugging the charge connector would unreasonably delay your departure or expose you to a risk to your personal safety.
After using the feature, Tesla requires the driver to schedule Service so the car can be inspected.
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
Tesla Semi catches fire in California: what we know
