News
Astra ‘Rocket 3’ nosecone dooms first Florida launch attempt
On Thursday, February 10th, Astra Space’s Rocket 3.3 launch vehicle took off from Cape Canaveral Space Force Station (CCSFS) Launch Complex 46 (LC-46).
Unfortunately, while liftoff and booster ascent appeared to be more or less perfect, Rocket 3’s payload fairing failed to separate, triggering a series of events that caused its upper stage to enter an uncontrolled and unrecoverable spin after burning for just a few seconds. Astra was unable to salvage the spinning rocket, resulting in a mission failure well short of orbit.
“Unfortunately we heard that an issue has been experienced during flight that prevented the delivery of our customer payloads to orbit today. We are deeply sorry to our customers NASA, University of Alabama, the University of Mexico and the University of California Berkeley,” said Astra Space Director of Product Management Carolina Grossman. “More information will be provided as we complete the data review.”
Today’s launch comes after two previous aborted launch attempts. The first attempt on February 5th was delayed due to a CCSFS radar system malfunction. The second launch delay came on February 7th, after the rocket aborted briefly after ignition because of a minor telemetry issue.
The Mission
NASA’s first mission under the agency’s Venture Class Launch Services (VCLS) Demonstration 2 contract hoped to launch four CubeSats to space as early as February 5th, 2022. The satellites, which made up the agency’s 41st Educational Launch of Nano-satellites (ELaNa) mission, were the first VCLS payloads launched – albeit unsuccessfully – from Cape Canaveral’s LC-46 pad, which last supported NASA’s Orion spacecraft Ascent Abort 2 (AA-2) test flight in July 2019.
The satellites onboard the flight were developed by three universities and one NASA center:
- BAMA 1 (University of Alabama, Tusscolusa)
- INCA (New Mexico State University, Las Cruces)
- QubeSat (University of California, Berkeley)
- R5-S1 (NASA’s Johnson Space Center, Houston)
The ELaNa 41 mission CubeSats were selected through NASA’s CubeSat Launch Initiative (CSLI) and were assigned to the mission by NASA’s Launch Services Program based at Kennedy. CSLI provides launch opportunities for small satellite payloads built by universities, high schools, NASA Centers, and non-profit organizations.
About Astra
Founded in 2016, Astra Space is an American launch vehicle company based in Alameda, California. Astra’s official vision “is to Improve Life on Earth from Space by creating a healthier and more connected planet.” The company hopes to secure a large portion of the small satellite launch market, stating that it “offers the lowest cost-per-launch dedicated orbital launch service of any operational launch provider in the world.”
As of November 2021, Astra charges around $2.5-3.5M for a dedicated Rocket 3 launch, which can deliver up to 150 kg (330 lb) to low Earth orbit (LEO). In comparison, for a dedicated Electron launch, Rocket Lab charges about $7.5M for 300 kg (660 lb) to LEO. For customers willing to accept a one-size-fits-all rideshare solution, SpaceX charges $1M for 200 kg (440 lb) to LEO or higher sun-synchronous orbits (SSOs).
While the aerospace company is based out of California, its frequent orbital and suborbital test flights have all been conducted at the Pacific Spaceport Complex in Kodiak, Alaska. Prior test flights used Rocket 1, Rocket 2, and Rocket 3 prototypes as Astra refined its design and embraced a hardware-rich development style that didn’t shy away from failure.
Rocket 3.3 reached orbit for the first time – carrying an instrumented boilerplate payload for the United States Space Force – on November 21st, 2021. Less than two months later, Rocket 3.3 (serial number LV08) attempted to carry several NASA-sponsored cubesats into orbit on February 10th, 2022 – also the rocket’s first East Coast launch. Like Rocket 3.3’s predecessors, the two-stage vehicle was fueled with liquid oxygen (LOx) and refined kerosene (RP-1). Powered by five Delphin engines, the first stage produces up to ~145 kilonewtons (32,500 lbf) of thrust at liftoff. The second stage is powered by one pressure-fed Aether engine that delivers about 3.3 kN (740 lbf) of thrust in the vacuum of space.
The unsuccessful launch attempt occurred just three months after Astra applied for their Federal Aviation Administration (FAA) launch license and less than one day after receiving that license.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
