News
Boeing, NASA attempt Starliner landing after missing intended orbit
During the early morning hours of Friday, December 20th, at Space Launch Complex – 41 at Cape Canaveral Air Force Station United Launch Alliance successfully launched a uniquely configured, rated for human spaceflight Atlas V rocket topped with the Boeing Starliner crew capsule to complete its inaugural Orbital Flight Test to the International Space Station (ISS).
However, following the stunning sunrise launch and successful spacecraft separation, Starliner experienced an anomaly with an automated mission event timer which hindered a crucial orbital insertion burn from being completed.
The missed burn and the resulting domino effect of consequences cut Starliner’s journey short. In a joint media teleconference held Saturday, December 21st including NASA Administrator Jim Bridenstine, Boeing senior vice president of Space and Launch Jim Chilton, and deputy manager of NASA Commercial Crew Steve Stich, it was confirmed that just 48 hours following launch Starliner is expected conclude the test flight and return for a controlled landing at White Sands Missile Range in New Mexico.
Initially, Starliner was expected to spend approximately 8 days docked on orbit with the ISS for a return journey tentatively scheduled to occur on December 28th. The lack of orbital insertion and consequential overuse of fuel consumed by smaller incremental burns performed throughout the day on Friday to place Starliner in a safe orbit all but guaranteed that the spacecraft would miss its opportunity to rendezvous and autonomously dock with the ISS, a pivotal objective of the orbital test flight. A fact that was later confirmed on Twitter by Bridenstine.
During the teleconference, Starliner was described as a healthy spacecraft that had in fact achieved circular safe orbit approximately 250km above sea level, lower than would have been achieved had the initial burn occurred as planned. As docking with the ISS was completely out of reach and Starliner remained under tight constraints of how long it could maintain free orbital flight, Boeing and NASA teams jointly decided to bring Starliner home as soon as possible.
While Starliner remained on orbit Friday and Saturday, flight controllers completed many OFT mission objectives. A number of the achievements were outlined in a statement posted to Boeing’s Starliner updates webpage.
“Entry, descent, and landing is not for the faint of heart.” – Jim Chilton
While many OFT mission objectives were successfully met during the dramatically cut short mission the entire goal of Starliner still remains. After all, Starliner is designed to ferry human astronauts safely to and from the ISS. A huge part of that is re-entering the Earth’s atmosphere and landing under survivable conditions.
Enough of Starliner’s fuel was preserved to afford multiple opportunities to safely land. Two opportunities to land at the planned site of White Sands Space Harbor on the White Sands Missile Range in New Mexico. This location may sound familiar as it is the same location where a different Starliner test capsule recently completed a pad abort test.
NASA and Boeing teams are targeting a landing attempt on Sunday 7:57 am EST (1257 GMT). Should it be needed a backup landing attempt at 3:48 pm EST (848 GMT) in the same location is also available. An anthropomorphic test dummy dressed in Boeing’s recognizable blue spacesuit inside the capsule nicknamed “Rosie the Rocketeer” is wired up with sensors to collect data reflecting the conditions a human astronaut would experience during descent.
NASA will livestream the landing attempt and recovery efforts on NASATV beginning at 5:45 am EST (1045 GMT).
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.
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
