Connect with us

News

Blue Origin rocket launch fails after engine catches fire

Blue Origin's 23rd New Shepard launch has ended in failure. (Blue Origin)

Published

on

Blue Origin’s suborbital New Shepard rocket suffered a catastrophic engine failure during its 23rd launch attempt, ending a seven-year streak of 21 successes.

Following a handful of mostly weather-related delays that pushed New Shepard’s 23rd launch about two weeks past its original August 31st target, the single-stage vehicle lifted off from Blue Origin’s Van Horn, Texas launch site around 10:25 am CDT (14:25 UTC) on September 12th. Measuring about 15 meters (49 ft) tall, 3.7 meters (12.1 ft) wide, and capable of producing about 50 tons (~110,000 lbf) of thrust with its lone BE-3 engine at full throttle, New Shepard only made it about halfway through its nominal powered ascent before catastrophe struck.

The first signs of trouble appeared about 62 seconds after liftoff in the form of flickers and flashes in New Shepard’s exhaust, which is normally almost transparent. Less than two seconds after the first seemingly harmless flash, flames unintentionally burst from New Shepard’s engine section and quickly surrounded its BE-3PM engine. Less than a second after that, the rocket’s aft and began shedding pieces and stopped producing thrust, triggering a solid rocket motor stored inside its deployable capsule.

About a second after the incident began, the capsule’s abort motor ignited and carried the suborbital spacecraft safely away from the failing New Shepard booster. The capsule ultimately coasted to an apogee of 11.4 kilometers (7.1 miles) – almost ten times lower than nominal – before descending back to Earth, deploying its parachute system, and safely touching down in the Texas desert scrub. Thankfully, NS-23 was only carrying experiments, and no humans were at risk. Had a crew of suborbital tourists been aboard, they would have likely been a little battered but otherwise completely unharmed.

While any failure of a rocket is unfortunate, the failure of a rocket nominally designed to launch humans can have even worse repercussions. However, thanks to the seemingly flawless unplanned performance of New Shepard’s abort system, it’s safe to say that the day could have gone much worse for Blue Origin.

The failure is still not going to do the reputation of Blue Origin or New Shepard any favors. It also invites less than favorable comparisons with SpaceX, a different spaceflight startup also funded and founded by a tech tycoon in the early 2000s.

Advertisement
-

Founded a year and a half after Blue Origin, SpaceX, in comparison, reached orbit with Falcon 1 in 2008. In June 2010, it successfully debuted Falcon 9, an orbital-class rocket roughly 20 times larger. In 2012, Falcon 9 successfully launched an orbital Dragon spacecraft which became the first private vehicle to dock to the International Space Station. In January 2015, it attempted to recover a Falcon 9 booster for the first time. In December 2015, one month after Blue Origin’s first successful New Shepard landing, SpaceX aced its first Falcon 9 booster landing.

Nine months later, Falcon 9 suffered a catastrophic failure during prelaunch testing in September 2016 and didn’t return to flight until January 2017. That is where, for the most part, the paths of Blue Origin and SpaceX almost entirely diverged – but not in any obvious way. Instead, after a successful suborbital launch in October 2016, New Shepard didn’t fly again until December 2017. In the roughly six years between October 2016 and September 2022, New Shepard completed 10 uncrewed suborbital launches, 6 suborbital tourist launches, and suffered one failure during another uncrewed mission – 18 total launches.

Despite suffering a catastrophic failure that destroyed a customer’s multimillion-dollar satellite in September 2016, SpaceX returned to flight four months later, completed 150 orbital Falcon launches without fail in the same period; debuted the world’s largest operational rocket, Falcon Heavy, and completed two additional launches with it; debuted Crew Dragon and Cargo Dragon 2 on Falcon 9; launched its first astronauts into orbit, launched its first operational astronaut transport mission for NASA, launched its first two Starlink internet satellite prototypes, launched another 60 refined Starlink prototypes, began operational Falcon 9 Starlink launches, built and launched more than 3000 Starlink satellites total; landed 130+ Falcon boosters, and reuse Falcon boosters 117 times.

(SpaceX)
Completed on September 11th, Falcon 9’s latest mission was its 173rd successful orbital launch. (Richard Angle)

The differences could not be more stark or strange, given that both companies have been operating more or less side by side and working towards similar goals for as long as they’ve existed. To Blue Origin’s credit, the company managed a record six New Shepard launches – three carrying tourists – in 2021. NS-23 was its fourth planned launch in 2022, suggesting that it could have achieved a similar cadence this year if the mission had had a different fate. Instead, the launch failure has triggered an anomaly investigation that will search for the root cause and try to uncover shortcomings that will then need to be rectified before New Shepard can return to flight. Given that Blue Origin once went 15 months between successful New Shepard launches, it’s impossible to say how long that process will take.

In the meantime, the apparent failure of New Shepard’s BE-3PM engine could trigger investigations into Blue Origin’s other engine programs. While substantially different, BE-3U, a variant optimized for the upper stage of New Glenn, Blue Origin’s first orbital rocket, likely shares the most in common with New Shepard’s BE-3PM. BE-7, a small engine meant to power a Moon lander, could also be impacted.

Most importantly, Blue Origin is also in the midst of finally preparing two much more powerful and far more complex BE-4 engines for customer United Launch Alliance (ULA). Years behind schedule, Blue Origin completed the first two theoretically flightworthy BE-4 engines and began putting them through qualification testing earlier this year. It wants to ship those engines to ULA as soon as possible to avoid delaying the debut of the customer’s new Vulcan Centaur rocket. BE-3PM and BE-4 probably don’t share a single part, but many Blue Origin employees have likely worked on both programs, and the same Blue Origin leadership has certainly overseen both. As long as there’s any form of commonality, no matter how abstract, there’s always a risk that the underlying cause of problems in one program could be present in others.

Ultimately, it’s unlikely that there will be any serious connection. The New Shepard booster that failed on NS-23 was almost five years old and was flying for a record-breaking ninth time. It’s possible that Blue Origin was privately worried about the possibility of failure while pushing the envelope, but it offered no qualifications while discussing the mission. SpaceX CEO Elon Musk, in comparison, has almost always made it clear that failure is a possibility when the company attempts ‘firsts’ of any kind.

Advertisement
-

SpaceX recently launched and recovered the same Falcon 9 booster for the 14th time, setting its own internal record. As a result, that lone Falcon 9 booster, B1058, has flown as many times in the last 31 months as all New Shepard boosters combined have flown in the last 45 months.

Finally, while no company should be put in that position, Blue Origin deserves praise for its live coverage of the anomaly. Instead of immediately cutting the feeds, which would be what most providers would be expected to do during an operational launch, Blue Origin continued to broadcast views of the failure and provide live commentary until New Shepard’s capsule touched down well ahead of schedule.

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Lifestyle

Watch Tesla’s “guardian angel” FSD feature take over for collision evasion

Published

on

By

Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.

Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”

The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.


The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.

Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.

Tesla plans big safety improvements for Full Self-Driving v15

Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.

Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.

Continue Reading

News

Tesla Roadster event gets delayed due to unfavorable weather

Published

on

Credit: Tesla

Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.

The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:

“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”

We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.

Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.

Tesla Roadster is available for order once again following brief hold

The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.

The Tesla Roadster will be unveiled in Waco, Texas.

Continue Reading

Elon Musk

SpaceX turned a heralding moment for Starship into its greatest

Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.

Published

on

By

SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.

The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.

Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.

That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.

The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.

SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.

Continue Reading