News
SpaceX’s first orbital Starship launch slips to March 2022 in NASA document
A NASA document discussing a group’s plans to document SpaceX’s first orbital-velocity Starship reentry appears to suggest that the next-generation rocket’s orbital launch debut has slipped several months into 2022.
In March 2021, CEO Elon Musk confirmed a report that SpaceX was working towards a target of July 2021 for Starship’s first orbital launch attempt. At the time, it seemed undeniably ambitious but far from impossible. Less than half a year prior, SpaceX had kicked off a series of suborbital Starship test flights to altitudes of 10-12.5 km (6.2-8 mi). Beginning in December 2020, SN8 – effectively the first structurally complete Starship prototype – nearly stuck a landing on its first try, only narrowly falling short due to an engine and pressurization issue.
Less than two months later, SpaceX completed and launched Starship SN9 – again with a nearly flawless six-minute flight capped off with an unsuccessful landing attempt. Starship SN10 followed less than a month later and became the first prototype to land in one piece – albeit only for a few minutes. It was two weeks after that near-success – SpaceX’s third launch in as many months – that Musk revealed a goal of July 2021 for Starship’s first orbital launch. At that point in time, it appeared all but inevitable that SpaceX would be technically ready for an orbital launch before the end of the year.
Two weeks after Musk’s comments and less than four weeks after SN10’s near-miss, Starship SN11 gave one of the worst performances yet, invisibly exploding inside a fogbank well above the ground. However, further stoking the fires of optimism, Starship SN15 debuted a number of upgrades and became the first prototype to successfully launch, land, and survive a ~10km test flight in early May. Put simply, SpaceX built five Starship prototypes practically from scratch in roughly eight months and then completed five test flights in less than five months – all of which were largely successful.
SpaceX considered reusing Starship SN15 or launching SN16 to gain more landing experience but ultimately decided to mothball the prototypes to avoid disrupting orbital launch site construction. Just three months after SN15’s successful landing, SpaceX rolled the first orbital-class Starship and Super Heavy to the orbital launch site and briefly stacked the pair (Ship 20 and Booster 4) to their full height, forming the tallest rocket ever assembled. Although largely a photo opportunity, SpaceX still installed a full 29 Raptors on Super Heavy B4 and six Raptors on Starship S20, further raising confidence that the company’s engine production was already up to the task of supplying the nearly three-dozen needed for a single orbital test flight.
However, for reasons that are less than clear, that August 6th full-stack milestone is about where SpaceX’s H1 2021 momentum appeared to run into a brick wall. Perhaps due to a desire to focus on orbital launch site construction even at the cost of avoiding road closures or testing that would require a clear pad, Starship S20 sat on a stand for the better part of two months before completing even a minor test – by far the longest any Starship prototype has waited.
Seemingly in the midst of its third round of Raptor engine removal, Super Heavy B4 has yet to attempt a single test and it’s unclear how close to ready the orbital pad is to support booster proof and static fire tests. Neither ship nor booster has attempted to static fire its Raptor engines, though S20 could potentially be ready for its first test as early as Monday, October 18th.
Combined with recent developments in the FAA’s Boca Chica environmental review process, the odds of SpaceX attempting the first orbital Starship launch by the end of 2021 have rapidly dropped from decent to near-zero. From a technical perspective, it seems likely that SpaceX could still be ready for an orbital launch attempt just a few months from now. From a regulatory perspective, though, it would be practically unprecedented for the FAA to complete a favorable environmental review and approve even a one-off orbital Starship launch license in ~10 weeks. Even the apparent March 2022 target revealed in a NASA poster focused on the agency’s plans to film an orbital Starship reentry via high-altitude jet assumes that the FAA’s review and licensing process will take ~7 months from August 2021 – still extremely optimistic.
Ultimately, after two months with next to no prototype testing, it’s beginning to look like SpaceX has decided to focus on finishing Starbase’s first orbital launch site, refining vehicle designs, and building new prototypes (B5, S21, S22) rather than pushing hard for rapid B4/S20 testing and an imminent launch attempt. As a result, it’s becoming increasingly unlikely that Booster 4 and Ship 20 will fly as new and improved prototypes like Super Heavy B5 and Starship S21 prepare to overtake them.
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.
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 said this morning it will ramp up production at Gigafactory Berlin to a volume of 7,500 vehicles per week.
This is a 20 percent boost in production. Tesla will hire 1,000 new employees to help with the increase.$TSLA pic.twitter.com/kravKfRO5n
— TESLARATI (@Teslarati) June 25, 2026
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.
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.
“Application of the accelerator pedal was found to be as high as 98.8 percent,” the NTSB said in their findings. The highest recorded speed in the five seconds leading up to the impact was 67 miles per hour. The area where the crash occurred is residential, and Texas State laws… pic.twitter.com/XGD97NHVZ2
— TESLARATI (@Teslarati) March 18, 2026
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.
Tesla Cybercab stands to gain from new Trump autonomy rules
Tesla plans production boost at Giga Berlin following rebound in Europe
