NASA chief praises progress Blue Origin is making after launch failure 22%

By Eric Berger26%

7/1/2026, 12:57:36 PM

BS Summary: This article contains 22 faulty reasoning types, including Unattributed Quote, Halo Effect, and Recency Bias, with Optimism Bias as the most egregious example at 21.3% saturation with 152 hits. Analysis detected 857 faulty-reasoning hits from 715 analyzed words, generating a BS Score of 35.3% and a BS Rank of 22% (17,275 of 21,887 articles). This article is better (less manipulative) than 78.90% of the article peer group.

NASA Administrator Jared Isaacman said this week that Blue Origin has been putting significant resources into the cleanup of its launch pad since the explosion of its New Glenn rocket there in late May. 
“Blue Origin’s response to the situation is almost beyond impressive, and that’s not just a NASA assessment,” Isaacman said in response to questions from reporters on Wednesday afternoon. 
He noted that officials from the US Space Force have also been deeply involved in Blue Origin’s planning and work since an anomaly during a test firing took out New Glenn’s only operational launch pad on May 28. 
NASA has a significant stake in Blue Origin’s return to flight. 
It is counting on the company’s Mk. 1 lander to carry dozens of cargo missions to the Moon, and its Mk. 2 lander to eventually ferry people to the lunar surface. 
The company’s New Glenn rocket was expected to play a critical role in launching both of those landers. 
Plan A is to launch on New Glenn 
Before the accident, Blue Origin had been hoping to launch its first Mk. 1 mission, named Endurance, later this year for a cargo landing on the Moon. 
Additionally, the company is developing a test version of the Mk. 2 lander for launch as part of the Artemis III mission, which NASA hopes to fly during the second half of next year. 
Blue Origin officials, including chief executive Dave Limp, have said the company is working toward rebuilding Launch Complex 36A, completing the anomaly investigation, and launching New Glenn on a return-to-flight mission before the end of this year. 
Privately, some NASA officials have expressed skepticism about this timeline. 
Most independent observers have suggested that a 12- to 18-month timeline is probably the most realistic for New Glenn’s return to flight. 
Isaacman stressed this week that NASA’s preferred option is for the Endurance mission, which will carry two NASA science and technology payloads to the lunar surface, to launch on New Glenn. 
“They’re making great progress,” Isaacman said of Blue Origin. 
“So plan A is very much still to launch the Mk. 1 on New Glenn. 
They are very committed to getting back in the business of launching New Glenn before the end of the year. 
And Plan A is looking a lot better today than it was weeks ago, just based on the progress that the Blue Origin team is making.” 
NASA considering its options 
However, he added that prudence demands that NASA should also study alternative launch vehicles for the Endurance mission as well as Blue Origin’s lander for Artemis III. 
Options include SpaceX’s Falcon Heavy or United Launch Alliance’s Vulcan rockets. 
So NASA is closely watching Blue’s recovery. 
Isaacman said he receives daily updates from his team. 
“We’ve got time into 2027 before we’re getting nervous,” Isaacman said. 
“If we start tracking towards mid-2027, that has implications for the Artemis III mission, and for uncrewed landers, and that would be more concerning.” 
Cranes enter the picture 
Also on Wednesday, Limp provided additional information about the company’s plans to return to flight. 
“We continue to actively investigate the cause of the anomaly,” he wrote. 
“The vehicle is highly instrumented with extensive data from multiple camera angles and sensors, giving us confidence in our ability to identify and correct the root cause. 
Early analysis points to the aft section of the first stage.” 
During the test anomaly, Blue Origin lost the lightning tower at its launch site as well as the massive transporter-erector, which moved the rocket from a nearby integration hangar out to the launch site and lifted it vertically for takeoff. 
To expedite a return to flight, Limp said, the company is not rebuilding the same pad and is skipping construction of a new transporter-erector (which would take a long time). 
The company released a video showing how its engineers envision this process working. 
It involves using a crane to lift the integrated first and second stages onto the launch mount. 
Once there, and after pre-flight testing, a payload fairing would be placed atop the vehicle ahead of launch. 
Isaacman lauded Blue Origin for this transparency as it moves toward returning to flight, noting the broad interest within the space community in this topic. 
Article reasoning-pattern comparisonThis article: 5.9%Eric Berger: 1.0%Ars Technica: 2.8%Confirmation Bias5.9%This article: 3.2%Eric Berger: 1.8%Ars Technica: 1.2%Anchoring Bias3.2%This article: 2.8%Eric Berger: 2.9%Ars Technica: 2.4%Availability Heuristic2.8%This article: 3.1%Eric Berger: 1.0%Ars Technica: 1.0%Representativeness Heuristic3.1%This article: 3.8%Eric Berger: 1.5%Ars Technica: 0.6%Hindsight Bias3.8%This article: 3.8%Eric Berger: 1.7%Ars Technica: 2.1%Overconfidence Bias3.8%This article: 1.5%Eric Berger: 1.8%Ars Technica: 3.4%Framing Effect1.5%This article: 0.0%Eric Berger: 0.7%Ars Technica: 0.5%Loss Aversion0.0%This article: 3.8%Eric Berger: 0.3%Ars Technica: 0.5%Status Quo Bias3.8%This article: 0.0%Eric Berger: 0.2%Ars Technica: 0.1%Sunk Cost Effect0.0%This article: 21.3%Eric Berger: 6.6%Ars Technica: 4.2%Optimism Bias21.3%This article: 3.4%Eric Berger: 1.8%Ars Technica: 1.7%Pessimism Bias3.4%This article: 1.4%Eric Berger: 3.9%Ars Technica: 6.2%Negativity Bias1.4%This article: 0.0%Eric Berger: 0.5%Ars Technica: 1.2%Self-Serving Bias0.0%This article: 0.0%Eric Berger: 0.6%Ars Technica: 0.6%Fundamental Attribution Error0.0%This article: 0.0%Eric Berger: 0.3%Ars Technica: 0.1%Actor-Observer Bias0.0%This article: 3.5%Eric Berger: 1.1%Ars Technica: 0.6%In-Group Bias3.5%This article: 0.0%Eric Berger: 0.0%Ars Technica: 0.2%Out-Group Homogeneity Bias0.0%This article: 10.2%Eric Berger: 4.9%Ars Technica: 2.0%Halo Effect10.2%This article: 0.0%Eric Berger: 0.0%Ars Technica: 0.1%Horn Effect0.0%This article: 0.0%Eric Berger: 0.0%Ars Technica: 0.0%Dunning-Kruger Effect0.0%This article: 8.8%Eric Berger: 1.4%Ars Technica: 1.0%Recency Bias8.8%This article: 0.0%Eric Berger: 0.5%Ars Technica: 0.3%Primacy Effect0.0%This article: 0.0%Eric Berger: 0.1%Ars Technica: 0.1%Blind-Spot Bias0.0%This article: 0.0%Eric Berger: 0.7%Ars Technica: 0.5%Ad Hominem0.0%This article: 0.0%Eric Berger: 0.0%Ars Technica: 0.2%Straw Man0.0%This article: 7.0%Eric Berger: 3.1%Ars Technica: 4.1%Appeal to Authority7.0%This article: 2.7%Eric Berger: 1.3%Ars Technica: 1.1%False Dilemma2.7%This article: 0.0%Eric Berger: 0.1%Ars Technica: 0.7%Slippery Slope0.0%This article: 0.0%Eric Berger: 0.0%Ars Technica: 0.1%Circular Reasoning0.0%This article: 3.1%Eric Berger: 3.6%Ars Technica: 3.8%Hasty Generalization3.1%This article: 0.0%Eric Berger: 0.0%Ars Technica: 0.2%Red Herring0.0%This article: 0.0%Eric Berger: 0.2%Ars Technica: 0.6%Bandwagon0.0%This article: 0.0%Eric Berger: 2.1%Ars Technica: 2.7%Appeal to Emotion0.0%This article: 3.8%Eric Berger: 0.6%Ars Technica: 0.6%Begging the Question3.8%This article: 0.0%Eric Berger: 1.1%Ars Technica: 2.3%Post Hoc (False Cause)0.0%This article: 0.0%Eric Berger: 0.0%Ars Technica: 0.2%Tu Quoque0.0%This article: 0.0%Eric Berger: 0.3%Ars Technica: 0.5%Burden of Proof0.0%This article: 0.0%Eric Berger: 0.4%Ars Technica: 0.2%Appeal to Nature0.0%This article: 0.0%Eric Berger: 0.4%Ars Technica: 0.2%Composition/Division0.0%This article: 0.0%Eric Berger: 1.4%Ars Technica: 1.5%Anecdotal0.0%This article: 0.0%Eric Berger: 0.1%Ars Technica: 0.1%No True Scotsman0.0%This article: 0.0%Eric Berger: 1.4%Ars Technica: 1.7%Ambiguity (Equivocation)0.0%This article: 0.0%Eric Berger: 0.0%Ars Technica: 0.0%Gambler’s Fallacy0.0%This article: 0.0%Eric Berger: 0.3%Ars Technica: 0.1%Middle Ground0.0%This article: 0.0%Eric Berger: 0.0%Ars Technica: 0.1%Personal Incredulity0.0%This article: 4.2%Eric Berger: 0.2%Ars Technica: 0.1%Special Pleading4.2%This article: 0.0%Eric Berger: 0.0%Ars Technica: 0.1%Genetic Fallacy0.0%This article: 11.2%Eric Berger: 0.7%Ars Technica: 1.5%Unattributed Quote11.2%This article: 3.9%Eric Berger: 0.4%Ars Technica: 1.0%Quote-first Misdirection3.9%This article: 7.7%Eric Berger: 4.4%Ars Technica: 4.5%Biased Writer Voice7.7%This article: 0.0%Eric Berger: 1.3%Ars Technica: 1.0%Indoctrination0.0%This article: 0.0%Eric Berger: 1.0%Ars Technica: 0.7%Politically Left Leaning Bias0.0%This article: 0.0%Eric Berger: 0.1%Ars Technica: 0.2%Politically Right Leaning Bias0.0%This article: 0.0%Eric Berger: 0.6%Ars Technica: 1.3%Attempt to Sell a Product or S…0.0%

