Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
h25b said:
GoingHot said:...where do you find detailed reports like this. On the NTSB accident queri page, you get a full report, but not with graphics and other detail.
flx757 said:That one, along with most other full accident reports, are avialable from a link on the NTSB home page. Go to www.ntsb.gov then click on "Accident Reports" under the Data and Information heading. That will bring you to their "Publications" page. From there, just go to the menu on the left and select "Most Recent" or "Older" from the Aviation section.
GoingHot said:what they were thinking when they crossed the OM at 4000, (well above 2600) and continued for 2 miles before starting down, leaving only 3 miles to get down? Why didn't they just tell ATC they need to make another turn in holding so they could cross OM at 2600?
According to what I was told by those who are/were at Hendrick, expired/improper equipment along with the fact that the accident Captain routinely used it as his ONLY source of information in flight, without cross-checking other instruments, is why the crash occured. Complacency, bad decision-making, and generally poor airmanship. All respect to the deceased, but it is what it is. No other way to say it, unfortunately.Which is why they were flying with an expired GPS data base plugged inside a non-certified GPS receiver?
ultrarunner said:Because they likely didn't know where they were. It's quite likely they had the PF HSI on GPS mode, and were looking at dme distances from a different fix. Remember, they had an outdated database card and a non-certified GPS receiver.
But if you look at their profile descent, it's quite obvious they likely thought they were further ought from the MAP then they actually were, as there was absolutely no urgency to get down as it was a stablized descent.