37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 912119 |
Time | |
Date | 201010 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | GEG.Airport |
State Reference | WA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Flight Plan | IFR |
Component | |
Aircraft Component | GPWS |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 227 Flight Crew Type 20000 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
When landing on runway 3 at geg; at 20 ft AGL and approximately 300 ft past the threshold; we received a 'too low terrain' GPWS warning. We continued to land since it was VMC and we were over the runway at the time (idle power and in the flare).this event brought up some questions: 1. The landing area on runway 3 has just opened after being closed for a long time. Is there new data in the database (our database was current)? And; could a lack of the extra concrete being in the database cause the warning? 2. Did the airplane do anything wrong? This is the only warning we received in three legs. 3. Did I do something wrong to cause the warning?note: it was a normal approach and landing (no approach and no vasis but the approach was stable all the way down). Another concern for us was that the warning was received so late if we didn't have a runway below us we would probably have contacted the ground before a go-around could be accomplished. I wanted to report this so other crews do not run into the same situation.
Original NASA ASRS Text
Title: A B737-300 flight crew received a 'too low terrain' GPWS warning while in a VMC flare over Runway 3 at GEG.
Narrative: When landing on Runway 3 at GEG; at 20 FT AGL and approximately 300 FT past the threshold; we received a 'too low terrain' GPWS warning. We continued to land since it was VMC and we were over the runway at the time (idle power and in the flare).This event brought up some questions: 1. The landing area on Runway 3 has just opened after being closed for a long time. Is there new data in the database (our database was current)? And; could a lack of the extra concrete being in the database cause the warning? 2. Did the airplane do anything wrong? This is the only warning we received in three legs. 3. Did I do something wrong to cause the warning?Note: It was a normal approach and landing (no approach and no VASIs but the approach was stable all the way down). Another concern for us was that the warning was received so late if we didn't have a runway below us we would probably have contacted the ground before a go-around could be accomplished. I wanted to report this so other crews do not run into the same situation.
Data retrieved from NASA's ASRS site as of April 2012 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.