News
SpaceX rapidly constructing Starship’s first Florida launch pad and tower
After restarting work on the project a few months ago, SpaceX appears to have gotten back up to speed and begun to make rapid progress on the construction of Starship’s first Florida launch pad and tower.
Located at NASA’s Kennedy Space Center (KSC) Launch Complex 39A facilities, SpaceX has intended to construct a Starship launch site there for several years. A serious attempt was made in late 2019 but SpaceX soon abandoned the effort and redirected its energy towards Starship prototyping and a much different launch pad design. Two years later, SpaceX’s second attempt shares only a little in common with the first. Both are to be located within the eastern half of Pad 39A’s shield-like footprint, although the specific location of the tower and launch mount has been modified. If this attempt comes to fruition, Starship’s first East Coast launch facilities will still sit just a few hundred feet away from the only SpaceX pad capable of launching Crew Dragon, Cargo Dragon, or Falcon Heavy.
Beyond those two characteristics, SpaceX’s second attempt is almost entirely different.
Instead of continuing with an older launch pad design, Starship’s 39A facilities will likely be close to a direct copy of Starbase’s first orbital launch site (OLS), which SpaceX began constructing in earnest in late 2020. It’s safe to assume that some lessons have been learned from Starbase OLS construction and that some modifications will be made to the Florida pad’s design, but no obvious changes are thus far visible.
Most of the visible work SpaceX has done this year centers around the company’s KSC-based Roberts Road facilities, where it has built a major Falcon processing facility and a staging yard for Starship pad construction and broken ground on a massive East Coast Starship factory. At that staging yard, SpaceX began assembling prefabricated sections of Starship’s Pad 39A ‘launch tower’ around March 10th after tower parts began arriving at KSC sometime in February. Within two weeks, SpaceX had completed the basic structure of two tower sections. Another two more weeks after that, around April 11th, a third section had reached a similar level of completion and SpaceX had begun assembling a fourth.
Compared to SpaceX’s Starbase tower assembly, Florida Starship work appears to be proceeding at a similar pace. SpaceX began assembling the fourth Florida tower section about 30 days after starting the first, while Starbase took about 25 days to reach the same point. However, SpaceX does appear to be taking a slightly different approach for Pad 39A. On top of tower section assembly, SpaceX is constructing an extra four sets of the small concrete foundations and steel frames each tower section is assembled on, implying that Starship’s Florida launch tower could be almost entirely prefabricated before SpaceX begins to combine those sections.
That differs from Starbase, where SpaceX rarely constructed more than two or three tower sections at a time before removing and stacking each completed section and beginning to assemble the next on the same foundation and jig. However, while undeniably efficient, SpaceX workers then had to spend months outfitting the tower with plumbing, wiring, additional structure, and more. It’s likely that SpaceX has concluded that it’s better to do as much of that work as possible before the tower is assembled, in which case each Florida section may end up spending more time on the ground. Given the obvious challenges imposed by attempting a major construction project at an active, one-of-a-kind launch pad like LC-39A, it would make even more sense for SpaceX to want to complete as much work as possible before moving Starship pad hardware into the line of fire.
Nonetheless, work will still have to be done at the pad itself. In recent weeks, SpaceX has made significant progress on the foundations 39A’s Starship launch tower and mount require. The bottom half of the concrete base that each steel tower section will eventually sit on has also progressed rapidly. All told, SpaceX is will on its way to replicating Starbase’s orbital Starship launch site on the East Coast, hopefully ensuring that Starship will be able to begin orbital test flights within the next 6-12 months even if the company’s Starbase environmental review continues to be bogged down by bureaucracy.
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
