Connect with us

News

SpaceX Starlink launch suffers last-second scrub, ULA up next [update: double scrub]

ULA's latest Delta IV Heavy launch attempt is up next after a last-second SpaceX scrub. (ULA)

Published

on

Update: ULA has scrubbed today’s NROL-44 launch attempt after the weather at the launch site substantially worsened. The Delta IV Heavy rocket’s next shot at launch is now scheduled no earlier than 11:58 pm EDT (03:58 UTC), Tuesday, September 29th, just two hours after a SpaceX Falcon 9 is scheduled to launch the US military’s fourth upgraded GPS III satellite.

SpaceX’s eleventh Starlink launch of the year was scrubbed ~30 seconds before liftoff by bad weather, likely delaying the mission a few days and leaving ULA’s latest Delta IV Heavy launch attempt next in line.

Scheduled to lift off at 10:22 am EDT on Monday, September 28th, SpaceX’s 12th operational Starlink launch (V1 L12) nearly made it to liftoff before the company called the mission off, prioritizing mission success above all else. Given that SpaceX’s Starlink program puts the company in the unique position of being its own launch customer, the decision to let a relatively mild weather violation delay a Starlink mission by at least a few days is unintuitively encouraging.

It’s no secret that SpaceX has become the most successful private launch company in history and a commercial force to be reckoned with, handily overtaking United Launch Alliance (ULA) and Arianespace to acquire a vast majority of the commercial launch market share. Falcon 9 is on track to become the fastest commercial rocket in history to cross the 100-launch milestone and SpaceX is already well on its way to regularly out-launching entire countries with 20+ missions per year. The single biggest risk facing the company is arguably complacency and an infamous tendency known as “launch fever.”

The first twice-flown Falcon 9 payload fairing half is pictured here shortly before SpaceX scrubbed Starlink-12. (SpaceX)

At the cutting edge of spaceflight, constant, exhaustive vigilance is ultimately the only thing standing between a reliable rocket or spacecraft and catastrophic failure. Perhaps the single biggest threat to that vigilance is the somewhat understandable desire to avoid launch delays – a fact of life for rocketry that nevertheless costs time, money, and (to some) reputation. The term “launch” or “go fever” was originally colloquialized to describe the irresponsible managerial pressure to launch largely responsible for both of NASA’s catastrophic Space Shuttle failures.

Some (if not most) parts of SpaceX almost assuredly would rather avoid launch delays. The fact that the company continues to accept Starlink launch delays and respect Falcon 9’s limits strongly implies that SpaceX has found ways to prevent launch fever while still pushing the envelope of launch cadence and rocket reuse. Starlink-12, for example, was originally meant to launch on September 17th but was delayed ~10 days by strong ocean currents before being scrubbed seconds before launch on September 28th. Combined with the fact that SpaceX is technically free to accept more risk on its own Starlink launches, compounded delays will inevitably test the limits of any organization’s resolve.

Falcon 9 fogs up the camera moments before a scrubbed launch attempt. (SpaceX)

While the argument that SpaceX is technically the only direct stakeholder in Starlink missions is a bad-faith argument that could easily be made to push for increased risk tolerance, it’s only true in a vacuum. A Falcon 9 failure during a Starlink launch would still have major consequences for all of SpaceX’s customers, particularly delaying critical NASA astronaut and US military launches until a lengthy accident investigation is completed. SpaceX executives and managers involved in launch go/no-go decisions clearly understand this and act accordingly.

Starlink-12 will likely be recycled for another launch attempt sometime after ULA’s next Delta IV Heavy launch attempt and probably after SpaceX’s own GPS III SV04 mission for the US military, scheduled no earlier than (NET) 12:02 am EDT (04:02 UTC) and 9:55 pm EDT (01:55 UTC), September 29th, respectively. Catch ULA’s latest NROL-44 launch attempt at the company’s official webcast below.

Advertisement
-

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla crosses major Unsupervised Self-Driving milestone

Published

on

Credit: Tesla

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.

Continue Reading

News

Tesla Robotaxi will be a 24/7 service: here’s when

Published

on

Credit: @AdanGuajardo/X

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.

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.

Continue Reading

News

Tesla Full Self-Driving will now overtake manual driving to avoid disaster

Published

on

Credit: Tesla

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.

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.

Continue Reading