715 words analyzed.

Speakers

3speakers62%attributed speech273writer words
Voice mapSelect a segment to jump to its words
Writer's voice • 11 words • 100.0% coverageJared Isaacman • 34 words • 0.0% coverageJared Isaacman • 28 words • 100.0% coverageJared Isaacman • 38 words • 0.0% coverageWriter's voice • 11 words • 0.0% coverageWriter's voice • 31 words • 0.0% coverageWriter's voice • 18 words • 0.0% coverageWriter's voice • 8 words • 0.0% coverageWriter's voice • 27 words • 0.0% coverageWriter's voice • 34 words • 0.0% coverageDave Limp • 37 words • 0.0% coverageWriter's voice • 10 words • 100.0% coverageWriter's voice • 22 words • 100.0% coverageJared Isaacman • 31 words • 0.0% coverageJared Isaacman • 9 words • 100.0% coverageJared Isaacman • 15 words • 0.0% coverageJared Isaacman • 20 words • 100.0% coverageJared Isaacman • 26 words • 0.0% coverageWriter's voice • 4 words • 0.0% coverageJared Isaacman • 27 words • 0.0% coverageWriter's voice • 11 words • 0.0% coverageWriter's voice • 7 words • 100.0% coverageJared Isaacman • 9 words • 0.0% coverageJared Isaacman • 11 words • 0.0% coverageJared Isaacman • 24 words • 0.0% coverageWriter's voice • 4 words • 0.0% coverageDave Limp • 15 words • 0.0% coverageDave Limp • 12 words • 0.0% coverageDave Limp • 27 words • 0.0% coverageDave Limp • 11 words • 0.0% coverageWriter's voice • 40 words • 0.0% coverageDave Limp • 30 words • 0.0% coverageBlue Origin • 13 words • 0.0% coverageWriter's voice • 17 words • 0.0% coverageWriter's voice • 18 words • 0.0% coverageJared Isaacman • 25 words • 0.0% coverage
Selected voice

Jared Isaacman

76%flagged-word coverage
297 attributed words67% of attributed speech63% writer coverage
0%10.0%20.0%Unattributed Quote+4.4 ptsWriter: 11.7%Jared Isaacman: 16.2%16.2%Biased Writer Voice+5.9 ptsWriter: 6.6%Jared Isaacman: 12.5%12.5%Quote-first Misdirection+9.4 ptsWriter: 0.0%Jared Isaacman: 9.4%9.4%

Attribution is sentence-level. Pattern percentages are calculated only from words assigned to that voice.

Loading…
Loading…
Loading…
Loading…

Analysis

Hover over highlighted words in the article to view the associated bias or fallacy analysis.