News
SpaceX Starship hardware mystery solved amid reports of Florida factory upheaval
A SpaceX Starship hardware mystery has been effectively solved after rocket parts arrived at Port Canaveral and were loaded aboard a transport ship, seemingly preparing for an unexpected journey by sea.
In an unexpected turn of events, SpaceX appears to be preparing to ship major Starship hardware from its Cocoa, Florida facility to a similar worksite in Boca Chica, Texas. Spotted for the first time in a photo taken by local photographer Greg Scott on November 30th, that hardware – at least two large stands and a nearly-complete steel tank dome – abruptly appeared beside SpaceX’s Port Canaveral dock space.
Seemingly within hours of their appearance, new vessel GO Discovery also arrived in Port Canaveral and parked by the same SpaceX docks. Shortly thereafter, workers loaded her with both build stands and a Starship tank dome and secured the surprise cargo. As it turns out, another local SpaceX-follower and prolific photographer/videographer happened to capture the disappearance of both stands and dome from SpaceX’s nearby Cocoa, FL Starship construction facility, where Starship Mk2 and Starship Mk4 were being built.
This neatly ties up the minor mystery of where that hardware went: SpaceX clearly moved all three parts to Port Canaveral, where they have since been loaded on a small supply ship. Two main questions remain, however: why have they been moved to the port and where are they headed?
The band is breaking up
Unfortunately, it appears that both questions can effectively be answered by a report published by YouTube channel “What about it?!”. According to former Cocoa employee that spoke to reporter and channel creator Felix Schlang, SpaceX has reportedly transferred up to 80% of the Starship facility’s workforce to other groups in Florida and Texas. Instead of the friendly internal competition that pitted Cocoa against Boca Chica in the race to first Starship flight, SpaceX is temporarily slowing down its Florida build operations and will redirect as much of its workforce and resources as possible to Boca Chica.
According to Schlang’s source, this will likely result in several months of relative downtime in Florida, while he was also told that Starship Mk2 and Mk4 are now effectively dead before arrival as a result of several challenging and reoccurring technical issues. Starship Mk2 likely shares some significant heritage with Starship Mk1, which lost its top during a pressure test. Roughly two-dozen steel Starship Mk4 rings may also be scrapped after SpaceX’s Florida team could not overcome a technical hurdle. Per the source, many of those single-weld steel rings were slightly different diameters, making it next to impossible to build a sound pressure vessel (i.e. Starship Mk4) with them.
Combining the appearance of Starship hardware on GO Discovery just yesterday and reports of major Cocoa layoffs, it’s all but certain that the Starship components on Discovery are going to head to Boca Chica, Texas. Schlang’s source also indicated that all affected employees were given the option to transfer to Boca Chica or Hawthorne, a prime indication that this abrupt change in plans is more a strategic move than a financial one. With any luck, most affected employees will be able to transfer to Florida pad operations or Boca Chica, although such a major and abrupt change is likely a no-go for anyone with major ties to South Florida.
The Starship dome and stands now likely headed for Boca Chica were built over the course of a month or two in Florida, meaning that they were either built under the impression that they would support Boca Chica’s Starship Mk3 prototype or repurposed after SpaceX decided to pause work in Cocoa. Of note, something like 8-12 of Starship Mk4’s steel rings were able to be stacked and all of those double-rings are still present at SpaceX Cocoa, while a number of single rings were indeed scrapped over the last few weeks. A header tank was also reportedly removed from Starship Mk2’s more or less finished nose section. If any of that hardware is technically viable, there’s a good chance that they may also be shipped to Texas to expedite Starship Mk3 integration.
Ultimately, given how rapidly SpaceX makes and changes decisions, pausing work in Cocoa doesn’t come as much of a surprise. It’s also far from the end of SpaceX’s Florida Starship-building efforts – Schlang indicates that SpaceX will instead focus on a similar facility located within Kennedy Space Center, making the process of building Starships offsite and transporting to Launch Pad 39A far more viable.
With this latest surprise, it also appears that SpaceX is now laser-focused on getting Starship Mk3 ready for South Texas flight testing. Stay tuned for an update on a flurry of recent developments at SpaceX’s Boca Chica Starship facilities.
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
