News
SpaceX preparing giant crane to assemble Starship’s first Florida launch tower
SpaceX has begun staging and assembling parts of a giant crane it will soon need to stack Starship’s first East Coast launch tower and install other major launch pad components.
The presence of the base of that crane at SpaceX’s NASA Kennedy Space Center (KSC) Launch Complex 39A was visually confirmed by NASASpaceflight.com photographers during a weekly aerial tour of the area on June 3rd. Four days later, Teslarati photographer Richard Angle observed more major crane components on their way to Pad 39A, including the crane’s cabin.
More likely than not, the crane SpaceX or its contractor has begun assembling at 39A is a Liebherr LR 11350, the same kind of crane the company used to assemble Starship’s first orbital launch site and tower in South Texas. In fact, given how few LR 11350s there are in existence, it’s entirely possible that it’s the exact same crane. Assembly of that crane began around April 2021 and took a month and a half, at which point it was finally ready to lift an extended boom long enough to assemble a tower almost 500 feet (~150 meters) tall.
Pad 39A’s Starship launch tower is expected to be very similar to Starbase’s, although it will undoubtedly carry over numerous design changes thanks to lessons learned while building and outfitting the first tower. In fact, SpaceX has already assembled five of the nine individual sections that will eventually be stacked to form that tower, and one such change is already obvious. Instead of stacking each tower section as soon as its barebones framework is complete, SpaceX is taking a more methodical approach to its second launch tower. In an apparent attempt to limit the amount of work that needs to be done at Pad 39A itself, each of those segments is being thoroughly outfitted with secondary structures (ladders, doors, walkways, frames, raceways, etc.) before stacking.
SpaceX may even pre-install most of the thousands of feet of plumbing needed to connect a Starship to ground systems located around 90 meters (~300 ft) below it. Once stacked, each section – including all those partial propellant and gas lines – will still need to be joined together, but that process should be far easier than fully installing all the systems the tower needs to do its job. Outfitting Starbase’s launch tower, for example, took SpaceX around half a year and, to some extent, is still ongoing 11 months after the final stack. That likely explains why Starship’s 39A tower section assembly appears to be taking more time. With any luck, partially combining the outfitting and section assembly stages will significantly expedite final assembly, as far less work will need to be done at extreme heights or require a skyscraper-sized crane.
Through Starbase, SpaceX has already demonstrated the ability to stack a Starship launch tower from its unoccupied concrete base to its final height of ~145 meters (~475 ft) in about two months flat. While SpaceX will have to slalom its way around Pad 39A’s busy launch manifest, there’s no reason to believe that Starship’s first Florida launch tower won’t be stacked at least as quickly.
Aside from the arrival of crane parts, SpaceX has also made great progress on the Starship launch site itself. In the last few weeks, the company appears to have completed several significant concrete pours on the tower base. SpaceX has also installed all six of the pedestal-like orbital launch mount’s legs after months of foundation work. Elsewhere at Cape Canaveral, a different team has made excellent progress assembling the massive donut-like platform that will sit on top of those legs. Due to its extreme weight (possibly around 300 metric tons, per Elon Musk’s comments on the Starbase mount), the same LR 11350 crane will also be needed for that major installation milestone.
Plenty of parts are still missing, of course. Four tower sections still need to be assembled. Starship’s first Florida launch tower will need its own set of two ‘chopstick’ arms for lifting and (maybe) catching Starship and Super Heavy, as well as a third swinging quick-disconnect arm to connect Starship to ground systems. Aside from delivering several new tanks, SpaceX has also made no apparent progress on adding a massive methane propellant farm to Pad 39A, and it’s possible that the pad’s oxygen farm will also need to be expanded. Propellant storage has proven to be a major headache for SpaceX at Starbase.
Nonetheless, SpaceX is making great progress on most of the most difficult parts of Starship’s first Florida launch site, and there’s a good chance that just like its launch mount, work on the pad’s tower arms is already underway somewhere offsite. A great deal of work remains to be done but SpaceX is still well on its way to launching Starships out of Kennedy Space Center in the not-too-distant future.
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
