News
SpaceX’s Starship Mk1 prototype heads to the launch pad – but why?
SpaceX has transported (half of) its Starship Mk1 prototype to its South Texas launch pad for the first time ever, signifying that the company is about to enter a major new stage of testing.
The move, however, raises the question: why is SpaceX transporting only half of Starship Mk1 to the launch pad?
Following SpaceX CEO Elon Musk’s September 28th presentation on Starship, the spacecraft prototype was partially disassembled, having essentially been mocked up to stand as a backdrop at the event. The impact was fairly minor, taking up no more than a few days of work, but Starship Mk1 remains in two large, separate pieces – a curved nose section and the ship’s cylindrical propellant tank and propulsion section.
A little over a month after Musk’s presentation, SpaceX technicians freed Starship Mk1’s lower tank section from a steel mount and temporarily installed the giant half-spacecraft on framework mounted to a Roll Lift transporter. SpaceX has consistently relied on Roll Lifts for the task of transporting Starship’s massive segments both around and between its Boca Chica, Texas build and launch facilities. This time around, only Starship Mk1’s lower half was loaded onto the transporter before being staged overnight near the main gate of SpaceX’s build site.
Although work continued throughout the night, around dawn on October 30th, transport activity restarted in earnest, with technicians preparing to move Starship. A road closure filed with Cameron County suggested that something would occur on the 30th, with followers speculating that Starship Mk1 would be transported to SpaceX’s South Texas launch pad. As it turned out, that speculation was correct, and (half of) Starship Mk1 was indeed moved to the launch pad and installed atop a new launch mount that was built from scratch in just a few months.
(Half a) Starship on the pad
While it’s undeniably thrilling to see Starship Mk1 head to SpaceX’s Boca Chica launch pad for the first time ever, it remains to be seen why exactly only half of the rocket was transported – no mean feat. Although a great deal of progress has been made over the last month outfitting Starship Mk1 with all the wiring, electronics, plumbing, and other subsystems the prototype will need to function, it’s plainly visible that a significant amount of work remains before Starship will be ready for integrated testing.
Most notably, as pictured above, the launch mount frame is certainly more or less complete, but most of the complex plumbing, wiring, and power equipment it will need to serve its function is not obviously present. There is admittedly a possibility that SpaceX will reuse the ‘quick disconnect’ umbilical ports used by Starhopper on Starship Mk1, but that remains to be seen.
Additionally, Starship Mk1 also has some level of work left before it will be ready for its first propellant loading test, let alone flight. Aside from a large amount of wiring and avionics that still needs to be partially run, harnessed, and connected, Starship’s main liquid oxygen and methane feedlines – needed to fuel the rocket – are largely complete but still unfinished.
There are at least a few obvious possible explanations for SpaceX moving the Starship Mk1 tank section to the launch pad in its partially-finished state. The easiest explanation is that SpaceX wants to perform leak and pressure tests of Starship’s tanks as early as possible, even if that involves testing the rocket without its nose (the host of Mk1’s batteries, power controllers, COPVs, pressurization tanks, and more). It’s not clear that Starship Mk1 is – at present – capable of performing a wet dress rehearsal (WDR), a common aerospace test where a rocket is fully fueled and counts down to launch without actually igniting.
Instead, SpaceX could potentially perform a pressure (or at least leak) test with a neutral gas (or perhaps liquid nitrogen) just to verify that Starship Mk1 is structurally sound before kicking off cryogenic propellant loading. Additionally, it’s possible that SpaceX could get around Mk1’s incomplete propellant feed lines by attaching pad umbilicals directly to the ends of the incomplete feed lines.
At the same time, it’s possible that SpaceX has decided to finish assembling Starship at the launch pad itself, hinted at when a local photographer captured a number of Mk1’s control surfaces and aero covers being moved around shortly after Starship was moved to the pad. Time will tell. For the time being, SpaceX has no more road closures scheduled (meaning no nose section transport) until November 7th and 8th, followed by another on the 12th.
Stay tuned to find out what transpires!
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
