Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> But how can the pilot figure that out, while flying the aircraft?

Looking out the window.




So you're in a thing going close to the speed of sound, the thing starts malfunctioning, you look out the window, think "ahh the weather is nice, therefore the machine will probably not kill me" and keep flying? How does that thought process go?


And the weather wasn't nice - "A pilot who ejected from a malfunctioning F-35B in heavy rain over South Carolina last year..."


You more or less described standard operating procedure for operating a malfunctioning aircraft. That's why training starts with the eyes of the pilot and instrument-only flying comes later.

(And if you're going the speed of sound on a landing approach, something has already gone way off the rails).


Pilots are trained to fly without instruments. Even in inclement weather conditions.


> the report said its standby flight display and backup communication system “remained basically functional.”

Just to be clear, the pilot had the backup instruments available and functional, and the plane could be substantially controlled (i.e. could be pointed in the pilot's desired direction).

People are using feelings rather than facts to judge this pilot. So they do it differently then they would for example a police or SWAT team member shooting the wrong person under pressure. The same actions would have been judged very differently if chance hadn't kept that plane from crashing into a populated area.


He didn't kill someone. He bailed out of a malfunctioning plane with little time to decide.

If his plane went towards the ground with mach 1 at 1900 feet impact would occur in 1.5 seconds.


> He didn't kill someone.

The pilot left that to chance and chance made it that nobody was killed. At the very least you can recognize this was a failure of the pilot especially when the plane was realistically flyable, and backup instruments were available, in line with his training. In line with that overly broad definition of "uncontrolled flight" he ignored the backup instruments and punched out before attempting alternatives.

> a malfunctioning plane

The report called the aircraft flyable. The manual being overly broad on what's an "out-of-controlled flight" means he was not derelict in his duties but ejecting from a flyable aircraft (and leaving it to crash at the whims of randomness) was a mistake.

> If his plane went towards the ground with mach 1 at 1900 feet impact would occur in 1.5 seconds

But it wasn't, he wasn't in the middle of the crash, some instruments malfunctioned, the backups were working (they're there to be used in case the primary fails or else the designers would have bothered to put backups). The plane flew another 64 miles which took substantially more than 1.5s.

The "well technically" argument works less as the stakes go higher, and even less when dealing with a squadron commander. The plane flew, the instruments worked, and the pilots are trained for this. The report recognizes this.


it was rainy so at 1,900 feet he was probably in a cloud




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: