Connect with us

News

SpaceX go for Starlink launch, landing as ULA rocket delays persist

Falcon 9 B1058 (pictured here on July 20th) is scheduled to launch Starlink-12 later this morning. (Richard Angle)

Published

on

SpaceX is on track for Falcon 9’s latest Starlink launch and landing later today as delays continue to hamper a United Launch Alliance (ULA) rocket meant to lift off more than a month ago.

In fact, an almost identical scenario played out a month ago as SpaceX and ULA coincidentally aligned to attempt two launches less than a day apart. The pad hardware supporting ULA’s Delta IV Heavy NROL-44 mission suffered several delays on August 26th and 27th, followed by a dramatic post-ignition launch abort on August 29th. Throughout, SpaceX effectively had to sit on its hands and wait for permission to launch Falcon 9’s SAOCOM 1B mission. Historically, it’s been safe to assume that a ULA mission – particularly one like NROL-44 – would unilaterally take precedence over a SpaceX launch, forcing the company to wait indefinitely until the range was clear.

Instead, in a major twist, SpaceX received permission to launch – and ultimately did launch – SAOCOM 1B on August 30th with ULA’s Delta IV Heavy and its multibillion-dollar NROL-44 payload still on the launch pad. In essence, one or several stakeholders in the military mission have become confident enough in the reliability of SpaceX’s rockets to no longer perceive a nearby Falcon launch as a major risk. Now, just a month after the development, SpaceX appears to be on track to repeat the feat.

Falcon 9 booster B1058 will support Starlink-12 on its third flight. (Richard Angle)

Three days after SAOCOM 1B lifted off from Cape Canaveral Air Force Station (CCAFS) Launch Complex 40 (LC-40), a separate Falcon 9 rocket launched SpaceX’s 12th Starlink mission (Starlink-11) from Kennedy Space Center (KSC) Launch Complex 39A (Pad 39A). Starlink-12 is also scheduled to launch no earlier than (NET) 10:22 am EDT (14:22 UTC), September 28th from Pad 39A, a bit less than six miles (9.5 km) north of the ULA rocket and NROL-44 satellite at LC-37.

SAOCOM 1B was such a surprise because the unique southerly trajectory saw Falcon 9 fly almost directly above LC-37, meaning that an in-flight failure could have very likely showered ULA’s pad, rocket, and payload with debris. LC-40, however, is just a little over two miles (3.5 km) north of LC-37. In other words, a Starlink launch heading northeast from Pad 39A is clearly of little concern to ULA or the NROL-44 launch customer, particularly after SAOCOM 1B was allowed to launch under far riskier conditions.

Falcon 9 B1060 lifts off for the first time with the US military’s GPS III SV03 satellite. (Richard Angle)

Instead, the real test of the SAOCOM 1B precedent will come when SpaceX prepares for the mission scheduled after Starlink-12 – the company’s third launch of an upgraded GPS III satellite (SV04) for the US military. As of now, ULA’s next NROL-44 launch attempt is tentatively scheduled around midnight (~04:00 UTC) on September 29th. Shortly thereafter, Falcon 9 is scheduled to launch GPS III SV04 (from LC-40) as early as 9:55 pm EDT (01:55 UTC) that same day.

Given the sheer number of difficulties ULA has had with LC-37 pad systems on this launch attempt, it’s reasonable to assume that NROL-44 will slip beyond September 29th. If that happens, stakeholders will once again have to decide if SpaceX can launch two miles to the north or has to wait for ULA. Either way, tune in tomorrow morning to catch SpaceX’s Starlink-12 launch webcast. Weather at Kennedy Space Center is currently 60% go for launch.

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

Advertisement
-

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