←back to thread

247 points po | 1 comments | | HN request time: 0.293s | source
Show context
kelnos ◴[] No.43531565[source]
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.

replies(6): >>43531622 #>>43531632 #>>43531674 #>>43531859 #>>43532104 #>>43532858 #
1. Animats ◴[] No.43532104[source]
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...