News
Blue Origin rocket launch fails after engine catches fire
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.
..there is room for a lot of speculation ?– i did a frame by frame Picture – on the bottom row you can see some parts falling away. maybe the nozzle fell apart?!? pic.twitter.com/OOzPkPiX6G— Flo (@FloSpacenerd) September 12, 2022
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.
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.
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.
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.
Elon Musk
Tesla Full Self-Driving v14.2.1 texting and driving: we tested it
We decided to test it, and our main objective was to try to determine a more definitive label for when it would allow you to grab your phone and look at it without any nudge from the in-car driver monitoring system.
On Thursday, Tesla CEO Elon Musk said that Full Self-Driving v14.2.1 would enable texting and driving “depending on [the] context of surrounding traffic.”
Tesla CEO Elon Musk announces major update with texting and driving on FSD
We decided to test it, and our main objective was to try to determine a more definitive label for when it would allow you to grab your phone and look at it without any nudge from the in-car driver monitoring system.
I’d also like to add that, while Tesla had said back in early November that it hoped to allow this capability within one to two months, I still would not recommend you do it. Even if Tesla or Musk says it will allow you to do so, you should take into account the fact that many laws do not allow you to look at your phone. Be sure to refer to your local regulations surrounding texting and driving, and stay attentive to the road and its surroundings.
The Process
Based on Musk’s post on X, which said the ability to text and drive would be totally dependent on the “context of surrounding traffic,” I decided to try and find three levels of congestion: low, medium, and high.
I also tried as best as I could to always glance up at the road, a natural reaction, but I spent most of my time, during the spans of when it was in my hand, looking at my phone screen. I limited my time looking at the phone screen to a few seconds, five to seven at most. On local roads, I didn’t go over five seconds; once I got to the highway, I ensured the vehicle had no other cars directly in front of me.
Also, at any time I saw a pedestrian, I put my phone down and was fully attentive to the road. I also made sure there were no law enforcement officers around; I am still very aware of the law, which is why I would never do this myself if I were not testing it.
I also limited the testing to no more than one minute per attempt.
I am fully aware that this test might ruffle some feathers. I’m not one to text and drive, and I tried to keep this test as abbreviated as possible while still getting some insight on how often it would require me to look at the road once again.
The Results
Low Congestion Area
I picked a local road close to where I live at a time when I knew there would be very little traffic. I grabbed my phone and looked at it for no more than five seconds before I would glance up at the road to ensure everything was okay:
In full: the Low Congestion Area pic.twitter.com/6DqlBnekPn
— TESLARATI (@Teslarati) December 4, 2025
Looking up at the road was still regular in frequency; I would glance up at the road after hitting that five-second threshold. Then I would look back down.
I had no nudges during this portion of the test. Traffic was far from even a light volume, and other vehicles around were very infrequently seen.
Medium Congestion Area
This area had significantly more traffic and included a stop at a traffic light. I still kept the consecutive time of looking at my phone to about five seconds.
I would quickly glance at the road to ensure everything was okay, then look back down at my phone, spending enough time looking at a post on Instagram, X, or Facebook to determine what it was about, before then peeking at the road again.
There was once again no alert to look at the road, and I started to question whether I was even looking at my phone long enough to get an alert:
In full: the Medium Congestion Area pic.twitter.com/gnhIfBVe6Q
— TESLARATI (@Teslarati) December 4, 2025
Based on past versions of Full Self-Driving, especially dating back to v13, even looking out the window for too long would get me a nudge, and it was about the same amount of time, sometimes more, sometimes less, I would look out of a window to look at a house or a view.
High Congestion Area
I decided to use the highway as a High Congestion Area, and it finally gave me an alert to look at the road.
As strange as it is, I felt more comfortable looking down at my phone for a longer amount of time on the highway, especially considering there is a lower chance of a sudden stop or a dangerous maneuver by another car, especially as I was traveling just 5 MPH over in the left lane.
This is where I finally got an alert from the driver monitoring system, and I immediately put my phone down and returned to looking at the road:
In full: the High Congestion Area pic.twitter.com/K9rIn4ROvm
— TESLARATI (@Teslarati) December 4, 2025
Once I was able to trigger an alert, I considered the testing over with. I think in the future I’d like to try this again with someone else in the car to keep their eyes on the road, but I’m more than aware that we can’t always have company while driving.
My True Thoughts
Although this is apparently enabled based on what was said, I still do not feel totally comfortable with it. I would not ever consider shooting a text or responding to messages because Full Self-Driving is enabled, and there are two reasons for that.
The first is the fact that if an accident were to happen, it would be my fault. Although it would be my fault, people would take it as Tesla’s fault, just based on what media headlines usually are with accidents involving these cars.
Secondly, I am still well aware that it’s against the law to use your phone while driving. In Pennsylvania, we have the Paul Miller Law, which prohibits people from even holding their phones, even at stop lights.
I’d feel much more comfortable using my phone if liability were taken off of me in case of an accident. I trust FSD, but I am still erring on the side of caution, especially considering Tesla’s website still indicates vehicle operators have to remain attentive while using either FSD or Autopilot.
Check out our full test below:
Elon Musk
Tesla CEO Elon Musk announces major update with texting and driving on FSD
“Depending on context of surrounding traffic, yes,” Musk said in regards to FSD v14.2.1 allowing texting and driving.
Tesla CEO Elon Musk has announced a major update with texting and driving capabilities on Full Self-Driving v14.2.1, the company’s latest version of the FSD suite.
Tesla Full Self-Driving, even in its most mature and capable versions, is still a Level 2 autonomous driving suite, meaning it requires attention from the vehicle operator.
You cannot sleep, and you should not take attention away from driving; ultimately, you are still solely responsible for what happens with the car.
The vehicles utilize a cabin-facing camera to enable attention monitoring, and if you take your eyes off the road for too long, you will be admonished and advised to pay attention. After five strikes, FSD and Autopilot will be disabled.
However, Musk announced at the Annual Shareholder Meeting in early November that the company would look at the statistics, but it aimed to allow people to text and drive “within the next month or two.”
He said:
“I am confident that, within the next month or two, we’re gonna look at the safety statistics, but we will allow you to text and drive.”
“I am confident that, within the next month or two, we’re gonna look at the safety statistics, but we will allow you to text and drive.”
Does anyone think v14.3 will enable this? pic.twitter.com/N2yn0SK70M
— TESLARATI (@Teslarati) November 23, 2025
Today, Musk confirmed that the current version of Full Self-Driving, which is FSD v14.2.1, does allow for texting and driving “depending on context of surrounding traffic.”
Depending on context of surrounding traffic, yes
— Elon Musk (@elonmusk) December 4, 2025
There are some legitimate questions with this capability, especially as laws in all 50 U.S. states specifically prohibit texting and driving. It will be interesting to see the legality of it, because if a police officer sees you texting, they won’t know that you’re on Full Self-Driving, and you’ll likely be pulled over.
Some states prohibit drivers from even holding a phone when the car is in motion.
It is certainly a move toward unsupervised Full Self-Driving operation, but it is worth noting that Musk’s words state it will only allow the vehicle operator to do it depending on the context of surrounding traffic.
He did not outline any specific conditions that FSD would allow a driver to text and drive.
News
Tesla Semi just got a huge vote of confidence from 300-truck fleet
The confidential meeting marks a major step for the mid-sized carrier in evaluating the electric truck for its regional routes.
The Tesla Semi is moving closer to broader fleet adoption, with Keller Logistics Group wrapping up a key pre-production planning session with the electric vehicle maker’s team this week.
The confidential meeting marks a major step for the mid-sized carrier in evaluating the electric truck for its regional routes.
Keller’s pre-production Tesla Semi sessions
Keller Logistics Group, a family-owned carrier with over 300 tractors and 1,000 trailers operating in the Midwest and Southeast, completed the session to assess the Tesla Semi’s fit for its operations. The company’s routes typically span 500-600 miles per day, positioning it as an ideal tester for the Semi’s day cab configuration in standard logistics scenarios.
Details remain under mutual NDA, but the meeting reportedly focused on matching the truck to yard, shuttle and regional applications while scrutinizing economics like infrastructure, maintenance and incentives.
What Keller’s executives are saying
CEO Bryan Keller described the approach as methodical. “For us, staying ahead isn’t a headline, it’s a habit. From electrification and yard automation to digital visibility and warehouse technology, our teams are continually pressure-testing what’s next. The Tesla Semi discussion is one more way we evaluate new tools against our standards for safety, uptime, and customer ROI. We don’t chase trends, we pressure-test what works,” Keller said.
Benjamin Pierce, Chief Strategy Officer, echoed these sentiments. “Electrification and next-generation powertrains are part of a much broader transformation. Whether it’s proprietary yard systems like YardLink™, solar and renewable logistics solutions, or real-time vehicle intelligence, Keller’s approach stays the same, test it, prove it, and deploy it only when it strengthens service and total cost for our customers,” Pierce said.
Tesla Full Self-Driving v14.2.1 texting and driving: we tested it
Tesla CEO Elon Musk announces major update with texting and driving on FSD
