News
SpaceX, NASA hold press conference, historic astronaut launch clears final hurdles before readiness
With less than a month to go before the historic first crewed flight – and final human rating certification test – of the SpaceX Crew Dragon Demonstration 2 mission, NASA and SpaceX jointly held a full day of pre-mission press conferences on Friday, May 1st. Throughout the day many minor, but crucial, details were revealed.
Two primary technical concerns remained prior to Crew Dragon’s debut astronaut mission- the final drop test of the Crew Dragon Mark III parachutes and NASA’s clearance of SpaceX’s resolution of an in-flight engine-out anomaly suffered during the ascent phase of a previous Starlink mission.
Falcon 9 Merlin 1D engine-out anomaly
During the March 18th Starlink launch of a four-time flown Falcon 9 first-stage booster, a brief anomalous engine flare was witnessed during the ascent. Although ultimately successful in the deployment of the stack of 60 satellites, the first-stage booster failed to stick the landing aboard the autonomous spaceport drone ship “Of Course I Still Love You” resulting in a total loss. SpaceX CEO, Elon Musk, responded to comments posted to Twitter confirming the in-flight, early shutdown anomaly of one of the nine Merlin 1D engines.
Musk provided assurance that a thorough investigation would be conducted by SpaceX prior to any return to flight. Musk also noted that the first-ever engine failure of a Merlin 1D engine proved its robustness and the importance of redundancy provided by the other eight engines.
Just prior to the next Starlink mission on April 22nd marking a recycled Falcon 9 booster’s return to flight, Musk once again took to Twitter to provide insight into the early shutdown, in-flight anomaly. Musk stated that a small amount of isopropyl alcohol, used for cleaning the Merlin 1D engines, had been trapped in a sensor dead leg – later clarified as “an area it couldn’t float through” by SpaceX webcast host Lauren Lyons – and was ignited during flight causing the early shutdown of one Merlin 1D engine.
As identified during the April 22nd launch broadcast, out of an abundance of caution SpaceX decided to forgo that cleaning process for the April 22nd mission. However, no information was divulged regarding NASA’s response to either the anomaly or the resolution. Ultimately, the first stage Falcon 9 booster of the Starlink-6 performed flawlessly and even managed to stick the landing aboard the awaiting drone ship.
During Friday’s Commercial Crew and International Space Station overview news conference, a question regarding NASA’s response to the anomaly posed by Jeff Foust – reporter for SpaceNews.com – was directed to NASA’s Commercial Crew Program program manager, Kathy Lueders. She was asked to expand on the final technical constraints remaining prior to the launch of the Crew Dragon DM-2. Lueders responded positively stating that NASA had “reviewed the anomaly resolution…and cleared the engines on our launch vehicle” referring to the Falcon 9 booster slated to support DM-2, noting that the engine-out issue had been satisfactorily resolved and is now behind them.
One more drop test
Early in Friday’s Commercial Crew and International Space Station overview news conference – and later confirmed during remarks made by Lueders – SpaceX Chief Operating Officer, Gwynne Shotwell noted that a final 27th drop test of the Crew Dragon Mk III parachutes was scheduled to be completed later in the day. During a later Q&A interview with the crew of DM-2 – NASA astronauts Bob Behnken and Doug Hurley – Hurley commented that the final drop test had begun, however, he wasn’t quite sure if it had been completed successfully or not.
Just after the closing remarks of the crew Q&A interview, SpaceX announced via social media the successful completion of the 27th and final drop test of the all-important Mk III parachutes.
The May 1st final parachute drop test followed a worrisome stumble of the parachute program on March 24th. SpaceX announced that a Crew Dragon test article had become unstable forcing the helicopter pilot to prematurely release the test article out of an abundance of caution to maintain the safety of the helicopter crew. SpaceX noted that “while the test article was lost, this was not a failure of the parachute system and most importantly no one was injured.”
The confirmation of the successful May 1st drop test and the resolution of the Merlin 1D engine anomaly close out one of the final chapters of prerequisites prior to returning human spaceflight to American soil.
The only hurdles that remain to be cleared are various agency-level readiness reviews. According to Lueders, a SpaceX Flight Readiness Review is tentatively scheduled for Friday, May 8th followed by a NASA Flight Readiness Review on May 11th. Just one week ahead of launch, the final joint Launch Readiness Review is tentatively scheduled to be completed Wednesday, May 20th at which point DM-2 will bring crewed astronaut spaceflight back to American soil for the first time in nearly a decade.
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.
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
