37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1004772 |
Time | |
Date | 201204 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ABQ.Airport |
State Reference | NM |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 244 Flight Crew Type 13000 |
Person 2 | |
Function | First Officer Pilot Not Flying |
Experience | Flight Crew Last 90 Days 439 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
[We were] approaching abq from the east running late; winds 300/9. We discussed the following: first; legality of runway 26 at night; (reviewed NOTAMS and 10-7); and saw nothing that precluded using 26. Second; [we] used performance data to look at runway 30; and if used; it required maximum braking. [We] created a visual point five miles east of the field at 180 KTS/7;300 ft AGL. [We] fully configured with flaps 30 positioned east southeast of field approximate radial 120. Intentionally offset to the south east because of terrain. At approximately 8;500 ft MSL (vsi approximately 800); we received a single (i.e. One) 'terrain' aural warning; and the first officer said he saw the pull up light for one second. I immediately initiated the go-around (adding power and starting a climb). Immediately thereafter (within three seconds); all warnings both aural and visual stopped. I leveled the altitude and announced 'leveling' and 'I'm going to continue the approach.' we proceeded to fly the remainder of the approach; and although saw white over white when approximately 1;500 ft AGL; was stabilized and within all parameters by the 1;000 ft call. Landed; and rolled out to taxiway C for the right turn. I asked tower if they had received any altitude warnings for us; and they said no. The first officer and I immediately realized the situation; and called for a complete terrain avoidance maneuver; instead of a brief go-around. After a lengthy discussion and agreement; we both felt that mistakes had been made; and that an as soon as possible was called for. I am clearly aware of proper terrain avoidance maneuvers; and made the mistake of thinking that known circumstances and flight parameters allowed for an abbreviated response to the procedure. This was clearly wrong! Regardless of the duration of warnings; the performance of the complete maneuver was called for and should have been completed. If again faced with any GPWS warnings of this type; I will not hesitate to perform the complete maneuver. Also; although we adequately prepared for; and briefed the hazards associated with a night visual to runway 26; I will not again choose this night approach option into abq.
Original NASA ASRS Text
Title: An Air Carrier crew approached ABQ for a night visual to Runway 26 and momentarily leveled after an GPWS warning; but continued the approach and after landing decided a Runway 26 night approach was ill advised.
Narrative: [We were] approaching ABQ from the east running late; winds 300/9. We discussed the following: First; legality of Runway 26 at night; (reviewed NOTAMS and 10-7); and saw nothing that precluded using 26. Second; [we] used performance data to look at Runway 30; and if used; it required MAX braking. [We] created a visual point five miles east of the field at 180 KTS/7;300 FT AGL. [We] fully configured with flaps 30 positioned east southeast of field approximate radial 120. Intentionally offset to the south east because of terrain. At approximately 8;500 FT MSL (VSI approximately 800); we received a single (i.e. one) 'Terrain' aural warning; and the First Officer said he saw the Pull Up light for one second. I immediately initiated the go-around (adding power and starting a climb). Immediately thereafter (within three seconds); all warnings both aural and visual stopped. I leveled the altitude and announced 'leveling' and 'I'm going to continue the approach.' We proceeded to fly the remainder of the approach; and although saw white over white when approximately 1;500 FT AGL; was stabilized and within all parameters by the 1;000 FT call. Landed; and rolled out to Taxiway C for the right turn. I asked Tower if they had received any altitude warnings for us; and they said no. The First Officer and I immediately realized the situation; and called for a complete terrain avoidance maneuver; instead of a brief go-around. After a lengthy discussion and agreement; we both felt that mistakes had been made; and that an ASAP was called for. I am clearly aware of proper terrain avoidance maneuvers; and made the mistake of thinking that known circumstances and flight parameters allowed for an abbreviated response to the procedure. This was clearly wrong! Regardless of the duration of warnings; the performance of the complete maneuver was called for and should have been completed. If again faced with any GPWS Warnings of this type; I will not hesitate to perform the complete maneuver. Also; although we adequately prepared for; and briefed the hazards associated with a night visual to Runway 26; I will not again choose this night approach option into ABQ.
Data retrieved from NASA's ASRS site as of July 2013 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.