News
SpaceX’s next Falcon Heavy reaches milestone as third booster arrives in FL
A new SpaceX rocket was spotted traveling into Florida yesterday on its way to one of the company’s several Cape Canaveral booster storage and processing hangars. More likely than not, this particular booster is the second Falcon Heavy center core ever built, a heavily modified variant of Falcon 9’s first stage.
With the presumed center core’s arrival, all three Falcon Heavy boosters are now at or near SpaceX Launch Complex 39A, a major step forward for the second flight of the super heavy-lift launch vehicle, currently NET March 2019. Aside from the first stage, it appears that Falcon Heavy Flight 2’s payload fairing may have also arrived at Cape Canaveral around the end of January.
Captured by SpaceX Facebook group member Joshua Murrah on the morning of February 11th, the shrinkwrapped Falcon booster and truck were stopped at a weigh station on the border of Alabama and Florida, a now-common location for core spottings thanks to its adjacency to Mr. Murrah’s daily commute. No more than an 8-10 hour drive from Florida’s East Coast and Kennedy Space Center, the rocket likely arrived at its destination sometime within the last 12 or so hours.
While Falcon Heavy hardware would normally be expected to head straight for SpaceX’s hangar at Pad 39A, the only facility currently capable of launching the triple-booster rocket, the company faces a mild logistical challenge thanks to the terminally delayed launch debut of Crew Dragon. As of now, Crew Dragon, Falcon 9, and 39A’s transporter/erector (T/E) are integrated inside the pad’s hangar, leaving very little space for additional rocket processing as a result of the sheer scale of the T/E. Past photos of SpaceX’s 39A hangar illustrate that it can nominally house 4 or 5 Falcon boosters with ease, but space becomes far more limited once the T/E is rolled inside.
there might actually be juuuust enough room to literally fit them per FH Flight 1 processing pics, but only enough for Falcon Heavy integration if the TE remains outside. Will be very curious to see how SpaceX handles this, it's one hell of a logistical puzzle 😅 pic.twitter.com/D5BFXQnQ3V
— Eric Ralph (@13ericralph31) January 30, 2019
In essence, Falcon Heavy Flight 2 will likely have to wait until Crew Dragon has completed its launch debut before SpaceX technicians and engineers can begin integrating its three boosters and verifying that all is healthy, only the second time SpaceX will have performed those procedures. Crew Dragon’s uncrewed demonstration mission (DM-1) is currently scheduled for NET March 2nd, although there is a high probability that it will slip at least a few more days into March, if not further. Prior to its latest March 2nd launch target, Crew Dragon was expected to launch sometime in mid-to-late January as of December 2018, a date that has effectively remained 30+ days away ever since.
It’s ambiguous what the causes of those delays are and SpaceX and NASA clearly have no interest in directly tackling an explanation, but the most likely reason can be found in a painfully mundane reality: paperwork, worsened by a record-length US goverment shutdown. While both partners are likely culpable in some way, the fact remains that SpaceX has a long history of doing difficult things faster and cheaper than the old guard perceives as possible, while NASA has its own decades-long history of doing difficult things with extreme caution (for better or for worse).
-
- The second (and third) flight of Falcon Heavy is even closer to reality as the first new side booster heads to Florida after finishing static fire tests in Texas. (Reddit /u/e32revelry)
-
- SpaceX Facebook group member Joshua Murrah captured two great photos of the second Falcon Heavy side booster to arrive in Florida in the last month. (Joshua Murrah, 01/17/19)
-
- SpaceX Facebook group member Joshua Murrah also captured what is likely the third Falcon Heavy booster’s Florida arrival. (Joshua Murrah, 02/11/19)
-
- Falcon Heavy ahead of its inaugural launch. (SpaceX)
With any luck, Crew Dragon will successfully launch into orbit for the first time in the first several days of March, leaving enough buffer for SpaceX to rapidly integrate, checkout, and static-fire Falcon Heavy for an operational launch debut – carrying communications satellite Arabsat 6A – near the end of March. If all goes well, Falcon Heavy’s third launch – the USAF’s second Space Test Program mission (STP-2) – could occur as early as April 2019, potentially just a month after Flight 2.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
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 crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
