News
SpaceX, Boeing astronaut spacecraft working towards orbital meet-up in 2020
According to Boeing’s new Starliner testing plan, the spacecraft could potentially meet SpaceX’s own Crew Dragon astronaut spacecraft in orbit at the International Space Station (ISS) later this year.
Following Starliner’s near-catastrophic December 2019 orbital flight test (OFT), Boeing and NASA have finally announced that – at a minimum – a second uncrewed flight test will have to be completed before the company will be allowed to launch astronauts. According to the Washington Post, Starliner’s return to flight is expected to occur no earlier than October or November 2020, 10 or 11 months after it suffered several major software failures during its first spaceflight. While delays to that flight schedule are incredibly likely, it does mean that there’s a chance that SpaceX’s second crewed Crew Dragon launch could coincide with Starliner’s second orbital mission — a first for the two NASA Commercial Crew Program (CCP) providers.
Just one week before NASA and Boeing revealed plans to refly Starliner’s uncrewed flight test, NASA announced that SpaceX’s first operational Crew Dragon launch now has a full four astronauts assigned to it. Scheduled to launch no earlier than Q4 2020, the spacecraft will carry three NASA astronauts and one Japanese (JAXA) astronaut to the ISS, remaining in orbit for at least six months before returning its crew back to Earth. Now, there’s a chance that SpaceX’s first operational Crew Dragon will be joined in orbit by Boeing’s Starliner spacecraft sometime soon after arriving on station.
As previously discussed on Teslarati, Boeing’s Starliner OFT suffered several near-catastrophic close calls in the few days it spent in space, all of which appear to have egregiously shoddy and unqualified software to blame.
“Starliner launched atop a ULA Atlas V rocket on its orbital launch debut (OFT) on December 20th, 2019. Atlas V performed flawlessly but immediately after Starliner separated from the rocket, things went very wrong.
Bad software ultimately caused the spacecraft to perform thousands of uncommanded maneuvering thruster burns, depleting a majority of its propellant before Boeing was able to intervene. Starliner managed to place itself in low Earth orbit (LEO), but by then it had nowhere near enough propellant left to rendezvous and dock with the ISS – one of the most crucial purposes of the flight test. Unable to complete that part of the mission, Boeing instead did a few small tests over the course of 48 hours in orbit before commanding the spacecraft’s reentry and landing on December 22nd.
The Starliner spacecraft also reportedly almost suffered a second major software failure just hours before reentry. According to NASA and Boeing comments in a press conference held only after news of that second failure broke, a second Starliner software bug – caught only because the first failure forced Boeing to double-check its code – could have had far more catastrophic consequences. NASA stated that had the second bug not been caught, some of Starliner’s thruster valves would have been frozen, either entirely preventing or severely hampering the spacecraft’s detached trunk from properly maneuvering in orbit. Apparently, that service module (carrying fuel, abort engines, a solar array, and more) could have crashed into the crew module shortly after detaching.”
Teslarati.com — February 11th, 2020
The only sane response was obviously for NASA to require Boeing to successfully complete a second Orbital Flight Test (OFT), a necessary decision the space agency and card-holder was bizarrely hesitant to acknowledge. Now, almost four months after Starliner was nearly lost on its first orbital flight test, NASA and Boeing have finally stated the obvious and confirmed that a second OFT will be required before astronauts can fly on Starliner. Even then, if things go wrong during OFT2 or Boeing completes the mission but still fails to rectify all faults identified by a joint failure investigation, NASA may still delay the spacecraft’s astronaut launch debut.
SpaceX has undeniably had its own stumbles while developing Crew Dragon, most notably when the first successfully flight-proven spacecraft violently exploded moments before a static fire test in April 2019. SpaceX was able to rectify the responsible design flaws and successfully complete an identical static fire test less than seven months later, followed by a second successful launch less than three months after that. Based on WaPo’s indication that Starliner’s second OFT is scheduled for Q4 2020, Boeing is now anywhere from 12-18 months behind SpaceX with its efforts to launch NASA astronauts to and from the space station. SpaceX successfully completed Crew Dragon’s OFT equivalent in March 2019.
Regardless, if Crew Dragon performs flawlessly during its Demo-2 astronaut launch debut – scheduled no earlier than mid-to-late May – and Boeing’s Starliner OFT2 mission launches on time in Q4 2020, there is a great chance that both spacecraft will be simultaneously docked to the space station. Better circumstances would be unequivocally preferable but it will still mark an important symbolic milestone for NASA’s Commercial Crew Program (CCP) and assured access to the ISS.
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
