News
SpaceX Crew-1 launch set for Sunday, ULA successfully launches spy satellite
On Friday evening, Nov. 13, NASA and SpaceX announced that the first operational Commercial Crew Program mission of the Crew Dragon would be delayed 24 hours to Sunday, Nov. 15, at 7:27 pm EST (0027 GMT 11/16). During a Crew-1 pre-launch news conference, SpaceX’s senior director of the Human Spaceflight Programs, Benji Reed, stated that the delay was driven by impacts on recovery efforts caused by tropical storm Eta, which had plagued Florida for days.
Just prior to the news conference, United Launch Alliance(ULA) successfully launched its Atlas V rocket after suffering delays of its own earlier in the week. The NROL-101 mission carried a classified payload for the National Reconnaissance Office of the U.S. government and successfully launched from Space Launch Complex 41 (SLC-41) at Cape Canaveral Air Force Station at 5:32 pm EST.
Florida weather caused multiple launch delays
Weather, especially that caused by tropical storm Eta, has caused a domino effect of delays for SpaceX and ULA over the last few weeks. The ULA Atlas V 531 rocket stacked with the secretive NROL-101 payload, initially set to liftoff on Nov. 3, was first delayed by damage sustained to environmental control system hardware of the upper stage.
According to company CEO, Tory Bruno, as the rocket was transported from ULA’s vertical integration facility (VIF) to the launchpad of SLC-41, very high winds caused damage to a duct that controlled the flow rate of an upper payload environmental control system. As a result, the rocket was returned to the VIF to have the duct replaced. A launch attempt scheduled for the following day on Wednesday, Nov. 4, was called off due to an unrelated problem with ground support equipment.
The NROL-101 mission was then set to launch on Sunday, Nov. 8, but that attempt was eventually called off due to the impending weather that would be brought across the Florida peninsula by then hurricane Eta. On Friday, Nov. 6, the Atlas V 531 rocket and payload for the National Reconnaissance Office was once again returned to the VIF for protection from the storm.
A final launch attempt was identified for Friday, Nov. 13, just 22 hours before the scheduled launch of the SpaceX, NASA Crew-1 mission from nearby Launch Complex 39A at the Kennedy Space Center. Fortunately, the weather held out long enough for the ULA Atlas V 531 rocket to liftoff. Following liftoff and successful payload deployment the mission was later declared a full success by ULA.
Florida weather also caused offshore recovery delays, impacting crewed launch
Similarly, the SpaceX and NASA Crew-1 mission has also suffered setbacks due to inclement weather, although not at the launch site. Following the successful launch and landing of the B1062 Falcon 9 of the recent GPSII-SV04 mission on Thursday, Nov. 5, SpaceX recovery teams battled unsettled seas to return the booster and the recovery droneship, Of Course I Still Love You (OCISLY), safely back to Port Canaveral.
After securing B1062 safely aboard OCISLY, the SpaceX recovery vessel GO Quest took refuge at the Port of Morehead City in North Carolina. The recovery crew would wait there to assist with the recovery of the B1061 Falcon 9 of the Crew-1 mission, rather than return to Port Canaveral in Florida. The droneship Just Read The Instructions (JRTI) was intended to meet the crew of GO Quest at the Crew-1 booster recovery zone prior to the end of the week.
Due to high winds and rough seas churned up by tropical storm Eta, the OCISLY droneship took an exceptionally tedious 7-day journey hugging the eastern coast of the United States to return to Port Canaveral. The delay caused the crew transfer process from OCISLY to JRTI to be delayed which in turn hindered the departure of the JRTI droneship.
As tropical storm Eta moved out and away from Florida the waters of the Atlantic remained too rough for the JRTI droneship to make up for the lost time. Following the conclusion of SpaceX’s Crew-1 preflight launch readiness review on Friday, Nov. 13, it was announced that the delay in getting the recovery droneship to the B1061 landing zone would delay the Crew-1 launch attempt by 24 hours.
Recovering the Falcon 9 booster, of any mission, is a secondary mission objective. However, the recovery of the Crew-1, B1061 Falcon 9 is important to both NASA and SpaceX – enough so to delay a launch attempt. NASA and SpaceX have already designated this booster to be reused on the next Crew Dragon mission, Crew-2, targeted for no earlier than March 30, 2021. In order to reuse a booster to save on launch costs, it must first be successfully recovered.
If all goes to plan, three NASA astronauts and one astronaut from the Japan Aerospace Exploration Agency will climb aboard the Crew Dragon Resilience on Sunday, Nov. 15, and blast off to the International Space Station precisely at 7:27 pm EST (0027 11/16) from LC-39A at the Kennedy Space Center.
NASA and SpaceX will provide a hosted live broadcast of all Crew-1 events beginning at 3:15 pm EST on Sunday, Nov. 15, on NASA TV and on the SpaceX website.
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
