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.

Advertisement

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.

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.

Advertisement

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

NTSB findings on fatal Tesla crash tell a very different story

The NTSB confirmed the driver, not Tesla’s FSD, caused the fatal Texas house crash.

Published

on

By

The National Transportation Safety Board released preliminary findings Wednesday confirming that a Tesla driver, not the vehicle’s software, caused a fatal crash in Katy, Texas in June. The driver, 44-year-old Michael Butler, had engaged Full Self-Driving Supervised mode on Rose Hollow Lane, a residential street with a 30 mph speed limit, before manually overriding the system by pressing the accelerator pedal all the way to 100%. Data recovered from the 2025 Tesla Model 3 showed the vehicle was traveling over 70 miles per hour when it struck a home and killed 76-year-old Martha Avila, who was inside. Weather was clear, the road was dry, and it was daylight.

Texas man charged in fatal Tesla crash where he blamed Autopilot

Butler told authorities he had passed out at the wheel. But security camera footage obtained by the NTSB told a different story, and showed the car accelerating through an intersection before leaving the road entirely. Police also found that Butler’s phone had Google searches including the terms “Tesla FSD not aggressive enough 2026” and “Tesla FSD too timid,” raising serious questions about how he was using the system before the crash. Butler has since been charged with manslaughter. The victim’s family has filed a lawsuit against both Butler and Tesla, alleging negligence.

The NTSB findings aligned directly with what Tesla VP of AI Software Ashok Elluswamy had already stated publicly on X in the weeks after the crash, writing that “the driver manually overrode self-driving by pressing the accelerator all the way to 100%.” The data confirmed his account.

Continue Reading

Investor's Corner

Lucid CEO dispels any rumors of bankruptcy: ‘So far from the facts’

Published

on

Credit: Lucid

Lucid CEO Silvio Napoli responded to rumors of an imminent bankruptcy that was reportedly being mulled after a report stated the automaker was working with the firm AlixPartners to iron out its next steps.

The company felt a massive loss on Wall Street yesterday, as the report essentially pushed the stock down as much as 55 percent on Tuesday.

The report, published initially by Eletric-Vehicles.com, claimed Lucid was essentially in dire straits and was told by AlixPartners, a commonly used restructuring advisor, to either take shares private or file for Chapter 11 bankruptcy protection.

Lucid denies rumors of bankruptcy after over 40% stock drop

Lucid’s head of Communications, Nick Twork, immediately challenged the report and stated the company “has sufficient liquidity to carry its operations well into next year.”

Now, the company’s CEO is chiming in as well, stating that the report is “so far from the facts that they require a direct response.”

Napoli said:

“Lucid is not considering bankruptcy or a transaction to take the company private. Those reports are false. The Board did not explore either scenario. Period.

As disclosed in our most recent quarterly filing, Lucid has sufficient liquidity to fund its operations well into next year.

We work with outside advisors to improve operational performance and execution. They are not advising Lucid on a take-private transaction or bankruptcy, and any suggestion that they have recommended either course of action to management or the Board is false.

My priority is clear: turn this company around. That is where the leadership team and I are focused.

I look forward to providing a full update during our quarterly earnings call on August 4th.”

It seems pretty clear that Lucid is confident things will be okay, and, to be honest, they should not have much to worry about, especially considering the company has been backed by the Saudi Public Investment Fund (PIF) for years. It has solid financial backing, and its sales, while weak, are pretty much right on par with a company of this age.

Lucid also sent a Cease & Desist letter to the publication for their report.

Lucid shares have rebounded nicely and are up nearly 21 percent at the time of publication. As soon as the company dispelled the rumors of bankruptcy yesterday, the stock began to climb back toward more reasonable levels.

Continue Reading

News

Tesla responds to strange Supercharging pricing error with classy move

Published

on

(Credit: Tesla)

Tesla has once again demonstrated strong customer focus by swiftly addressing and fully refunding a bizarre Supercharger pricing glitch that affected drivers in Atlantic Canada.

The issue surfaced earlier this month when the Tesla app began displaying dramatically inflated per-minute charging rates at stations in Prince Edward Island and parts of New Brunswick.

One widely shared screenshot from a Charlottetown, PEI Supercharger showed rates reaching ridiculous levels: $6.00 per minute for the 180-250 kW tier, along with $3.57/min for 100-180 kW and $2.29/min for 60-100 kW.

These figures were several times higher than normal Supercharger pricing in the region.

To put the error in perspective, charging at the highest incorrect rate would have been shockingly expensive.

At 250 kW, a common charging speed at Superchargers, a vehicle pulls roughly 4.17 kWh per minute. Under the glitch, a driver spending just 10 minutes at peak power would face a $60 bill. A typical 20- to 30-minute session to add meaningful range could have cost $120 to $180 or more, before any congestion fees.

Tesla gets another layer of gamification with Free Supercharging on the line

By comparison, standard Canadian Supercharger rates usually fall between $0.25 and $0.60 per kWh, making a similar session cost roughly $15–$40. The erroneous per-minute structure, combined with the inflated numbers, turned what should be a convenient stop into a potential financial shock.

The glitch appears to have started sometime around early July, and quickly drew attention on social media as owners questioned whether Tesla had implemented steep hidden increases. Some drivers even reported seeing $0 charges in their history, indicating broader billing confusion.

Tesla’s official Charging account on X stated that correct pricing would roll out at midnight on July 13, so the fix is already in effect. More importantly, the company announced it would waive all fees for every Supercharger session since July 2. This blanket waiver covers the entire affected period without requiring users to file individual claims, with automated refunds expected soon. The decision affects stations in PEI and nearby areas in New Brunswick and Nova Scotia.

It’s a classy move, and rather than issuing partial credits or forcing owners to submit support tickets, Tesla simply absorbed the cost of the system error and made drivers whole. In an industry where hidden fees and bill disputes are common, Tesla’s proactive, no-questions-asked approach reinforces owner trust and highlights the company’s commitment to service excellence.

The incident, while disruptive for a short time, ultimately showcases Tesla’s ability to own mistakes and prioritize customer satisfaction. Atlantic Canada Tesla owners can now charge with confidence again, knowing the company has their back when technology glitches occur.

In an era of complex EV billing, such transparency and generosity are refreshing and set a positive example for the industry.

Continue Reading