News
SpaceX’s third Falcon Heavy launch on track as custom booster aces static fire
SpaceX has successfully completed a static fire of its newest Falcon Heavy center core, a sign that the most challenging hardware is firmly on track for a late-June launch target.
Currently penciled in for June 22nd, Falcon Heavy’s third launch is of great interest to both SpaceX and its customer, the US Air Force. Most of the two-dozen payloads manifested on the mission are admittedly unaffiliated with the US military. However, the rideshare – known as Space Test Program 2 (STP-2) – was acquired by the USAF for the branch to closely evaluate and certify SpaceX’s Falcon Heavy rocket for critical military launches. The potential upsides of a successful demonstration and evaluation are numerous for both entities and would likely trigger additional positive offshoots.
The Center Core experience
Beyond the general contractual aspects of STP-2, the mission is significant because it will use the third Falcon Heavy center core and second Block 5 variant to be built and launched by SpaceX. Of the technical issues that complicated and delayed SpaceX’s Falcon Heavy development, most can probably be traced back to the rocket’s center core, practically a clean-slate redesign relative to a ‘normal’ Falcon 9 booster.
Most of that work centered around the extreme mechanical loads the center core would have to survive when pulling or being pulled by Falcon Heavy’s two side boosters. Not only would the center core have to survive at least two times as much stress as a Falcon 9 booster, but that stress would be exerted in ways that Falcon 9 boosters simply weren’t meant to experience, let alone survive. After years of work, SpaceX arrived at a design that dumped almost all of that added complexity squarely on the center core and the center core alone. The side boosters would need to use nosecones instead of interstages and have custom attachment points installed on their octawebs and noses, but they would otherwise be unmodified Falcon 9 boosters.
On top of that, SpaceX’s Falcon upper stage and payload fairing would require no major modifications to support Falcon Heavy missions. On the opposite hand, the center core would require extensive rework to safely survive the trials of launch, let alone do so in a fashion compatible with booster recovery and reuse. Per the landing photos above, it’s difficult to tell a Falcon Heavy center core apart from a normal Falcon 9 booster, but the small visible changes are just the tips of several icebergs. Aside from a slight indication that the center core’s aluminum alloy tank walls are significantly thicker (they are), center cores feature a variety of unique mechanisms on their octawebs and interstages. All are involved in the tasks of locking all three boosters together, transferring side booster thrust to the center core, and mechanically separating the side boosters from the center core a few minutes after launch.
Underneath those mechanistic protuberances are the structural optimizations needed for a center core to survive the ordeal of launch. In short, to solve for those new loads, SpaceX wound up building a new rocket. Designing and building a new rocket – especially one as complex as Falcon Heavy’s center core – is immensely challenging, expensive, and time-consuming, particularly for the first few built. Like most complex products, building the first two Falcon Heavy center cores was probably no different. To make things worse, boosters 1 and 2 were based on totally different versions of Falcon 9 (Block 3 vs. Block 5), requiring even more work to further redesign and requalify the modified rocket.
This is where the center core assigned to Falcon Heavy Flight 3 and pictured above comes into play. Built just a few months apart from B1055, the first finished Falcon Heavy Block 5 center core, the newest center core – likely B1057 – is also the first to be built with the same design and manufacturing processes used on its predecessor. In other words, SpaceX can at long last begin serial production of Falcon Heavy center cores, allowing its engineering, production, test, and launch staff to finally get far more accustomed to the unique hardware.
Given Falcon Heavy’s healthy and growing manifest of 5-6 launches, SpaceX will probably need to build several additional Block 5 center cores over the next several years, hopefully resulting in a more refined flow for production, testing, and refurbishment. B1057 will be an excellent candidate for the first reused Falcon Heavy center core thanks to STP-2’s lightweight nature and an extremely gentle landing trajectory. With respect to Flight 3’s schedule, Crew Dragon’s April 20th explosion means that Falcon Heavy will have Pad 39A all to itself for many months to come. Truly the epitome of bittersweet, no doubt, but it does improve the odds that Falcon Heavy’s June 22nd STP-2 launch target will hold.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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
