News
SpaceX’s first Falcon 9 Block 5 landing failure caught on video after launch success
In an extraordinary bit of live footage, SpaceX’s first Falcon 9 Block 5 launch of the Cargo Dragon spacecraft was topped by a spectacular partial failure of the Block 5 booster during its attempted recovery at Landing Zone-1 (LZ-1).
Despite this off-nominal recovery, Falcon 9 successfully placed Cargo Dragon into what John Insprucker deemed a highly accurate orbit, leaving the spacecraft to make its way to the International Space Station between now and Saturday. CEO Elon Musk further noted that Falcon 9 B1050 – despite landing in the ocean – was intact and still transmitting telemetry, potentially allowing SpaceX to still recovery the forlorn rocket.
Absolutely wild on-the-ground footage of @spacex Falcon 9 B1050's partially failed recovery, courtesy of Twitch streamer DasValdez. Keep in mind, of course, that the main mission – launching Cargo Dragon to orbit – was fully successful. pic.twitter.com/fKq7T79oIH
— Eric Ralph (@13ericralph31) December 5, 2018
What exactly went wrong is entirely unclear but roughly 30 seconds before a planned landing at LZ-1, Falcon 9 B1050 – shown live on SpaceX’s webcast – began to spin at an increasingly rapid pace, visibly losing some of its aerodynamic control authority before SpaceX cut the live feed. In the background, viewers could still hear the team on-console making callouts as the rocket’s landing burn started, culminating in a call for the landing team to “move to contingency procedure[s]”, the only SpaceX affirmation that something went wrong.
Above all else, it’s important to remember that the primary mission – sending Cargo Dragon to the ISS – continues to proceed nominally. In other words, Falcon 9 performed fine during ascent and only exhibited off-nominal behavior during the booster’s attempted landing after separating from the upper stage and Dragon payload.
- Despite major problems, Falcon 9 somehow pulled off a successful soft-landing in the Atlantic. (Tom Cross)
- Falcon 9 B1050 fought til the end, coming to a shockingly soft landing despite spinning rapidly. (Tom Cross)
- CRS-16 one minute before launch. (SpaceX)
- Falcon 9 B1050 seen shortly before a grid fin lost control, throwing the rocket into a near-uncontrollable spin. (SpaceX)
CEO Elon Musk took to Twitter soon after the breathtaking loss of control and expected landing time, stating that the SpaceX team currently pegged the failure on a grid fin’s stalled hydraulic fin, which ultimately caused the wild spinning seen in the webcast. Although it is almost without a doubt too early to actually know if the booster is in good enough condition to ever fly again, Musk seemed to directly suggest that it could eventually relaunch in support of an “internal SpaceX mission”, basically either Starlink or tech development.
Grid fin hydraulic pump stalled, so Falcon landed just out to sea. Appears to be undamaged & is transmitting data. Recovery ship dispatched.
— Elon Musk (@elonmusk) December 5, 2018
Stay tuned as SpaceX and Musk continue to offer updates on the continuing Cargo Dragon mission and attempted Falcon 9 recovery. SpaceX’s webcast recap can be viewed below.
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!
News
Tesla Cybercab stands to gain from new Trump autonomy rules
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.
News
Tesla plans production boost at Giga Berlin following rebound in Europe
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.
News
Tesla and driver sued by family of woman killed in Texas crash: what we know
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.



