|
Patient was still billed
|
|
|
Author: anony Date:
3/13/2023 12:57:20 AM +5/-0
Show Orig. Msg (this window) Or
In New Window
|
Thank you for using my pictures from the previous thread, fairly intelligent discussion regarding it. Wx at the time was a high overcast. Near the departure is KRHP, it was 4800' overcast with an elevation of 1699' so appx 6500'MSL. Then just east of the ridge is K1A5, 5000' overcast and elevation of 2034' so appx 7000'MSL. The question will be why he was at the altitude he was, he went slightly north, not a direct track to avoid higher terrain but the very last part of the ridge he ended up crossing it at the highest elevation in the area at appx 5120', the area he was following was 2500-4000'. His altitude and airspeed were stable for appx 5 minutes prior to the ridge so he clearly was happy with what he had selected.
More than likely didnt realize how high the last ridge was combined with his track unforturnately taking him right over the top of a high peak. I'm guessing the HTAWS was inhibited due to nuisance alarms flying in that area, and didnt have foreflight updated to his current track to get an updated HOE in the profile view. The overcast combined with an area of zero ground lighting has the NVGs struggling to see the peak ahead is obscuring the beginning of the lights of the town of Franklin.
Its also important looking at the data that its raw pressure alt from the ADSB, altimeter setting was 30.16 that night so you have to add 240' feet to what you see. The scary part is if he had a moments notice of what was about to happen and started to pull back and during the course of the correction the aircraft started to hit the trees or is he just talking to crew and looking down and suddenly the sounds of trees hitting the airframe and seeing trees going past the side windows gets him to grab the controls and pull up and out of it before the aircraft got pulled in.
Included another shot of just how close he was to not hitting the ridge, just slightly different track and he misses it entirely.
|
|
Return-To-Index Display Full Msg Thread |
|
Erlanger- MedTrans crash
+5/-0 Scud running 3/12/2023 9:50:38 PM
|