Connect with us

News

SpaceX’s Falcon 9 and Heavy manifest grows lopsided as launches align for Q4

Published

on

For a variety of reasons both clear or otherwise, a significant number of SpaceX’s Falcon 9 and Falcon Heavy launches initially scheduled near the beginning or middle of the second half of 2018 are all slipping right into October, November, and December.

While communications satellite Telstar 18V’s two-week slip to NET September 8 and SAOCOM-1A’s own several-week tumble to October 7th appear to have their own respective and discernible reasons, namely some sort of range or payload issue (Telstar) and difficulties with the Falcon 9 rocket (SAOCOM), it’s much harder to know why multiple other payloads have slipped into late 2018.

Although the multiple slips and slides of several payloads and much of SpaceX’s H2 2018 launch manifest may be hard to parse alongside the year’s milestone first half, at least two reliable launch manifest sources (SpaceflightNow and one other) more or less independently corroborate the apparent realignment. Explanations, however, are far harder to find – to be expected in the business of space launch. Still, multiple launch delays can be traced to either payload or rocket issues.

Payload-side delays aplenty but rocket-slips, too

Iridium CEO Matt Desch, for example, noted that his company’s Iridium NEXT-8 launch of the constellation’s final 10 satellites is slipping from its original launch date target because of delays preparing the satellites for launch, rather than any issue with SpaceX rocket availability. While not official, the Falcon 9 launch of communications satellite Es’hail-2 has also rapidly jumped from the end of August or early September into Q4 2018 (likely NET October or November), hinting heavily at payload processing delays or technical issues with the complex satellite, as multi-month rocket-side delays would likely preclude interim September and October launches.

Advertisement
-

Meanwhile, at least two of those prospective Q4 2018 SpaceX launches happen to be rideshare-dedicated, meaning that the payload consists of dozens of smaller satellites manifested and organized by a middleman company or agency. These two launches are Spaceflight’s SSO-A launch (~70 satellites) – currently NET November 2018 – and the US Air Force-led STP-2 mission, designed primarily to help SpaceX certify Falcon Heavy for Air Force launches while also placing roughly two dozen smaller satellites into orbit. STP-2 was delayed for multiple years as SpaceX gradually paced towards Falcon Heavy’s first real launch debut (February 2018), but launch delays (currently NET November 30 2018, probably 2019) will likely be caused by some combination of rocket, payload, and pad delays as SpaceX readies for what is essentially the second debut of much different Falcon Heavy.

While likely less a payload-side delay than a mountain-of-tedious-paperwork-and-bureaucracy delay, SpaceX’s NET November 2018 inaugural (uncrewed) demonstration launch of Crew Dragon, NASA scheduling documents published alongside an August 27 Advisory Council presentation suggest that the spacecraft will be ready for launch as early as September, whereas independent sources and visual observations have confirmed that the new Falcon 9 Block 5 booster (B1051) is either near the end or fully done with its McGregor, Texas acceptance testing. One certainly cannot blame SpaceX or NASA for caution at this stage, but the consequently uncertain launch debut of Crew Dragon almost certainly precludes any Falcon Heavy launches from Pad 39A in the interim, including STP-2’s theoretical NET November 30 launch date, which is literally inside Crew Dragon’s “November 2018” launch target.

 

On the other hand, several recent delays of SpaceX’s imminent (-ish) launch of Argentinian Earth observation satellite SAOCOM-1A have been suggested by several employees of the country’s CONAE space agency to be rocket-related, as they understand that the satellite itself is effectively ready to head to orbit at any time. It has yet to be officially confirmed, but it’s understood that Falcon 9 B1048 – previously flown on the launch of Iridium-7 – is being refurbished for SAOCOM-1A, potentially contributing to launch delays as SpaceX cautiously works through the inaugural reuses of some of its very first serial Falcon 9 Block 5 boosters.

Time will soon tell, as launching the roughly 8 to 10 launches tentatively remaining on SpaceX’s 2018 manifest will require extensive reuse of Block 5 boosters if multiple slips into 2019 are to be prevented. Regardless, best of luck to SpaceX’s technicians and engineers as they beat back rocket demons, grapple with uncooperative satellite payloads, and navigate the winding paths of Department of Defense and NASA rocket launch certifications.


For prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket recovery fleet check out our brand new LaunchPad and LandingZone newsletters!

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

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