Connect with us

News

SpaceX Falcon 9 booster spied on highway as triple-satellite launch moves right

Reddit user intamin1 spotted a Falcon 9 booster northbound between Hawthorne and Vandenberg on Jan 22. (Reddit /u/intamin1)

Published

on

A SpaceX Falcon 9 booster was spotted heading north from the company’s Hawthorne, California factory on January 22nd, signifying a likely shipment of the flight-proven rocket that will help launch Canada’s trio of Radarsat Constellation Mission satellites.

Delayed from mid-February to early March 2019 after an unplanned landing anomaly damaged the Falcon 9 originally assigned to the mission, the shipment of a different booster to Vandenberg Air Force Base (VAFB) helps to narrow down the rocket now likeliest to launch the Canadian Space Agency’s (CSA) radar satellite constellation.

https://twitter.com/GoForStaging/status/1088174203298230272

Do the Booster Shuffle!

Thanks to a hydraulic pump failure that led Falcon 9 B1050 to land (albeit softly and in one piece) in the Atlantic Ocean last December, the imminent launch of two booster-dense Falcon Heavy missions, and the thus far schedule-shy orbital launch debut of Crew Dragon, SpaceX’s fleet of available boosters – all flight-proven – can be succinctly summarized as “B1046 thru B1049”.

B1050’s future is uncertain after suffering a smashed interstage and soaking in salt water for several days, while B1051 is definitively assigned to Crew Dragon’s orbital launch debut, known as Demo-1 (DM-1). Falcon 9 B1052 and B1053 are unknown quantities and B1054 was expended after a high-value US Air Force launch, also SpaceX’s final mission of 2018. It’s probably safe to bet that B1052, B1053, and B1055 will be the next three boosters to support a Falcon Heavy launch (or two), currently NET March and April 2019. All three of those Falcon Heavy (FH) boosters have completed static fire tests in Texas and both side boosters arrived at SpaceX’s Florida facilities within the last ~6 weeks.

 

Advertisement
-

Assuming that Falcon Heavy Flight 2 and 3 use the same exact boosters, SpaceX production technicians and engineers may already be nearing the completion of another Falcon 9 booster (B1056, presumably) at the Hawthorne factory, although they are likely 1-2 weeks away from that milestone. If, Falcon Heavy Flight 3 (presumed to be the USAF’s STP-2 mission) does not reuse all three first stage boosters from Flight 2 (commercial payload Arabsat 6A), then Hawthorne will have to build, ship, and test anywhere from 1-3 additional boosters between now and April 2019. In the latter scenario, all unflown – mid-build or completed – Falcon boosters would be ‘claimed’ between now and March or April.

Put in another way, short of opting for a delay that could stretch 1-4 months or longer, the Canadian Space Agency (CSA) and Radarsat prime contractor MDA will have to accept one of SpaceX’s flight-proven Falcon 9s.

Falcons on wheels

Thanks to SpaceX’s trusty and well-worn method of using good old trucks and roads to transport Falcon 9 and Heavy boosters, upper stages, fairings, landing legs, and much more cross-country, spaceflight fans have long taken advantage of opportunities – rare and fleeting as they might be – to spot and track SpaceX hardware on public roads. Put simply, a lot of people are excited about SpaceX or are at least familiar and curious enough to know someone to share a photo or observation with. As a result, the community averages dozens of ‘core spottings’ per year. With a little intuition, the process of elimination, a few sources, and some wild guesses, this allows unofficial fans to (very roughly) paint a picture of SpaceX’s fleet of rockets.

 

For example, the Falcon 9 spotted in Valencia, CA on January 22nd by Reddit user intamin1 could theoretically be any SpaceX booster currently in existence. By knowing the rough state of SpaceX’s fleet (as described above) and observing that the booster was northbound between Hawthorne, CA (the factory) and Vandenberg Air Force Base (VAFB) on Jan 22, a great deal can be intuited. Bound for SpaceX’s West Coast launch complex (SLC-4), it ought to be flightworthy. Knowing that a Falcon Heavy center booster was on SpaceX’s McGregor, Texas static fire stand on January 10th means that the spotted booster can’t (or at least shouldn’t) be coming from Texas, as Falcon Heavy has no known launches planned from VAFB. The process of testing, inspecting, and preparing Falcon boosters for cross-country shipment is also not easily rushed.

On the East Coast, SpaceX needs to launch communications satellite PSN-6 and Spaceflight rideshare GTO-1 in mid to late February. With no new boosters expected to be easily available for months and PSN-6/GTO-1 already entering into the phases of payload fueling, integration, and fairing encapsulation, it can be all but guaranteed that a flight-proven booster was assigned to the mission months ago and is now nearly ready for its third flight somewhere in Cape Canaveral, FL.

Advertisement
-
SpaceX manufactures Falcon 9 and Heavy at its Hawthorne, CA factory. (SpaceX)

