A decision to eject from a failing F-35B fighter and the betrayal in its wake
208 comments
·March 31, 2025tgsovlerkhgsel
If you hate the long form filler and know what a fighter jet is, start (with the knowledge that the pilot is landing in poor weather) at "Suddenly, at 1:32:05 p.m", read until the first two sentences in section 2, then skip to section 5.
Edit: That said, there are no answers. It's just the long known story: A pilot ejects from a malfunctioning (but likely flyable) jet, gets cleared in the first two investigations because most other pilots would have interpreted the situation similarly, promoted, and then fired less than 4 months after moving with his family to the location of his new role. It remains unclear why but scapegoating to distract from the plane's issues is commonly seen as the most likely explanation, with all the risks it entails (pilots becoming more hesitant to eject or openly admit mistakes so safety can be improved).
bufferoverflow
I hate the long form so much. I come for the information about the plane crash details, and I get the wall of verbal diarrhea about pilot's upbringing.
At least put all that extra nonsense at the end.
null
stevage
I feel like in previous reporting I'd seen suggestions that the other pilots had lost confidence in him, and that you couldn't be the leader of a squadron if any of the pilots had any doubts.
This story seems to completely discount any "lost confidence" as a made up story.
motorest
> This story seems to completely discount any "lost confidence" as a made up story.
The "lost confidence" angle would be discarded if it was just made-up nonsense. It is also a convenient angle to pin the blame on a scapegoat who was proven to have zero blame or responsibility.
One can only imagine what would have been written on the guy if he crashed and went down with the plane. Certainly we would be reading about human errors and failures in judgement and lack of training and reckless behavior.
This is what mid/upper management types do in large organizations to cover their ass.
I recall a story about a high-speed train accident in Spain where the conductor was found to be the sole responsible due to speeding, and it took an investigator from the European Union to call out the company's managers for unexplainably failing to implement and run a pretty standard traffic control system on that track section whose basic features include automatically enforcing speed limits. The system would render impossible that sort of failure and, in spite of having been installed, it was unexplainably disconnected. But it was human error, of course.
exe34
> human error, of course
Well management is only human...
stogot
It seemed only to be one commandant that said he was “at fault” (in complete disregard to the other two investigations and stellar reviews to his two bosses).
Simplest reason: that commandant had a vendetta against him
yard2010
The soviet russians nuked Chernobyl with this attitude, it must be good
Sabinus
Your comment reminded me, an excellent showcase of institutional shenanigans is the Chernobyl miniseries on Netflix. Denial, blame, coverups, accountability. It's a very well made series in a grim Soviet setting.
yaro330
Just please don't take it as a documentary. It's a disservice to the people that actually worked at the plant that day and portrays them as arrogant fools, which none of them actually were.
That Chernobyl Guy on YouTube did great breakdowns.
stefanfisk
Don’t you mean HBO?
atoav
To me that smells like a plane that is too expensive to lose and someone higher up was looking for an excuse.
Sure the pilot with his life on the line could have risked the investment into his education on top of the investment into the aircraft to figure out whether an ill-prepared procedure was really ill-prepared — but should that really be the expectation?
If you rely on your pilot having to interpret written procedure in a very specific way by mind magic, that is on those who wrote the procedure. I am not sure if "ignores the procedure of a aircraft that expensive" is the skill you are looking for, even if it safes the aircraft for the moment.
bsder
> It remains unclear why but scapegoating to distract from the plane's issues is commonly seen
Only because people aren't willing to accept the fact that this is just rank, base, bog standard, internal military politics. The pilot was probably fine until he got a new, important posting that displaced someone else and that someone else was willing to throw some elbows to get it overturned.
As for fault, the reality of the military command chain is that you are responsible for shit that goes wrong on your watch even if it isn't necessarily your fault. You can lose the ability to get important postings if something bad goes wrong even once. Generally, those people run their time out as quietly as possible and leave. It is not smart of the military, but the military isn't noted for smart.
glimshe
I do hate the long form filler. Are there a lot of people that will only consume information if there is a huge article around it? I'm not saying I like tldr either, but there's an optimal middle ground somewhere.
petre
As I have said before: the pilot is alive instead of deceased so it was a good decision.
tetris11
I came here to say exactly the same
instagib
They had one short sentence in there that he still had a tiny alternate primary flight display. Still had control surfaces. He knew he was descending and his authorized air space. Pull up, look at the pfd, do some resets, follow helmet malfunction protocols.
There was very little about a devils advocate side to the story.
I could imagine others joking about ejecting for minor warnings or trolling him. Especially in the marines.
Do a FOIA on all ejections because his is just one. He had a good 27 year career and ended as a colonel with retirement benefits.
TomK32
Even if he would have trusted the alternative controls the jet has, he was in clouds over a densely populated area going 350mph just 750 feet above the ground, far below the 6000 feet the article quotes from the manual.
"In fact, the F-35B’s flight manual said, “the aircraft is considered to be in out of controlled flight (OCF) when it fails to respond properly to pilot inputs,” adding, “if out of control below 6,000 feet AGL (above ground level): EJECT.”"
rob74
Well, that's the crux of the issue: apparently the aircraft still did respond properly to pilot inputs. Of course, it's totally understandable to get spooked by all the electronics failing and decide to rather bail out than bet on the plane still being flyable, but if you go by the book, he shouldn't have ejected...
chopin
You can't know whether the plane responds correctly to your inputs under instrument conditions when you can't trust the instruments.
TomK32
You haven't read the article, or the part I quoted from it referring to the manual, which I would consider as "going by the book". Two of the three boards looking into the mishap "concluded that most highly experienced pilots with similar levels of experience in an F-35 would have punched out of the plane".
itsdrewmiller
The area being densely populated would be a point against ejecting, wouldn't it?
blobbers
I think this was just a story, less an investigation. It's basically his view, the lack of closure, and the result.
YZF
I feel like we had a discussion of this crash in the past. Would be nice to find those threads.
Feels like we're missing a piece of the puzzle in this story. Maybe something else happened over that year? Politics? The story starts as you'd expect. Accidents happen. Support. Returning to duty. What went wrong?
avidiax
My feeling is that the F-35 is "too big to fail". They needed to blame the pilot, and certainly didn't need anyone familiar with the defects of the plane in a prominent command or as a general.
So they fire the guy, and promote someone else that can be relied on to say that the F-35 has no more defects than any other plane had at this point in the program, and we can trust the US military industrial complex to deliver the F-47 in a similar fashion.
At the same time, you send a message: eject when your plane is misbehaving and you'll end your career. Sure, there's a risk that someone won't eject when they should, but there's also a chance that you'll be able to cover up another malfunction when the pilot nurses the plane back to base.
Did Pizzo say anything disparaging about the F-35? I doubt it. But when you've got billions of dollars of revenue/potential embarrassment on the line, you don't take chances.
JumpCrisscross
> My feeling is that the F-35 is "too big to fail"
Allies cancelling orders may force Washington’s hand: the cost of additional jets, parts, et cerera skyrocket if spread over fewer planes.
pjmlp
That is only happening thanks to the way US view on the world has changed, and the remote kill switch used against Ukrainian jets.
US has killed the allies trust.
Had these two events not happened, and most likely sales would not have been cancelled regardless of the F-35 issues.
atmosx
A common misconception - often echoed on this site - is that NATO allies and the U.S. operate on equal terms. They don’t. If the U.S. wants to sell 100 F-35s to European nations, it will happen.
Even today, with all this talk around NATO, there’s a massive U.S. military presence at NATO bases across Europe.
These forces are, in effect, under U.S. control, stationed in countries like Germany and Italy. And if Germany suddenly decided it wanted them gone - well, it’s not their call.
TL;DR: Life on the empire’s periphery might be comfortable, but you don’t get to choose your enemies - and you still have to pay your dues, or else.
stevage
I'm always surprised about this line of thinking. Surely an active duty pilot is going to keep his mouth shut, whereas as we see, as a retired one he's happy to talk to the papers.
dcow
On top of that, the person I want flying more of the same plane is one who’s experienced piloting it during major failure conditions. Instead they retire the experienced guy and put some other fresh hotshot in the seat.
pjmlp
Ironically every time someone proudly assert the existence of F-35 C++ coding standard [0], I am not sure if they actually understand the impact.
The software mess from F-35 would it be even worse without the standard, or has the existence of the standard hardly improved the coding practices as usually gets told.
Not that the answer to this philosophical question solves the issues for everyone affected by the F-35 software problems.
jiggawatts
One fun thing about “too big” projects like the F-35 is that the project management overheads cause a kind of recursive overhead, like the rocket equation, but applied to technical outcomes instead of orbital velocity. Any change isn’t “just” the change, it now has to got through review boards, subcontractors, liaisons, integration reviews, etc…
The result is that the F-35 computers are being “upgraded” (lol) to the same compute power as a first-gen Apple Watch… starting this year and finishing who-knows-when.
Meanwhile the F-16 which is “not as important” has already been upgraded with the same kind of chips as modern GPUs and has orders of magnitude more performance than the “flying computer” the the F-35 was supposed to be.
Weep for the poor C++ developers forced to shoehorn modern software into a computer that isn’t yet as powerful as a battery-powered consumer device most people have upgraded three times already.
jandrewrogers
The F-35 was designed for export. The F-22 wasn’t and I suspect the F-47 is not either. There are different objectives at work here.
The F-35 is technically capable but even that is subject to export controls despite being purpose-built for export. A lot of European companies have a large stake in the success of the F-35 in its various versions because they are building it for European customers.
guappa
I think at large european industry has more stake in F-35 not being bought, and local planes be used instead.
blobbers
This is a really interesting 'first thought'. "Designed for export"
Not the typical mindset of someone wanting true superiority through military power. Makes you think twice.
The F35 is expensive, keeps the defense apparatus going, and ultimately gets paid for by other countries. F22 barely reached production, so F47 will be interesting.
ashoeafoot
What european companies built the F35? Especially what part of the software is from Europe ?
Aeolun
It’s bizzare to think that high command in the US is that shortsighted.
atmosx
True. However, did you notice the emojis used in relation to the leaked Huthi attack? It’s difficult to place confidence in individuals wielding significant power when they conduct themselves like adolescents.
ARandomerDude
Defense companies with workers in congressional districts and bribe politicians – I mean, make campaign contributions in exchange for huge contracts. Congress oversees the military. The officers who don't help politicians get what they want don't get promoted. The officers who do, get rank, status, book deals, and lucrative jobs at defense companies after they retire.
It's disgusting but it's not that hard to figure out how it happens.
jyunwai
Past discussion from November 2024: https://news.ycombinator.com/item?id=42098475
makeitdouble
Going through the past threads, a lot of comments are about how the backup instruments were still on and functioning, while in this article he's said to have 0 visibility and no idea what is still accurately working and what is not, with no possible communication and the HUD rebooting 3 times before going dark..
Did more information come up during the time period ?
Either way, asking a pilot to not bail out in these circumstances sounds crazy.
decimalenough
The article mentions that "A small backup display was partially functional, but Del Pizzo had to look down to see it".
kelnos
He was a test pilot; he's supposed to put his life at risk. Not just that -- and this is something the (current) article touched on -- he is also supposed to consider that ejecting could mean his plane crashing somewhere where it's going to kill one or more people; it seems he only considered that after he was on the ground.
He didn't know what was working because he didn't try to figure it out. All he did was tell the plane to switch modes from STOL to regular forward flight. He didn't see if pitch, yaw, and roll flight controls were being respected, and it doesn't seem he tried to use the backup radio, or the backup instruments, other then glancing at them.
But I don't think he made a terrible decision! Ultimately he's still alive, he healed from his injuries, and no one else was hurt, and that's a good outcome in my opinion. But maybe his judgment in a crisis situation isn't good enough for the command position he was given. He did lose a $165M piece of equipment, one that he very well may have been able land safely, and while I would never place that above the lives of actual humans, it does matter. And that's really what the three reports said: many other pilots probably would have done what he did in that situation, but he should have taken more time to ascertain whether his plane was flyable or not, even if that would have put him at further risk.
Maybe he would have been fine continuing to be a test pilot under the command of someone else's test group, but maybe his superiors decided that his actions showed he wasn't the kind of person they wanted in command. I dunno; I've never been a Marine (or any kind of military officer), so I don't know either way. But I suspect most of us here haven't, and don't really have expert knowledge on how these sorts of things are supposed to work.
kopirgan
The pilot, del Pizzo himself seems to have realised upon return to flying, the sound of engine dying he heard was actually the thrust engine not the main one.
Not sure if that's one factor the investigation considered. You can't wish away fact that the plane flew several minutes after he bailed.
Very hard for us to know it's complex.. We Can only guess
jpgvm
Losing all instruments with no visibility is still ejectable even if he thought the engine was still running. He was disorientated and relying on his instruments, when flying under IFR (instrument flight rules) loss of instruments is tantamount to loss of control. The likely outcome in those situations is controlled flight into terrain at 350+mph.
With low altitude being an aggravating factor he was always 100% correct in ejecting and whatever the plane did afterwards is largely irrelevant.
kopirgan
Yes 750m doesn't give much room for errors or time
rcakebread
It was 750 feet, not meters. So much less room.
mmaunder
I think there are many other moving parts in this story that aren’t public knowledge.
gscott
Mostly the hundreds of billions of dollars spent on an airplane that's not ready for prime time yet.
decimalenough
The F-35B entered service ten years ago, in 2015. But there have been continuous upgrades to it, and given that the 2023 incident described in the article started with the HUD (apparently) crashing 3 times in a row, there's plenty of room for improvement.
charlie90
Im not a pilot or anything, but looking at the cockpit of the f35, it seems pretty weird that the whole thing is a big touch screen. Reminds me of cars replacing physical controls with touchscreens...
mohsen1
Plus it's running Kubernetes for all of that!
https://thenewstack.io/how-the-u-s-air-force-deployed-kubern...
echoangle
I didn't watch the video but the article only mentions the F-16, not the F-35.
krunck
He wasn't loyal enough to the brand to not eject. The top brass in the F-35 project didn't like that. They needed to blame the pilot rather than the faulty machine in order to protect Lockheed Martin's and their own reputation.
kelnos
This was discussed four months ago: https://news.ycombinator.com/item?id=42098475
From my memory at the time, I was initially fully on the side of the pilot, but after reading through the discussion, I wasn't really sure anymore.
He didn't try to see if his flight controls (pitch, yaw, roll) were still responding, he didn't make use of the backup instruments, he didn't try the backup radio, and he had enough fuel to land elsewhere. The letter of the procedures may have said that he was in an out-of-control flight condition, but the procedures were too vague, and he should have had the experience to second-guess them and ascertain if his plane was actually out of control.
Sure, maybe all those things wouldn't have worked, and he would have had to eject. Or worse, they wouldn't have worked, and he would have spent enough time trying them that it would have been too late and he would have died.
But for better or worse, the actual outcome does matter: the plane was still flyable, and either a) he would have likely been able to successfully land, possibly at an alternate location with better weather, or b) he would have had the time and flight stability to try a bunch more options before deciding to eject.
I do find the circumstances strange, in how long it took for Marine brass to decide to relieve him of his command and torpedo his career. But I have no frame of reference for or experience around this, so perhaps it's not unusual. If he were just a rank-and-file pilot, he likely would have kept his position and continued on, perhaps with a bit of a bumpy road ahead. But he was given the command of an important group, a group tasked to refine flight procedures around this plane, and that comes with different expectations for his actions in the scenario he was in.
unsnap_biceps
> He didn't try to see if his flight controls (pitch, yaw, roll) were still responding, he didn't make use of the backup instruments, he didn't try the backup radio, and he had enough fuel to land elsewhere. The letter of the procedures may have said that he was in an out-of-control flight condition, but the procedures were too vague, and he should have had the experience to second-guess them and ascertain if his plane was actually out of control.
If the article is correct, the issue started when he was 750 feet above the ground depending at 800 feet per minute. He decided to eject approximately 30 seconds layer, at an approximate above ground height of 350 feet. Presuming he decided to continue troubleshooting, he was going to impact the ground in 25 seconds, and the ejection seat does take a few seconds for the pilot to clear the fuselage (and any explosions at impact).
This is a tragic situation to be in. He was under an immense time pressure to make a decision and from his understanding, the plane was out-of-control. He also doesn't know for sure if his rate of decent has accelerated, so he might have been dozens of feet above the ground.
I understand the armchair flying with perfect understanding and time to think it through means that he should have tried more stuff, but in the seat? I would have ejected. I think the majority of folks would have.
maxglute
IIRC he had no visibility so he couldn't test controls with eyeballs, can only assume out-of-control-flight scenario. Backup instruments said he was below 6000ft above ground level, aka trust instrument = potential for single digit seconds from hitting ground, and supposedly the F35 manual states ejection is the only option under those conditions.
lloeki
It started at 750ft
> Observe, orient: Jet still in the clouds, about 750 feet above ground, still in his control, descending glide path, about 800 feet per minute
Then brokenness again
> About 30 seconds had passed.
By then he might have been gliding halfway towards terrain.
> He felt the nose of the aircraft tilt upward. He felt a falling sensation.
Subtext is that this feels like stalling with only a few hundred feet and a few seconds left. There's no room to recover control surface.
There's only so much you can read in so little time with fallback instruments. Airspeed means squat, climb rate can be unreliable.
> Forty-one seconds.
Next loop is going to be either nothing happened or ground contact. What to you do.
maxglute
>6000ft above ground level
Context is I remember reading comment that F35 manual calls for ejection if out of control flight under 6000ft agl. If pilot was at 750ft, it reinforces how little time/margin pilot had to make call and that he probably did everything he can until last minute.
russdill
The recent video of the air ambulance impacting the ground is really "instructive" here. There are good indications that they believed they were in level flight either because of some instrument failure or lack of attention.
Animats
The F-35, like most modern fighters, is highly unstable in pitch without active control. Yaw and roll have some aerodynamic stability depending on the plane's mode. VTOL mode is even less stable. In VTOL mode, no visual reference, failing flight instruments, with multiple fault indicators and what appeared to be a failed transition to conventional flight mode, it's hard to blame the pilot for punching out. The transition is one-button automatic, with automatic coordination of engine power and nozzle positions. It's possible to reverse the process at any point in the transition, although that didn't happen here.
The "Command report" is available here.[1] But at the point that relevant flight data recorder data ought to appear, it's censored. Power faults and crashes of one of the redundant flight computers are mentioned. No full timeline. The report mentions that the transition to conventional flight mode did happen after the pilot punched out. But there are no technical details as to whether it was slower than normal.
Not enough info to form an opinion.
[1] https://www.hqmc.marines.mil/Portals/61/Docs/FOIA/F-35%20Mis...
bjornsing
Personally I think the risk he exposed others to gets too little attention. That jet could have come down anywhere. I can understand it’s a nerve wrecking situation and that ejecting is a likely outcome in any event, so “sooner rather than later” might feel like the better option. But sending the jet off as a cruise missile could have been avoided.
echoangle
If you don't see anything, staying in the aircraft doesn't make it any less of a missile. If he didn't eject, he could have still crashed into houses exactly like it could have after ejecting.
bjornsing
In the extreme, sure. And I’m not saying I know he was in the wrong. I’m just saying it’s something I think gets too little attention.
It was obviously possible to get the plane into a climb, because that’s how it ended up after he ejected. Once you are there is time to think and plan. Bad visibility doesn’t stretch infinity in the upward direction.
_cs2017_
"But for better or worse, the actual outcome does matter" -- curious what you mean by that?
gtsop
He means that he prefers for that poor lad to have died trying to save a piece of metal. Simple stuff, there is no going around it. For some people money is above human life.
_cs2017_
Sorry but I'm sure that's not what he meant.
IshKebab
Money is above human life at some point.
https://en.wikipedia.org/wiki/Value_of_life
But in this situation it sounds like the plane was highly likely to crash anyway so the estimated value you would save by potentially sacrificing him is low. Also I think the calculation is probably quite different in this situation compared to e.g. paying for safety measures in advance.
computerex
Extremely easy for you to write this treatise from the comfort of your armchair.
Do you understand this failure occurred at less than a thousand feet AGL?
chgs
To be fair his armchair is under a thousand feet AGL too
null
rpigab
Saying the pilot did nothing wrong means the plane did something wrong; sell less expansive planes to foreign countries. Throw him under the bus; sell more expansive planes.
I hear America is looking for efficiency and reduced gvt spendings, I'd say the F35 program is a good candidate to start, especially since now many countries aren't so fond of the whole "send all of your military data to our best friends the US of A".
preisschild
The F-35 would be a horrible place to start, because it is actually the best multirole jet fighter you can buy and gives you a massive advantage
renewiltord
The entire story is pretty interesting, actually.
When the pilot ejected and landed, the 911 dispatcher goes through some sort of flowchart like a call-center guy in Calcutta except at approximately 0.25x the pace https://www.youtube.com/watch?v=JCk3yk_38Fc (seriously, it's like watching an LLM execute on CPU).
Then there's the plane that no one could find for a while
Then the military said the reason they had to demote him was that while a normal pilot could have done what he did, he was a test pilot and they're supposed to run closer to the redline.
Overall, that combined with the contemporaneous Secret Service gaffes that nearly had the President whacked while they stood around in photo-op poses, really made me think: What if these people are all playing at their roles and they don't actually know what to do? I know it's general Millennial jokes that "nobody knows what they're doing; we're all just making it up as we go along".
But that's not true. I kind of know a lot of what I'm doing. There's a whole bunch of things where I can just execute with low error rate. These guys are doing something more important and their ancestors did it better. Which makes me think that they're not so good at what they do.
stevage
> (seriously, it's like watching an LLM execute on CPU).
I dunno, it seems fine to me. The person starts the call by saying they need an ambulance, so she is going through trying to collect information about what the injuries are.
The problem is that the pilot wanted to contact 911 to warn them about the plane crash, but somehow that got misinterpreted by the homeowner and got them on this ambulance track, and the pilot isn't doing a good job of saying "don't worry about me, let's talk about the plane". He keeps chiming in with these questions about the plane crash that seem to come out of nowhere.
He also doesn't even mention that he's concerned that the plane crash might have injured someone else.
Maybe there's more to this that was edited out.
But I'm not sure what the criticism is: she's supposed to stop asking questions about his injuries, and suddenly ask about a possible plane crash that they haven't had any reports of yet? What would that even achieve?
https://archive.is/192Wu