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.
News
Tesla Full Self-Driving v14.2.2.5 might be the most confusing release ever
With each Full Self-Driving release, I am realistic. I know some things are going to get better, and I know some things will regress slightly. However, these instances of improvements are relatively mild, as are the regressions. Yet, this version has shown me that it contains extremes of both.
Tesla Full Self-Driving v14.2.2.5 hit my car back on Valentine’s Day, February 14, and since I’ve had it, it has become, in my opinion, the most confusing release I’ve ever had.
With each Full Self-Driving release, I am realistic. I know some things are going to get better, and I know some things will regress slightly. However, these instances of improvements are relatively mild, as are the regressions. Yet, this version has shown me that it contains extremes of both.
It has been about three weeks of driving on v14.2.2.5; I’ve used it for nearly every mile traveled since it hit my car. I’ve taken short trips of 10 minutes or less, I’ve taken medium trips of an hour or less, and I’ve taken longer trips that are over 100 miles per leg and are over two hours of driving time one way.
These are my thoughts on it thus far:
Speed Profiles Are a Mixed Bag
Speed Profiles are something Tesla seems to tinker with quite frequently, and each version tends to show a drastic difference in how each one behaves compared to the previous version.
I do a vast majority of my FSD travel using Standard and Hurry modes, although in bad weather, I will scale it back to Chill, and when it’s a congested city on a weekend or during rush hour, I’ll throw it into Mad Max so it takes what it needs.
Early on, Speed Profiles really felt great. This is one of those really subjective parts of the FSD where someone might think one mode travels too quickly, whereas another person might see the identical performance as too slow or just right.
To me, I would like to see more consistency from release to release on them, but overall, things are pretty good. There are no real complaints on my end, as I had with previous releases.
In a past release, Mad Max traveled under the speed limit quite frequently, and I only had that experience because Hurry was acting the same way. I’ve had no instances of that with v14.2.2.5.
Strange Turn Signal Behavior
This is the first Full Self-Driving version where I’ve had so many weird things happen with the turn signals.
Two things come to mind: Using a turn signal on a sharp turn, and ignoring the navigation while putting the wrong turn signal on. I’ve encountered both things on v14.2.2.5.
On my way to the Supercharger, I take a road that has one semi-sharp right-hand turn with a driveway entrance right at the beginning of the turn.
Only recently, with the introduction of v14.2.2.5, have I had FSD put on the right turn signal when going around this turn. It’s obviously a minor issue, but it still happens, and it’s not standard practice:
How can we get Full Self-Driving to stop these turn signals?
There’s no need to use one here; the straight path is a driveway, not a public road. The right turn signal here is unnecessary pic.twitter.com/7uLDHnqCfv
— TESLARATI (@Teslarati) February 28, 2026
When sharing this on X, I had Tesla fans (the ones who refuse to acknowledge that the company can make mistakes) tell me that it’s a “valid” behavior that would be taught to anyone who has been “professionally trained” to drive.
Apparently, if you complain about this turn signal, you are also claiming you know more than Tesla engineers…okay.
Nobody in their right mind has ever gone around a sharp turn when driving their car and put on a signal when continuing on the same road. You would put a left turn signal on to indicate you were turning into that driveway if that’s what your intention was.
Like I said, it’s a totally minor issue. However, it’s not really needed, and nor is it normal. If I were in the car with someone who was taking a simple turn on a road they were traveling, and they signaled because the turn was sharp, I’d be scratching my head.
I’ve also had three separate instances of the car completely ignoring the navigation and putting on a signal that is opposite to what the routing says. Really quite strange.
Parking Performance is Still Underwhelming
Parking has been a complaint of mine with FSD for a long time, so much so that it is pretty rare that I allow the vehicle to park itself. More often than not, it is because I want to pick a spot that is relatively isolated.
However, in the times I allow it to pull into a spot, it still does some pretty head-scratching things.
Recently, it tried to back into a spot that was ~60% covered in plowed snow. The snow was piled about six feet high in a Target parking lot.
A few days later, it tried backing into a spot where someone failed the universal litmus test of returning their shopping cart. Both choices were baffling and required me to manually move the car to a different portion of the lot.
I used Autopark on both occasions, and it did a great job of getting into the spot. I notice that the parking performance when I manually choose the spot is much better than when the car does the entire parking process, meaning choosing the spot and parking in it.
It’s Doing Things (For Me) It’s Never Done Before
Two things that FSD has never done before, at least for me, are slow down in School Zones and avoid deer. The first is something I usually take over manually, and the second I surprisingly have not had to deal with yet.
I had my Tesla slow down at a school zone yesterday for the first time, traveling at 20 MPH and not 15 MPH as the sign suggested, but at the speed of other cars in the School Zone. This was impressive and the first time I experienced it.
I would like to see this more consistently, and I think School Zones should be one of those areas where, no matter what, FSD will only travel the speed limit.
Last night, FSD v14.2.2.5 recognized a deer in a roadside field and slowed down for it:
🚨 Cruising home on a rainy, foggy evening and my Tesla on Full Self-Driving begins to slow down suddenly
FSD just wanted Mr. Deer to make it home to his deer family ❤️ pic.twitter.com/cAeqVDgXo5
— TESLARATI (@Teslarati) March 4, 2026
Navigation Still SUCKS
Navigation will be a complaint until Tesla proves it can fix it. For now, it’s just terrible.
It still has not figured out how to leave my neighborhood. I give it the opportunity to prove me wrong each time I leave my house, and it just can’t do it.
It always tries to go out of the primary entrance/exit of the neighborhood when the route needs to take me left, even though that exit is a right turn only. I always leave a voice prompt for Tesla about it.
It still picks incredibly baffling routes for simple navigation. It’s the one thing I still really want Tesla to fix.
Investor's Corner
Tesla gets tip of the hat from major Wall Street firm on self-driving prowess
“Tesla is at the forefront of autonomous driving, supported by a camera-only approach that is technically harder but much cheaper than the multi-sensor systems widely used in the industry. This strategy should allow Tesla to scale more profitably compared to Robotaxi competitors, helped by a growing data engine from its existing fleet,” BoA wrote.
Tesla received a tip of the hat from major Wall Street firm Bank of America on Wednesday, as it reinitiated coverage on Tesla shares with a bullish stance that comes with a ‘Buy’ rating and a $460 price target.
In a new note that marks a sharp reversal from its neutral position earlier in 2025, the bank declared Tesla’s Full Self-Driving (FSD) technology the “leading consumer autonomy solution.”
Analysts highlighted Tesla’s camera-only architecture, known as Tesla Vision, as a strategic masterstroke. While technically more challenging than the multi-sensor setups favored by rivals, the vision-based approach is dramatically cheaper to produce and maintain.
This cost edge, combined with Tesla’s rapidly expanding real-world data engine, positions the company to scale robotaxis far more profitably than competitors, BofA argues in the new note:
“Tesla is at the forefront of autonomous driving, supported by a camera-only approach that is technically harder but much cheaper than the multi-sensor systems widely used in the industry. This strategy should allow Tesla to scale more profitably compared to Robotaxi competitors, helped by a growing data engine from its existing fleet.”
The bank now attributes roughly 52% of Tesla’s total valuation to its Robotaxi ambitions. It also flagged meaningful upside from the Optimus humanoid robot program and the fast-growing energy storage business, suggesting the auto segment’s recent headwinds, including expired incentives, are being eclipsed by these higher-margin opportunities.
Tesla’s own data underscores exactly why Wall Street is waking up to FSD’s potential. According to Tesla’s official safety reporting page, the FSD Supervised fleet has now surpassed 8.4 billion cumulative miles driven.
Tesla FSD (Supervised) fleet passes 8.4 billion cumulative miles
That total ballooned from just 6 million miles in 2021 to 80 million in 2022, 670 million in 2023, 2.25 billion in 2024, and a staggering 4.25 billion in 2025 alone. In the first 50 days of 2026, owners added another 1 billion miles — averaging more than 20 million miles per day.
This avalanche of real-world, camera-captured footage, much of it on complex city streets, gives Tesla an unmatched training dataset. Every mile feeds its neural networks, accelerating improvement cycles that lidar-dependent rivals simply cannot match at scale.
Tesla owners themselves will tell you the suite gets better with every release, bringing new features and improvements to its self-driving project.
The $460 target implies roughly 15 percent upside from recent trading levels around $400. While regulatory and safety hurdles remain, BofA’s endorsement signals growing institutional conviction that Tesla’s data advantage is not hype; it’s a tangible moat already delivering billions of miles of proof.
News
Tesla to discuss expansion of Samsung AI6 production plans: report
Tesla has reportedly requested an additional 24,000 wafers per month, which would bring total production capacity to around 40,000 wafers if finalized.
Tesla is reportedly discussing an expansion of its next-generation AI chip supply deal with Samsung Electronics.
As per a report from Korean industry outlet The Elec, Tesla purchasing executives are reportedly scheduled to meet Samsung officials this week to negotiate additional production volume for the company’s upcoming AI6 chip.
Industry sources cited in the report stated that Tesla is pushing to increase the production volume of its AI6 chip, which will be manufactured using Samsung’s 2-nanometer process.
Tesla previously signed a long-term foundry agreement with Samsung covering AI6 production through December 31, 2033. The deal was reportedly valued at about 22.8 trillion won (roughly $16–17 billion).
Under the existing agreement, Tesla secured approximately 16,000 wafers per month from the facility. The company has reportedly requested an additional 24,000 wafers per month, which would bring total production capacity to around 40,000 wafers if finalized.
Tesla purchasing executives are expected to discuss detailed supply terms during their visit to Samsung this week.
The AI6 chip is expected to support several Tesla technologies. Industry sources stated that the chip could be used for the company’s Full Self-Driving system, the Optimus humanoid robot, and Tesla’s internal AI data centers.
The report also indicated that AI6 clusters could replace the role previously planned for Tesla’s Dojo AI supercomputer. Instead of a single system, multiple AI6 chips would be combined into server-level clusters.
Tesla’s semiconductor collaboration with Samsung dates back several years. Samsung participated in the design of Tesla’s HW3 (AI3) chip and manufactured it using a 14-nanometer process. The HW4 chip currently used in Tesla vehicles was also produced by Samsung using a 5-nanometer node.
Tesla previously planned to split production of its AI5 chip between Samsung and TSMC. However, the company reportedly chose Samsung as the primary partner for the newer AI6 chip.
Tesla Full Self-Driving v14.2.2.5 might be the most confusing release ever
Tesla gets tip of the hat from major Wall Street firm on self-driving prowess