Given that B1046 and B1049 are on the West Coast after conducting launches from VAFB and that B1050 is out of circulation for the time being, only B1047 and B1048 remain (in theory) on the East Coast, both having flown two missions. B1048 was recently spotted and confirmed in photos of SpaceX’s Pad 39A integration hangar, although Falcon 9 B1051 and the first orbit-ready Crew Dragon were the center of attention.

B1047 completed its second launch in mid-November 2018 and returned to one of SpaceX’s Florida hangars for refurbishment around Nov 21. Unless any number of locals and bystanders somehow missed it, neither booster has left the Cape since arriving. Meanwhile, B1048 is currently the best-known candidate at hand for SpaceX’s Crew Dragon In-Flight Abort (IFA) test, expected to occur no earlier than spring 2019 and entirely dependent upon the successful launch, reentry, recovery, and refurbishment of the DM-1 capsule to proceed. As a result, the only booster that is realistically available for PSN-6/GTO-1 is Falcon 9 B1047 for what would be its third launch.

Assuming B1048 did not manage to make it from Cape Canaveral to Central California without a single spotting, the only rockets available for the RCM mission are B1046 and B1049. B1049 completed its second launch – Iridium-8 – just weeks ago and returned by drone ship to Port of LA on January 13th, whereas Falcon 9 B1046 – after completing its historic third launch – completed recovery and was snug in a Hawthorne, CA refurbishment bay by December 17th, 2018. Going off of Occam’s Razor, B1046 is the clear victor for the launch of RCM, although a ~60-90-day turnaround for the already thrice-flown booster could be a stretch. B1049, however, would have barely a single month for refurbishment and inspections.

In the last week or two, RCM stakeholders were provided an updated launch target, delaying the mission by approximately two weeks to a window that begins February 28th with the implication being that the launch is now expected NET early March. If that date is recent and from SpaceX, B1046 is the most practical option, with B1049 thus filling its refurbishment bay in Hawthorne, CA around the same day. If a risk of a 30-day or greater delay is tolerable for CSA and MDA, then B1049.3 would likely be a more optimal fit for their risk tolerance profile. Time will tell!

Advertisement
-

Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes!

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

Elon Musk

Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash

An Amazon cargo plane crash near Miami’s airport stopped feet from dozens of Tesla Cybercabs.

Published

on

By

Photorealistic depiction of the Amazon Prime plane crash in Miami on Sep 3, 2026 near a fleet of Tesla Cybercab
Photorealistic depiction of the Amazon Prime plane crash in Miami on Sep 3, 2026 near a fleet of Tesla Cybercab

An Amazon Prime Air Boeing 767 cargo jet overran the runway at Miami International Airport on Sunday afternoon, killing five people and injuring five more. The jet, operated by North Carolina based carrier 21 Air as Flight 7598, touched down around 2 p.m. after arriving from San Juan, Puerto Rico, then crossed the airport perimeter, plowed across NW 67th Avenue and struck multiple vehicles before catching fire, according to the Associated Press.

Photos and video from the scene show the aircraft’s nose stopped within meters of a fenced staging lot holding dozens of gold painted Tesla Cybercabs, the steering wheel free robotaxi Tesla began putting on public roads in Austin last week. Miami-Dade Fire Rescue has confirmed the plane struck “multiple vehicles” but has not said whether any Cybercabs were among them, and neither Tesla nor airport officials have addressed the fleet directly.

The Cybercabs had not yet entered commercial service in Miami. Tesla’s existing Robotaxi operation there runs on modified Model Y vehicles and has been unsupervised since Ashok Elluswamy confirmed the detail on X in July.


Elon Musk offered the briefest of reactions. Replying to a Zero Hedge post about the Cybercabs sitting so close to the wreckage, he wrote a single word: “Weird.” He has not commented further, and Tesla has not issued a statement.

The timing puts Tesla’s newest vehicle near an unrelated but highly visible tragedy just days after its Austin debut, a launch that had already drawn scrutiny from federal regulators. The National Highway Traffic Safety Administration opened an audit how Tesla certified the Cybercab as compliant with federal vehicle safety standards, a process Teslarati covered after the vehicle’s September 3 launch event. That inquiry concerns the car’s lack of a steering wheel and pedals, not the Miami crash.

Advertisement
-

Investigators from the FAA and NTSB are focused on the plane, not the parking lot beside it. Flight data reviewed by outlets including Simple Flying show the 767 touched down around 170 knots, well above the 135 to 140 knot range typical for the aircraft, though investigators have not determined a cause. Amazon said it is working with authorities and that its priority is the safety of everyone affected.

Whether any Cybercabs were damaged, and what Tesla plans for the fleet parked near one of the country’s busiest airports, remain open questions.

Continue Reading

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.

Advertisement
-

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.

Advertisement
-

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.

Advertisement
-
Continue Reading