News
SpaceX’s partial Falcon 9 landing failure could delay next West Coast launch
According to statements made by the Canadian Space Agency (CSA) and media outlet CBC, the launch of the agency’s next-generation Radarsat Constellation Mission (RCM) – a trio of Earth observation satellites weighing >4200 kg (9300 lbs) – has been “postponed … indefinitely” as a consequence of SpaceX’s first failed Falcon 9 booster landing since 2016.
Offering a rare glimpse into some of the extensive planning that goes on behind the scenes to make commercial rocket launches happen, CSA has indicated that the booster it planned to launch on – Falcon 9 B1050 – suffered an untimely (partial) demise during a recovery attempt shortly after successfully launching the CRS-16 Cargo Dragon mission on December 5th, 2018. While the booster shockingly was returned to dry land mostly intact after landing in the Atlantic, SpaceX and CSA must now settle on a different Falcon 9 to launch the mission.
A problem with a SpaceX booster rocket has postponed the launch of a $1 billion Canadian satellite program indefinitely. https://t.co/45qirdId5j @DeanBeeby
— CBC News (@CBCNews) January 15, 2019
Goldilocks and the Falcon boosters
While it doesn’t look like there are only three possible rocket options for the Radarsat constellation and SpaceX to choose from, the situation of picking a new booster this late in the launch flow is far less simple than it might initially seem. First and foremost, SpaceX likely needs to do its best to accommodate the preferences of customers CSA and MDA (MacDonald, Dettwiler and Associates Ltd.) regardless of how disruptive they may be. Originally targeted for sometime in November 2018, RCM’s launch slipped several months to the second half of February 2019 due to what CSA described as “higher priority missions [for]the US Government and a backlog of launches from…Vandenberg” late last year.
While that alone does not point directly towards any obvious explanations, CBC reporter Dean Beeby’s implication that the mission’s launch is now “postponed…indefinitely” offers a hint of an answer, although it could also be manufactured hyperbole where there actually is none. If CSA actually indicated that the launch is now postponed indefinitely, the only clear explanation for a launch delay greater than a month or so as a result of Falcon 9 B1050’s unplanned unavailability would lie in some unique aspect of that particular Falcon 9 booster.
Although each rocket SpaceX builds can be quite different from each other in terms of general quirks and bugs, the only obvious difference between B1050 and any other flight-proven Falcon 9 booster in SpaceX’s fleet was its low-energy CRS-16 trajectory, something that would have enabled a uniquely gentle reentry and landing shortly after launch. In other words, likely out of heaps of caution and conservatism if it is the case, customers CSA and MDA may have requested (or contractually demanded) that SpaceX launch the Radarsat constellation on a flight-proven Falcon 9 with as little wear and tear as possible, in which case B1050 would have been hard to beat.
“Unfortunately, the landing of [Falcon 9 B1050] was unsuccessful, preventing SpaceX from recuperating the reusable components for the launch of RCM. We continue to work closely with MDA and SpaceX to confirm a launch date for RCM.” – Spokesperson Audrey Barbier, Canadian Space Agency (CSA), 01/15/2019
If the customers remained steadfast in their (speculated) request for a gently-used flight-proven Falcon 9 even after B1050’s partial landing failure, the next most comparable booster would be Falcon 9 B1051 after launching the first orbital Crew Dragon mission sometime no earlier than (NET) February 2019. Aside from B1051, there will be no obvious booster alternative available for at least several months after Crew Dragon’s launch debut, unless NASA requests that its next contracted Cargo Dragon mission (CRS-17) launch on a new Falcon 9 rocket in March 2019.
Engines stabilized rocket spin just in time, enabling an intact landing in water! Ships en route to rescue Falcon. pic.twitter.com/O3h8eCgGJ7
— Elon Musk (@elonmusk) December 5, 2018
Warmer…
If a less lightly-used booster becomes an option for CSA/MDA, there are immediately multiple clear options available as long as SpaceX is will to accept possible delays to subsequent launches to quickly reassign a flight-proven Falcon 9. Falcon 9 B1046 – the first SpaceX rocket ever to launch three orbital-class missions – is being refurbished at SpaceX’s Hawthorne, California facilities a few hundred miles south of Vandenberg. B1047 completed its second successful launch in November 2018 and is being refurbished – along with the twice-flown B1048 – in Cape Canaveral, Florida. Finally, Falcon 9 B1049 completed its second successful launch just days ago (January 11th) and is being processed off of drone ship Just Read The Instructions (JRTI) at this very moment.
B1047 or B1048 have likely been assigned to the imminent NET February 18th launch of Indonesian commsat PSN-6 and SpaceIL’s Beresheet Moon lander, meaning that the best possible option for Radarsat – short of swallowing months of additional delays – is a decision between B1047/B1048 or B1046, with B1049 also a candidate if a slip into March or April is an option. Still, all of those options would require Canada and MDA to fly on a Falcon 9’s third (or fourth) launch, perhaps an unacceptable compromise or perceived risk for certain customers.
-
- Falcon 9 B1046 is processed in Port of LA shortly after its third successful launch and landing, December 2018. (Pauline Acalin)
-
- Falcon 9 B1047 is pictured here beneath an upper stage and satellite Es’hail-2 prior to its second launch. (Tom Cross)
-
- Falcon 9 B1048 landed at LZ-4 after its second launch and is now being refurbished on the opposite coast. (SpaceX)
Meanwhile, schedule pressures have meant that SpaceX is pushing as hard as possible to prepare three new Block 5 Falcon Heavy boosters for the giant rocket’s second and third launches, scheduled as early as March and April 2019. While unconfirmed, it appears that SpaceX may have chosen to manufacture all three of those boosters one after the other, meaning that the company’s Hawthorne factory would have been primarily focused on delivering those rockets for at least 2-3 months start to finish. In short, it does not appear that there is or will be an unflown Falcon 9 booster available for Radarsat anytime soon.
Whether the customers wait for a new booster to be produced, wait for Crew Dragon’s first launch to wrap up, or accept being the third or fourth launch of a well-scorched Falcon 9, RCM’s next published launch target should offer a hint as to how CSA, MDA, and SpaceX ultimately decided to respond to Falcon 9 B1050’s dip in the Atlantic OCean.
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
