News
(Update: scrubbed) SpaceX’s next Starlink launch to break rocket fairing reuse record
Update: SpaceX says that today’s Starlink-12 launch attempt was scrubbed due to a mysterious “recovery issue.” Liftoff from Kennedy Space Center Pad 39A is now scheduled no earlier than (NET) 1:57 pm EDT (17:57 UTC) on Friday, September 18th.
Prior to the announcement, fairing recovery ship GO Ms. Tree was spotted diverting to a North Carolina port for unknown reasons, leaving twin ship Ms. Chief to recover both fairing halves. Based on bouy data, conditions at the Atlantic Ocean fairing and booster recovery zones appeared to be moderately challenging but far from unreasonable and SpaceX has been happy to point to recovery weather for past launch delays.
SpaceX has revealed that its next Starlink launch will mark a new first for Falcon 9 payload fairing reuse, reaching a milestone that took booster reuse 18 months in less than a year.
Scheduled to lift off no earlier than (NET) 2:19 pm EDT (18:19 UTC) on Thursday, September 17th, the Starlink-12 (v1.0 L12) mission will be SpaceX’s 11th in 2020 alone and 13th overall. If things go according to plan, it could leave SpaceX’s nascent constellation just two or so months away from the beginning of the first public beta tests of Starlink internet service.
Meanwhile, Falcon 9 booster B1058 will be attempting its third launch less than four months after its flight debut, an unprecedented cadence of reuse for SpaceX. Aside from likely ensuring that B1058 becomes the proud holder of SpaceX’s first and second place records for booster turnaround (time between launches), the mission also continues an unexpected trend: the near-extinction of Falcon 9 static fire tests.

SpaceX’s first successful Falcon booster landing happened in December 2015, just a few months shy of five years ago. In March 2017, two years later, SpaceX reused a Falcon 9 booster on an orbital-class launch for the first time in history. Some 21 months after that historic milestone, SpaceX launched the same Falcon 9 booster for the third time, kicking off a relentless series of reusability firsts that continue to be made to this day.
Now, SpaceX says it’s about to launch the same Falcon 9 payload fairing half for the third time in a significant and unexpected first for fairing reuse. Constructed primarily out of a carbon fiber-aluminum honeycomb composite material, Falcon fairings are dramatically more fragile – and reaches much higher altitudes and velocities – than the boosters SpaceX has cut its teeth on recovering and reusing.


Compared to booster reuse, it’s quite the achievement. SpaceX first managed to launch the same Falcon 9 booster three times in December 2018, ~33 months after the first booster reuse. Measured from SpaceX’s first fairing reuse, completed in November 2019 as part of the first Starlink v1.0 launch (Starlink-1), the company will have managed to cross the three-flight fairing reuse barrier less than 11 months later – a full three times faster than SpaceX’s booster reuse program took to achieve the same milestone.
Additionally, prior to SpaceX’s September 16th reveal, it was purely up to speculation whether the company would be able to reuse Falcon fairing halves more than once, particularly when a given fairing half is only fished out of the ocean. If successful, Starlink-12 will prove that Falcon fairing halves can be reused at least three times regardless of whether SpaceX was/is able to catch said halve in a recovery ship’s net.


No more static fires?
Meanwhile, SpaceX appears to be turning a major corner on Falcon 9 launch operations. Of all 93 Falcon 9 launches since the rocket’s June 2010 debut, every single one has been preceded by a combined wet dress rehearsal (WDR) and static fire test a few days or weeks prior to liftoff. Effectively simulating a launch 1:1 up to the exact moment before liftoff, SpaceX has used static fires to verify vehicle health and firewall minor quality assurance lapses for as long as it’s been launching rockets.
In a major operational change that has almost flown under the radar, SpaceX appears to have killed the practice of universal prelaunch static fires beginning with Starlink-8 in June 2020. Including Starlink-8, of the seven launches SpaceX has completed in the last three months, just three (GPS III SV03, Starlink-9, and Starlink-10) included Falcon 9 static fire tests prior to liftoff. A step further, two of the four static fire-free launches were for major commercial missions – not retiring risk on SpaceX’s own Starlink launches, in other words.



As of today, Falcon 9 has completed 65 successful launches since the last catastrophic vehicle failure (Amos-6, September 2016) and 74 consecutively-successful launches if Amos-6 (which never lifted off) is excluded. As of 2020, it’s the most reliable US launch vehicle currently in operation, surpassing ULA’s Atlas V several months ago. In fewer words, it’s not actually surprising (in retrospect) that SpaceX has begun to relax its position on static fires – especially considering that there isn’t another launch provider on Earth that static fires rockets before every launch.
More likely than not, SpaceX will continue to static fire Falcon 9 and Heavy boosters at the launch pad before their flight debuts and upon customer request. If launch or post-flight inspection data offer reason(s) for concern, SpaceX may still choose to static fire boosters out of caution. Additionally, SpaceX shows no signs of ending the practice of performing full booster static fires in McGregor, Texas as part of acceptance testing, still leaving it a step beyond traditional rocket manufacturers, which only static fire individual engines.
Regardless, SpaceX’s 13th Starlink launch will be streamed live as usual, with coverage beginning around 15 minutes prior to liftoff.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
News
Tesla Robotaxi will be a 24/7 service: here’s when
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.
News
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
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.
News
Tesla Cybercab launch catches NHTSA’s attention who wants to know more
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.