37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1367130 |
Time | |
Date | 201606 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | LAS.Airport |
State Reference | NV |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | B737 Next Generation Undifferentiated |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | GPWS |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Inflight Event / Encounter Other / Unknown |
Narrative:
On short final at las ILS 25L in perfect night conditions (VMC; no wind) perfectly stabilized at 500 ft AGL; we received a 'too low terrain' followed by a 'pull up' warning (that occurred at 300 ft AGL.) we both looked at each other in disbelief that this was happening since everything was 'perfect.'we decided to perform a go-around procedure; but did not perform a 20 degree nose up emergency thrust escape maneuver. Sometimes you just have to inject common sense into aircraft malfunctions/instrumentation errors and not cause huge concern/fright in our passengers about a calm situation turning into an aggressive; emergency maneuver. It simply was not warranted in this situation; despite what the book says. Rocketing up in altitude in a busy airspace such as las creates its own risks that just were not warranted. Strangely enough; I had a similar experience about 10 years ago also at las 25L at night at 2000 ft AGL where we had the same thing happen! It turns out there was a bad database for terrain in the system and the plane thought we were near hills when we were not. I had followed up on that one with maintenance. I wrote this incident in the logbook for maintenance to check out.I wanted to get this report in so that when you analyze the fdap you will have a back story to what really happened. I would do the exact same thing again despite what is drilled in to our brains about 'pull up.' this was clearly a malfunction in the airplane.
Original NASA ASRS Text
Title: A B737NG flight crew at 500 ft AGL to LAS Runway 25L received an unexpected; false EGPWS 'TOO LOW TERRAIN' and 'PULL UP' caution warnings and executed a go-around. No terrain is located at the position so a database error is suspected.
Narrative: On short final at LAS ILS 25L in perfect night conditions (VMC; no wind) perfectly stabilized at 500 ft AGL; we received a 'Too Low Terrain' followed by a 'Pull Up' Warning (that occurred at 300 ft AGL.) We both looked at each other in disbelief that this was happening since everything was 'perfect.'We decided to perform a go-around procedure; but did NOT perform a 20 degree nose up emergency thrust escape maneuver. Sometimes you just have to inject common sense into aircraft malfunctions/instrumentation errors and not cause huge concern/fright in our Passengers about a calm situation turning into an aggressive; emergency maneuver. It simply was NOT warranted in this situation; despite what the book says. Rocketing up in altitude in a busy airspace such as LAS creates its own risks that just were not warranted. Strangely enough; I had a similar experience about 10 years ago also at LAS 25L at night at 2000 ft AGL where we had the same thing happen! It turns out there was a bad database for terrain in the system and the plane thought we were near hills when we were not. I had followed up on that one with Maintenance. I wrote this incident in the logbook for Maintenance to check out.I wanted to get this report in so that when you analyze the FDAP you will have a back story to what really happened. I would do the exact same thing again despite what is drilled in to our brains about 'Pull Up.' This was clearly a malfunction in the airplane.
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.