37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1574996 |
Time | |
Date | 201809 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | TKC.Airport |
State Reference | MN |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | SR22 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Direct |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Flight Instructor Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 150 Flight Crew Total 3500 Flight Crew Type 300 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural FAR Inflight Event / Encounter Weather / Turbulence Inflight Event / Encounter CFTT / CFIT |
Narrative:
Enroute to tkc; the weather was being reported as clear at the destination; therefore; I was expecting a visual approach. I had no thought in my mind that we wouldn't make it in to tracy. As we approached; I listened again; and the clouds had moved in (400 ft broken). The LNAV MDA for RNAV 29 is 444 ft AGL with a vdp at 1.3nm. Our aircraft is lpv capable; but there are no lpv mins for this approach. I elected to attempt the approach in hopes that we would break out of the broken layer. Our aircraft does provide us with vertical guidance for LNAV approaches; and the garmin perspective+ is equipped with synthetic vision. I followed the vertical navigation down to the MDA and leveled off. I continued at the MDA and flew past the vdp. I saw the runway about .1 or .2 out. I was not in a position to land and would have landed long on a 3;000 ft runway; so I elected to go missed.throughout the missed; and proceeding to the IAF for another attempt; I noticed a large hole in the clouds that would have legally allowed me to descend into class G airspace where I could have legally proceeded to my destination. However; I was not comfortable with what towers or terrain might be out there; offset from the runway center line. I have; however; flown many straight in approaches to runway 29 at tracy; and there are no obstacles on the approach path. Therefore; I elected another approach. As on the first attempt; I followed the vertical navigation down final approach. When I reached the MDA; I did not see the runway. At that time; I elected to continue down a little further. At approx. 150 ft below my MDA or 290 ft AGL; I saw the runway at 12 o'clock; on glide path; exactly like any other precision approach. I landed safely from that approach.historically; I have never considered flying below minimums. However; some get-there-itis; combined with powerful avionics that provide vertical guidance and synthetic vision that display the runway directly in front of you; made it very tempting to turn a non-precision approach into a precision approach. Right; wrong; or otherwise; I think this is an excellent lesson for anyone flying taa aircraft these days. They certainly have the ability to give the feeling of invulnerability in several areas (including instrument approaches; fuel planning; and thunderstorm avoidance with xm weather); which is a classic human factors pitfall; and a powerful one at that.
Original NASA ASRS Text
Title: SR22 pilot reported descending below minimums on an instrument approach.
Narrative: Enroute to TKC; the weather was being reported as clear at the destination; therefore; I was expecting a visual approach. I had no thought in my mind that we wouldn't make it in to Tracy. As we approached; I listened again; and the clouds had moved in (400 ft BKN). The LNAV MDA for RNAV 29 is 444 ft AGL with a VDP at 1.3nm. Our aircraft is LPV capable; but there are no LPV mins for this approach. I elected to attempt the approach in hopes that we would break out of the broken layer. Our aircraft does provide us with vertical guidance for LNAV approaches; and the Garmin Perspective+ is equipped with synthetic vision. I followed the vertical navigation down to the MDA and leveled off. I continued at the MDA and flew past the VDP. I saw the runway about .1 or .2 out. I was not in a position to land and would have landed long on a 3;000 ft runway; so I elected to go missed.Throughout the missed; and proceeding to the IAF for another attempt; I noticed a large hole in the clouds that would have legally allowed me to descend into Class G airspace where I could have legally proceeded to my destination. However; I was not comfortable with what towers or terrain might be out there; offset from the runway center line. I have; however; flown many straight in approaches to Runway 29 at Tracy; and there are no obstacles on the approach path. Therefore; I elected another approach. As on the first attempt; I followed the vertical navigation down final approach. When I reached the MDA; I did not see the runway. At that time; I elected to continue down a little further. At approx. 150 ft below my MDA or 290 ft AGL; I saw the runway at 12 o'clock; on glide path; exactly like any other precision approach. I landed safely from that approach.Historically; I have NEVER considered flying below minimums. However; some get-there-itis; combined with powerful avionics that provide vertical guidance and synthetic vision that display the runway directly in front of you; made it very tempting to turn a non-precision approach into a precision approach. Right; wrong; or otherwise; I think this is an excellent lesson for anyone flying TAA aircraft these days. They certainly have the ability to give the feeling of invulnerability in several areas (including instrument approaches; fuel planning; and thunderstorm avoidance with XM weather); which is a classic human factors pitfall; and a powerful one at that.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.