Connect with us

News

SpaceX Starlink launch suffers third weather scrub, next attempt Tuesday

SpaceX is headed for its third Starlink-12 launch attempt after ~20 days of delays. (SpaceX)

Published

on

Update: Multiple weather constraint violations forced SpaceX to scrub today’s Starlink-12 launch attempt less than half an hour before liftoff, marking the mission’s third weather-related scrub and fourth abort overall since mid-September. As of October 4th, the US Air Force 45th Space Wing predicted a 40% chance of weather violation.

SpaceX’s fifth Starlink-12 launch attempt is scheduled no earlier than 7:29 am EDT (11:29 UTC) on Tuesday, October 6th. The mission-specific T-1 weather forecast predicts a 70% chance of favorable conditions.

On the heels of a rare last-second Falcon 9 launch abort, SpaceX is closing in on its third attempt to launch the 12th batch of operational Starlink satellites.

Scheduled to lift off from Kennedy Space Center (KSC) Launch Complex 39A (Pad 39A) no earlier than (NET) 7:51 am EDT (11:51 UTC) on Monday, October 5th, Starlink-12 was originally scheduled to launch in mid-September. Bad weather at the Atlantic Ocean landing zone caused a ten-day delay from September 17th to the 27th, followed by a pad weather delay on the 28th.

Advertisement

After a ULA Delta IV Heavy mission with range priority was scrubbed for the seventh time on September 30th, SpaceX tried to launch Starlink-12 again but suffered an abort – later blamed on a pad sensor – seven seconds before liftoff. Finally, a new Falcon 9 launch with an upgraded GPS III satellite aboard was aborted just two seconds before liftoff on October 2nd. Moved from NET October 3rd to the 5th just prior to GPS III SV04’s separate launch delay, Starlink-12 is now up next.

Interrupting what has otherwise been a much-improved level of launch readiness and schedule reliability for Falcon 9 and Falcon Heavy’s Block 5 upgrade, this recent string of delays – while mostly the result of weather and ULA’s own NROL-44 launch delays – has even become a concern for CEO Elon Musk. Currently focused on building out SpaceX’s new Starship factory and pushing towards the rocket’s first high-altitude and orbital test flights in Boca Chica, Texas, Musk stated that he would be flying to Cape Canaveral “to review hardware in person” on the week of October 5th.

Musk also says that SpaceX is “doing a broad review of launch site, propulsion, structures, avionics, range, & regulatory constraints” to determine if an apparent goal of “48 launches” in 2021 is feasible.

To be fair to SpaceX, most of the plague of delays suffered by the company in the last month has been caused by a mixture of weather and the range’s preferential treatment of ULA’s “national security” NROL-44 launch. Additionally, of an impressive seven ULA NROL-44 launch attempts between August 26th and September 30th, just a single one was caused by weather – the remaining six a result of a wide variety of technical software and hardware bugs. SpaceX’s Starlink-12 and GPS III SV04 missions have only suffered one technical launch abort each on September 30th and October 2nd.

Advertisement

In other words, short of upgrading Falcon rockets to launch and land in worse weather conditions, most of SpaceX’s delays have been largely out of the company’s control, while ULA’s NROL-44 struggles demonstrate just how much worse things could be. According to an unofficial analysis of 44 Falcon Block 5 launches since May 2018, only four technical launch aborts have been triggered by a booster fault. Pad-caused aborts have been roughly as common, meaning that 1 in roughly 6 to 8 SpaceX launches suffers some kind of abort shortly before liftoff, on average.

Both captured in one frame, SpaceX’s GPS III SV04 and Starlink-12 missions have run into repeated launch delays over the last 1-3 weeks. (SpaceX)

Altogether, Falcon Block 5 rockets have been relatively dependable for on-time, on-schedule launches even if SpaceX has struggled with more repeated delays than usual in the last few months. To achieve anywhere close to 48 launches annually, however, major improvements will need to be made, likely including upgrades to whatever is responsible for Falcon 9’s weather constraints. As of October 2020, SpaceX has never launched four times in one month (or four times in the same ~30-day period). To launch 48 times in one year, SpaceX will need to average four launches per month. That, of course, in no way accounts for the possibility that 2020-esque summer weather could functionally cut 4-8+ weeks off of Falcon 9’s annual availability.

Regardless, SpaceX will begin live coverage of the third Starlink-12 launch attempt around 7:35 am EDT (11:35 UTC). Tune in to (hopefully) catch the company’s 17th launch this year.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

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.

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.

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.

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.

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.

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.

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.

Continue Reading