News
SpaceX considers second Crew Dragon launch pad to reduce risk from Starship
Reuters reports that SpaceX has proposed modifying a second Florida launch pad to support Crew Dragon missions after NASA raised concerns about the threat posed by plans to launch Starship out of the only pad currently certified for Dragon.
After more than a year of downtime, SpaceX restarted the construction of an orbital Starship launch site at NASA’s Kennedy Space Center LC-39A pad in late 2021. SpaceX has leased Pad 39A since 2014 and conducted 49 Falcon rocket launches out of the facility since its first use in 2017. Prior to SpaceX’s lease, Pad 39A supported 82 Space Shuttle launches from 1981 to 2011 and every Apollo Program launch to the Moon in the 1960s and 1970s, making it one of the most storied and well-used launch sites in the history of US spaceflight.
In 2018, Pad 39A began supporting launches of SpaceX’s Falcon Heavy, which was and still is the most powerful and capable rocket currently in operation. In May 2020, a Falcon 9 rocket and Crew Dragon spacecraft lifted off with two NASA astronauts in tow, marking SpaceX’s first human spaceflight and the United States’ first domestic astronaut launch of any kind since 2011. The next era of the historic pad could include Starship, a fully-reusable two-stage rocket that SpaceX has been developing in earnest since the mid-2010s. However, NASA is worried that a failure of that immense and unproven rocket could almost instantly destroy what is currently the only launch pad on Earth capable of launching the space agency’s astronauts to the International Space Station (ISS).
One certainly can’t blame NASA for worrying. In its latest iteration, SpaceX’s Starship 39A launch mount will sit roughly 1000 feet (~300m) East of Pad 39A’s existing Falcon launch facilities, which include a tower and arm that are needed for astronauts and cargo to access and board Crew and Cargo Dragons. The Starship mount is also around 1600 feet (~500m) northeast of Pad 39A’s lone horizontal integration hangar, without which Falcon launch operations would become far more difficult or even impossible.
For the Falcon pad and tower, there is a slight consolation: Starship’s own skyscraper-sized launch tower will be located directly between those Falcon facilities and Starship before and during launches and could partially protect them from any hypothetical blast. The hangar will be fully unprotected, however.
NASA is worried that if a Starship fails before or shortly after launch and explodes at or near its adjacent launch mount, it could destroy or damage the infrastructure the space agency and SpaceX need to launch Crew Dragon to the International Space Station (ISS). At the moment, Boeing – NASA’s second Commercial Crew partner – is likely a year or more away from its first operational astronaut launch, during which Falcon 9 and Crew Dragon will remain a single point of failure that could theoretically sever the space agency’s connection to its own space station at any moment.
In response to NASA’s concern, NASA executive Kathy Lueders – in an interview with Reuters – says that SpaceX has begun working with the agency on plans to both “harden” Pad 39A and modify its Cape Canaveral Space Force Station (CCSFS) LC-40 pad to support Dragon launches. According to Reuters, however, receiving approval to put those plans into action “could take months.” Depending on how significant the facilities LC-40 would need are, there’s also a chance that SpaceX would need to complete a new FAA environmental review to construct a crew access tower.
Meanwhile, Pad 39A is also the only launch pad in the world capable of supporting Falcon Heavy, which has also become an extremely important rocket for uncrewed NASA spacecraft launches, NASA’s plans to get cargo to its lunar Gateway space station, and to the US military. Modifying one of SpaceX’s other pads to support Falcon Heavy would likely be even harder and take even longer than adding Crew Dragon capabilities to LC-40. In both cases, it’s likely that NASA and the US military would strongly prefer – if they don’t eventually outright require – that SpaceX have backup options already constructed and ready to go before risking the destruction of Pad 39A with its first Starship launch.
39A’s Starship facilities could easily require another 6-12 months of work before they’ll be ready for launch, however, leaving a good amount of time for SpaceX to alleviate the concerns of its US government customers before they might actually start to disrupt plans for East Coast Starship launches.
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
