←back to thread

247 points po | 1 comments | | HN request time: 0s | 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 #
maxglute ◴[] No.43531632[source]
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.
replies(2): >>43531664 #>>43532008 #
lloeki ◴[] No.43532008[source]
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.

replies(1): >>43532056 #
1. maxglute ◴[] No.43532056[source]
>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.