37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1757401 |
Time | |
Date | 202008 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | RNO.Airport |
State Reference | NV |
Aircraft 1 | |
Make Model Name | A319 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying First Officer |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
On a full approach on RNAV X runway 16L; prior to badpe descending and in the process of configuring; we were given a low altitude alert by ATC followed immediately by a GPWS terrain pull up warning. In the weather; above the 6;900 crossing altitude we executed the GPWS escape maneuver until we were positive we were clear of terrain and then transitioned to a go around. We wanted to fly the opposite direction approach to 34R; to avoid the tailwind and the terrain alert possibility; but the visibility was insufficient. ATC said they get low altitude alerts on that approach all the time. We flew it a second time; but this time vectored to final and configured earlier. We again got a low altitude alert from ATC; who informed us we were below the min vectoring altitude; but this time we were in visual conditions and could clearly see the terrain well below us. We were level and crossed badpe at approximately 6;900 feet as charted. Because we were configured and not descending we did not trigger a GPWS alert and we landed normally. Having an aircraft only capable of flying the X approach and not the Y approach hampered us. Also the other runway with the ILS approach hampered us. Flying the full approach also set us up as we were descending helped trigger the alert. I recommend a note in the company pages suggesting vectors to final and configuring early as this was a GPWS alert and not a egpws alert.
Original NASA ASRS Text
Title: A319 flight crew reported executing a go-around after receiving a low altitude alert from ATC as well as a GPWS terrain alert on approach to RNO RWY 16L.
Narrative: On a full approach on RNAV X RWY 16L; prior to BADPE descending and in the process of configuring; we were given a low altitude alert by ATC followed immediately by a GPWS terrain pull up warning. In the weather; above the 6;900 crossing altitude we executed the GPWS escape maneuver until we were positive we were clear of terrain and then transitioned to a go around. We wanted to fly the opposite direction approach to 34R; to avoid the tailwind and the terrain alert possibility; but the visibility was insufficient. ATC said they get low altitude alerts on that approach all the time. We flew it a second time; but this time vectored to final and configured earlier. We again got a low altitude alert from ATC; who informed us we were below the min vectoring altitude; but this time we were in visual conditions and could clearly see the terrain well below us. We were level and crossed BADPE at approximately 6;900 feet as charted. Because we were configured and not descending we did not trigger a GPWS alert and we landed normally. Having an aircraft only capable of flying the X approach and not the Y approach hampered us. Also the other runway with the ILS approach hampered us. Flying the full approach also set us up as we were descending helped trigger the alert. I recommend a note in the company pages suggesting vectors to final and configuring early as this was a GPWS alert and not a EGPWS alert.
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.