TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Final Conclusions on Crash of F-35B That Flew Without a Pilot for 64 Miles

8 pointsby peutetre7 months ago

1 comment

t0mas887 months ago
I wouldn&#x27;t blame the pilot for ejecting after loosing navigation capabilities, the HUD and the PFD during a missed approach. That means you&#x27;re in very bad weather and lost the two primary means to control the aircraft and ensure you&#x27;re not hitting terrain. At low altitude, in instrument conditions, considering this a loss of control seems logical. Best decision is to eject.<p>Sure, sitting on the ground knowing the backup instruments were correct you could decide to keep on flying. Same for any civilian aircraft, we would trust the backup instruments and keep flying, because we don&#x27;t have ejection as an option.<p>But for a fighter jet I think the training in an emergency is &quot;when in doubt, eject&quot; they don&#x27;t want to loose pilots over staying with the aircraft for too long.<p>Also, this is amusing:<p>&gt; The loss of positive radar contact with the mishap aircraft resulted from a failed transponder caused by the electrical malfunction and the aircraft’s eventual descent below the air-traffic control radar horizon. The loss of positive contact could also be partially attributed to the F-35B’s low-observable technology.”<p>If you turn the transponder off on an F35 it&#x27;s supposed to be nearly invisible. So things worked as designed.
评论 #42015374 未加载
评论 #42017886 未加载