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 AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
