Connect with us

News

Astra returns to flight and deploys first satellites weeks after launch failure

(Astra)

Published

on

Astra’s Rocket 3 vehicle has successfully returned to flight and deployed its first satellites in orbit a mere 33 days after a failed launch attempt.

Rocket 3.3 – tail number LV0009 – lifted off at 12:22 pm EST (3:22 pm local) on March 15th from Kodiak Island, Alaska’s Pacific Spaceport Complex. A previous launch attempt the day prior was scrubbed by poor weather. 

Liftoff and ascent appeared nominal, followed by successful fairing separation – where Astra’s prior launch failed – and good upper stage performance. However, there was no immediate confirmation that payload deployment was successful. During a webcast of the launch, Carolina Grossman, Astra’s Director of Products warned viewers that a lack of ground stations meant there was no immediate way to know if payload deployment had occurred. Just over an hour after the deployment of the satellites, the CEO of Astra, Chris Kemp, stated that “the flight was nominal” on the webcast. “We were able to precisely deliver to the targeted orbit and inclination at orbital velocity.” Payload deployment was eventually confirmed.

The mission carried payloads for three customers. EyeStar-S4, developed by NearSpace Launch, will test inter-satellite communication technologies and remain attached to the Rocket 3.3’s second stage. OreSat0 is a student-built CubeSat meant to test flight hardware and develop “flight heritage” with several critical flight components for future use. The third payload remains unidentified.

Advertisement

The successful launch is a huge step for the Astra team. Just one month ago, during their first Florida launch attempt, technical difficulties during payload fairing separation ended the mission well before orbit. Astra recently completed an investigation of the anomaly and concluded that the failed payload fairing deployment was caused by an “electrical issue.” Bad engineering drawings led assembly technicians to arrange the fairing’s wiring in such a way that its five separation mechanisms fired in an incorrect order. That caused an electrical disconnection that prevented the last separation mechanism from receiving its command to open, which then prevented the fairing from separating completely before upper stage ignition.

According to Astra, “separately, we discovered a software issue that resulted in the upper stage engine being unable to use its Thrust Vector Control system. This led to the vehicle tumbling after the off-nominal stage separation and caused the end of the mission.” “The team worked really hard — every day, every weekend, many nights — to quickly identify the issues that we had on the flight, get another rocket back up to Kodiak, and fly it,” stated Kemp on the webcast. Astra has three more launches planned this spring, including additional missions from Launch Complex 36 in Cape Canaveral, Florida. 

Monica Pappas is a space flight enthusiast living on Florida's Space Coast. As a spaceflight reporter, her goal is to share stories about established and upcoming spaceflight companies. She hopes to share her excitement for the tremendous changes coming in the next few years for human spaceflight.

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