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.

Advertisement

 

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 Cybercab stands to gain from new Trump autonomy rules

Published

on

Credit: Teslarati

Tesla Cybercab stands to gain from new rules that the Trump Administration is aiming to enforce on autonomous vehicles. On Thursday, NHTSA, under the Trump Administration’s U.S. Department of Transportation, commenced rulemaking on the Federal Motor Vehicle Safety Standards (FMVSS).

This effort aims to eliminate the mandate for manual brake pedals in vehicles that are designed to be driven exclusively by automated driving systems. This would impact the Tesla Cybercab, which the company has stated would operate without a steering wheel or pedals.

Tesla Cybercab launch is imminent after latest sighting at Giga Texas

The Trump Administration is looking to revise FMVSS No. 135, which requires standard braking systems on light-duty vehicles.

Advertisement

Currently, the regulation requires light-duty cars to use traditional manual braking systems that allow operators to slow the vehicle. With the advent of self-driving in the U.S., these regulations need updating, and these are the changes that could come to FMVSS No. 135:

  • Removes requirements for hand- or foot-operated brake controls for vehicles designed never to be operated by a human. Existing rules still apply to AVs that retain manual controls.
  • All subject vehicles must still meet the same stopping distance performance criteria via alternative testing procedures.
  • While this update ensures AVs can physically stop when commanded, NHTSA is separately developing safety performance requirements for AVs in real-world driving scenarios.
  • NHTSA will continue to use its broad defect enforcement authority to investigate unsafe ADS behavior and oversee recalls.

As autonomy becomes a greater part of passenger travel, these types of rule adjustments will be more than reasonable. It will give manufacturers the ability to self-certify their vehicles and avoid any red tape that could ultimately delay the deployment of these vehicles.

Administrators are also incredibly excited about the opportunity to play a role in the advancement of self-driving vehicles.

“We are at the cusp of the greatest technological revolution in vehicle technology since the innovation of the Model T,” NHTSA Administrator Jonathan Morrison said. “If we want America to lead the way, we have to reimagine our regulatory framework. That’s why under Secretary Sean Duffy’s AV Framework, NHTSA is tearing down pointless barriers to innovative designs while strengthening the fundamental safety requirements that matter and holding AV developers accountable for safe performance.”

The Cybercab entered mass production at Gigafactory Texas in April. Tesla ultimately plans to push the vehicle into its Robotaxi fleet, potentially when frameworks like these are established.

Advertisement
Continue Reading

News

Tesla plans production boost at Giga Berlin following rebound in Europe

Published

on

Credit: Andre Thierig | X

Tesla plans to boost production at its Gigafactory Berlin plant in Germany following a sharp rebound in sales and demand in Europe after a softer 2025.

The plans put Tesla in a better position to compete with strengthening companies in Europe and potentially other markets; demand indicators show Tesla is much better off than in 2025.

Last year was a tough year for Tesla in terms of overall demand in Europe. The company produced over 200,000 vehicles at the German plant last year, a soft figure compared to the 375,000 vehicles Tesla lists as its current capacity at the factory.

Tesla’s overall European sales dropped significantly last year due to a variety of factors. However, sales are rebounding, and demand is strong once again, and only getting stronger. Tesla is now planning to bump production of Model Y vehicles at Giga Berlin upward by about 20 percent. It will also bring 1,000 new jobs to the plant.

Tesla confirmed the details of its planned production expansion in Germany this morning. It is a strategy to keep up with strengthening demand.

Advertisement

In Q1, Tesla saw a record 61,000 vehicles produced at Giga Berlin. European registrations rebounded sharply, with Model Y seeing 117 percent increases in March 2026 compared to last year. Germany alone saw stark increases, with a quadrupling in registrations to 9,252 units.

This trend continued in other key European markets, including France, Denmark and Sweden. Tesla registrations were up over 46 percent in some of these markets, and Model Y continued its trend as a top BEV in the market.

Demand has been recovering strongly in 2026, giving Tesla a reason to expand production efforts at the factory. These increases signal management’s confidence in sustained or growing European pull for Berlin-built vehicles.

Advertisement
Continue Reading

News

Tesla and driver sued by family of woman killed in Texas crash: what we know

Published

on

Credit: CNBC

Tesla is being sued by the family of the woman who was killed in a Texas crash involving a Model 3. The driver, who is also being sued, claimed the vehicle was operating on Autopilot mode, but Tesla executives have come out challenging that claim, stating that the driver of the vehicle overrode the system.

The lawsuit was filed by 76-year-old Martha Avila’s daughter and her husband, who allege a “design defect” involving a Tesla and a failure to warn. The suit alleges negligence against Tesla and the driver, Michael Butler.

Butler “stated he was operating with an automated driving assistance system engaged at the time of the crash,” the Harris County Sheriff’s Office said in a statement. He showed no signs of intoxication and was cooperative, the Sheriff’s Office said, according to NBC News.

Just after reports of the crash and numerous headlines that immediately blamed Tesla’s Autopilot suite, both Tesla CEO Elon Musk and Head of AI Ashok Elluswamy challenged that. Musk said the crash made “no sense” given that Tesla Autopilot and Full Self-Driving do not travel at the speeds the door cameras captured the car traveling at, which Tesla says was 73 MPH.

Advertisement

Tesla finally clarifies fatal Texas crash, confirms driver manually overrode acceleration

Elluswamy also revealed that Tesla data showed Butler overrode the system by pressing the accelerator to 100%, and that the pedal was compressed fully even after the car had crashed. Tesla has not released this data to the public, likely because it is communicating with agencies like the NHTSA on an investigation.

The suit uses a Washington Post analysis of government data that “identified at least 17 fatal incidents linked to Tesla Autopilot.”

This is far from the first time an accident has been blamed on Autopilot. A fatal crash in Texas was blamed on Autopilot several years ago, but when Tesla released data to the NTSB, which was investigating the crash, Autopilot was not available where the crash occurred, and Autosteer was never enabled, meaning the car was manually controlled at the time of the accident.

Advertisement

More information on the accident will be released as Tesla works with agencies to find the cause of the crash. From personal experience, it is hard to imagine Tesla Autopilot or FSD operating in this manner. It drives sometimes too cautiously in residential areas in parking lots, at least in my experience. Speeding happens, but at this rate in this type of area, it is hard to believe.

We look forward to more details being released with time.

Advertisement
Continue Reading