News
SpaceX installs Starship Mk1 rocket’s flaps for the second time in build-up to flight debut
A little over a month after SpaceX CEO Elon Musk presented an update on Starship in Boca Chica, Texas and technicians dressed the rocket up for the show, SpaceX has begun to install Starship Mk1’s flaps for the second time.
This time, with any luck, those flaps are here to stay until Starship Mk1’s inaugural launch debut, an ambitious flight test with a target altitude of 20 km (12 mi).
Around the second half of September, SpaceX technicians appeared to begin working around the clock to fully assemble Starship, outfitting the exterior with the beginnings of plumbing, power lines, and avionics harnesses, stacking the Mk1 prototype’s two halves, and installing the vehicle’s large fore and aft flaps. During SpaceX CEO Elon Musk’s September 28th Starship update, what looked to be the largely finished Starship Mk1 served as the main backdrop – an undeniably impressive one, at that.
As would soon become clear, SpaceX’s September 2019 Starship Mk1 integration was actually more of a mock-assembly – all the parts involved appear to genuinely be real flight hardware, but almost all of it was only temporarily attached to Starship to give the partial appearance of a finished ship. By October 1st, technicians began removing Starship Mk1’s four flaps, flap shrouds, and leg shrouds, finally culminating in the separation of the rocket prototype’s upper and lower halves.
The fact that neither Musk or SpaceX spokespersons noted that Starship wasn’t actually complete is at least a little unsavory, although it’s admittedly unsurprising given CEO Elon Musk’s known affinity for grand gestures and events. On a positive note, Starship’s mock-assembly likely served as an excellent learning experience for the Boca Chica team and thankfully only seems to have caused a week or two of delay.
Rapid progress in Boca Chica
Despite the mild disruption of dressing Starship Mk1 up for Musk’s presentation, SpaceX Boca Chica has made a huge amount of progress in the five weeks since. Barely three weeks after the rocket’s forward flaps (canards) were removed, SpaceX technicians began the reinstallation process with one major visible difference: a massive motorcycle-sized actuator.
On the first round of installations-for-show, Starship Mk1’s flaps featured no such mechanism, confirming suspicions that much of the hardware installed at the last second was not quite finished or was only being installed for Musk (and practice). The appearance of a previously unseen actuator mechanism on the first reinstalled canard suggests that this time around, SpaceX is installing Starship’s flaps with their final purpose of controlling Starship’s free-fall in mind.
Instead of copying Falcon 9’s proven method of vertical launch and vertical landing, SpaceX is taking a more radical approach with Starship that will see the spacecraft reenter Earth’s atmosphere belly-first, slow its forward speed to near-zero, and fall directly down for approximately 25 km (15.5 mi), using its flaps like a skydiver’s limbs. Perhaps just a few hundred meters above the ground, Starship will finally perform an aggressive flip maneuver, igniting its Raptors while sideways, swerving to neutralize that horizontal velocity, and finally landing on six small legs.
In this sense, although they certainly look the part, Starship’s aerodynamic control surfaces are very explicitly not wings and are instead meant to interact with the atmosphere at an almost 90-degree angle of attack (AoA). In line with that strategy, they only have to actuate with a single degree of freedom, drastically simplifying Starship’s control surfaces.
Similar to Starship Mk1’s newly filled-out canard actuators, SpaceX technicians have installed two massive hinges/mounts for Starship’s larger after flaps. Aft flap installation will likely start as soon as SpaceX technicians have installed the bulk of Starship Mk1’s external plumbing and wiring, a milestone that appears to be fast approaching.
Starship Mk1’s lower half was unexpectedly moved about a mile to SpaceX’s nearby launch facilities prior to the installation of its nose section, meaning that SpaceX will likely have to transport the nose to the launch pad for final mating. It’s unclear what tests SpaceX specifically plans to kick off Starship Mk1’s pre-flight preparations with, but it’s safe to assume that the most imminent milestone is a wet dress rehearsal (WDR), possibly preceded by a tank proof test.
The latter procedure would be designed to prove that Starship Mk1’s pressure vessel is both leakproof and structurally sound and would nominally involve filling the spacecraft’s tanks with a neutral fluid (likely water or liquid nitrogen). A WDR would see SpaceX load Starship as if preparing for launch (requiring liquid oxygen, methane, nitrogen, and helium) but stopping just prior to the engine ignition and liftoff that would otherwise follow. Although unlikely, a WDR could result in a massive fire or explosion if Starship were to lose structural integrity during the test, which is why the aforementioned neutral testing is typically performed first when handling brand new launch vehicles.
Finally, assuming Starship Mk1 successfully passes the above tests, SpaceX will use the vehicle to perform Raptor’s first triple-engine static fire test. That static fire will likely be the final major test activity before SpaceX readies Starship Mk1 for its 20-km flight debut, which will serve as a more or less full-fidelity test of Starship’s exotic skydiver-like landing.
Regardless of how exactly Starship Mk1’s imminent test campaign will play out, SpaceX has road closures scheduled on November 7th, 8th, and 12th. Right now, it’s anyone’s guess what is planned for Thursday and Friday, but it could potentially involve a tank proof test, launch pad checkouts, propellant loading, or something more benign, like transporting Starship’s nose section to the pad for final installation. Stay tuned!
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Elon Musk
Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash
An Amazon cargo plane crash near Miami’s airport stopped feet from dozens of Tesla Cybercabs.
An Amazon Prime Air Boeing 767 cargo jet overran the runway at Miami International Airport on Sunday afternoon, killing five people and injuring five more. The jet, operated by North Carolina based carrier 21 Air as Flight 7598, touched down around 2 p.m. after arriving from San Juan, Puerto Rico, then crossed the airport perimeter, plowed across NW 67th Avenue and struck multiple vehicles before catching fire, according to the Associated Press.
Photos and video from the scene show the aircraft’s nose stopped within meters of a fenced staging lot holding dozens of gold painted Tesla Cybercabs, the steering wheel free robotaxi Tesla began putting on public roads in Austin last week. Miami-Dade Fire Rescue has confirmed the plane struck “multiple vehicles” but has not said whether any Cybercabs were among them, and neither Tesla nor airport officials have addressed the fleet directly.
The Cybercabs had not yet entered commercial service in Miami. Tesla’s existing Robotaxi operation there runs on modified Model Y vehicles and has been unsupervised since Ashok Elluswamy confirmed the detail on X in July.
Footage of the plane crash from earlier today | #ONLYinDADE pic.twitter.com/iGoOtnd6cD
— ONLY in DADE (@ONLYinDADE) September 6, 2026
Elon Musk offered the briefest of reactions. Replying to a Zero Hedge post about the Cybercabs sitting so close to the wreckage, he wrote a single word: “Weird.” He has not commented further, and Tesla has not issued a statement.
The timing puts Tesla’s newest vehicle near an unrelated but highly visible tragedy just days after its Austin debut, a launch that had already drawn scrutiny from federal regulators. The National Highway Traffic Safety Administration opened an audit how Tesla certified the Cybercab as compliant with federal vehicle safety standards, a process Teslarati covered after the vehicle’s September 3 launch event. That inquiry concerns the car’s lack of a steering wheel and pedals, not the Miami crash.
Investigators from the FAA and NTSB are focused on the plane, not the parking lot beside it. Flight data reviewed by outlets including Simple Flying show the 767 touched down around 170 knots, well above the 135 to 140 knot range typical for the aircraft, though investigators have not determined a cause. Amazon said it is working with authorities and that its priority is the safety of everyone affected.
Whether any Cybercabs were damaged, and what Tesla plans for the fleet parked near one of the country’s busiest airports, remain open questions.
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 Cybercabs narrowly miss deadly Amazon cargo plane crash
Tesla crosses major Unsupervised Self-Driving milestone
