News
SpaceX’s first orbital-class Starship stretches ‘wings’ ahead of Raptor installation
SpaceX’s first orbital-class Starship prototype was spotted stretching its ‘wings’ on Sunday after completing a successful cryogenic proof test late last week.
While minor relative to almost any other testing milestone, the small step still serves as a reminder that the end goal of Ship 20’s test campaign is a launch on Super Heavy to orbital altitudes and velocities. If that launch goes more or less according to plan, Starship will then attempt to survive an orbital-class reentry for the first time, subjecting it to extreme heat and putting its many thousands of heat shield tiles through their most daunting challenge yet. Dozens of things could (and probably will) go wrong, while almost every system aboard must work perfectly to ensure that Starship makes it through reentry in one piece.
And even if all of that occurs as planned with no major issues, those same systems will still need to hold on for several more minutes to perform a freefall, engine reignition, flip, and landing maneuver that only two other Starship prototypes have completed. As it so happens, one of those crucial systems is Starship’s flaps.
Outfitted with actuators powered by Tesla Model 3/Y motors and a pair of Model S batteries, Starship’s four large ‘flaps’ are only capable of simple flapping motions. While they may look the part, Starship flaps aren’t wings and are specifically designed not to produce lift. Instead, in support of Starship’s unusual descent profile, they act more like the hands and legs of a skydiver (particularly one in a wingsuit), allowing ships to control their pitch, attitude, and roll while freefalling belly-down to the ground. In theory, that allows Starship to gain practically all of the benefit of a structural wing like that on the Space Shuttle but for a far lower mass penalty.
Instead of elegantly slowing down with wings, Starship uses its flaps to create as much drag as possible during descent, slowing down to a terminal velocity around 100 m/s (~225 mph) or less. Using a freefall trajectory and flaps incapable of generating lift does likely come at the cost of “crossrange performance,” referring to how far Starship can travel horizontally in Earth’s atmosphere after reentry. However, significant crossrange performance is almost entirely irrelevant outside of Cold War paranoia like the kind that NASA let influence the Shuttle’s design to an ultimately catastrophic degree. Landing vertically also precludes the need for exceptionally long, expensive runways like those the Shuttle needed.
Aside from allowing it to navigate to a small vertical landing pad (or massive ‘Mechazilla’ catch tower), Starship’s flaps are also important for controlling vehicle orientation and heading during reentry itself. To fill that role, those flaps will have to be able to actuate across their full range of motion during reentry, as Starship’s hypersonic assault against the thin upper atmosphere creates a flood of superheated plasma that wants nothing more to find the gaps in its heat shield. Shuttle engineers had to deal with the same issue, ultimately designing complex seals that would allow the vehicle’s wing and body flaps to actuate during reentry without allowing superheated plasma to leak inside and damage their fragile mechanisms or structure.
Although Starship does have the benefit of relying on steel – not aluminum – for almost all of its structures, it still has to grapple with the same challenges of shielding sensitive electronics, actuators, motors, and more from the reentry onslaught that its heat shield and steel structure are designed to survive.
Half-covered in heat shield tiles, it’s not clear how SpaceX plans to seal off the more sensitive, exposed components of each flap’s actuation mechanism – including motors, cabling, and the hinge itself. Based on what’s visible, Starship’s flaps and the cradle-like ‘aerosurfaces’ they slot into do have very tight tolerances and may rely on some felt-like ceramic wool or TPS blanket to seal the tiny remaining gaps. With small enough gaps, a hypersonic airstream can behave as if there are no gaps at all, suggesting that that might be SpaceX’s preferred approach to sealing Starship flaps.
Up next on Starship S20’s path to launch is the reinstallation of 3-6 Raptor engines (for the third time) ahead of a crucial static fire test campaign that could begin as early as Thursday, October 7th. Likely beginning with 1-3 Raptors, SpaceX will perform an unknown number of static fire tests, ultimately culminating in the first ignition of 4, 5, and 6 engines on any Starship prototype. If all goes well, that testing will also mark the first time Raptor Vacuum has been ignited on a Starship prototype and the first time SpaceX has ignited multiple Raptor variants (sea level and vacuum, in this case) on the same vehicle. Stay tuned for updates on engine installation.
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
