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

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

News

Tesla Full Self-Driving will now overtake manual driving to avoid disaster

Published

on

Credit: Tesla

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.

Advertisement
-

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.

Advertisement
-

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.

Continue Reading

News

Tesla Cybercab launch catches NHTSA’s attention who wants to know more

Published

on

(Credit: Teslarati)

Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.

The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.

NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.

Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)

However, the agency needs more information; it said in a summary:

“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”

It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:

“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”

Advertisement
-

Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.

Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.

In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.

Continue Reading