37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1182445 |
Time | |
Date | 201406 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | LEX.TRACON |
State Reference | KY |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | GPWS |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
This was our second flight into lex today; the same thing happened on our first flight into lex as well. It appears there is a GPWS database anomaly directly southeast of the bridl intersection on the lex ILS 22. During both instances we were on an almost perfect 90 degree left base to runway 22; receiving vectors for a visual approach into runway 22. My best guess would be about 2 miles southeast of the runway 22 extended centerline. The vectors put us on final roughly 1 mile outside of bridl. We were level at an ATC assigned altitude of 3;000 ft. We could visually confirm we were past the 1998 foot towers to the east of the airport. During the first flight; we received a GPWS alert of 'terrain; terrain'; with no lights or other indications. The mfd's did not even activate the terrain function. There were no other indications. On the second flight; we received; 'terrain; terrain; pull up!' with no other indications; not even a whooper. The PF (captain) began to respond by adding power but the warning cleared within a second so we took no further action. On the first flight; after the GPWS alert; I activated the mfd terrain function and saw no terrain or obstacle features that would have caused an issue. I was likely at a 10/5 scale and recall seeing all green; but there may have been some yellow further out; but definitely nowhere near the vicinity of us (the 1998 foot towers were behind us and therefore wouldn't have shown on the display.) after both instances we continued and landed with no further issues.
Original NASA ASRS Text
Title: CRJ-200 flight crew experiences EGPWS terrain warnings on two different approaches to Runway 22 at LEX in the same aircraft. The alerts were about one or two miles east of the extended centerline for Runway 22 with the aircraft at 3;000 FT in VMC.
Narrative: This was our second flight into LEX today; the same thing happened on our first flight into LEX as well. It appears there is a GPWS database anomaly directly southeast of the BRIDL intersection on the LEX ILS 22. During both instances we were on an almost perfect 90 degree left base to Runway 22; receiving vectors for a visual approach into Runway 22. My best guess would be about 2 miles southeast of the Runway 22 extended centerline. The vectors put us on final roughly 1 mile outside of BRIDL. We were level at an ATC assigned altitude of 3;000 FT. We could visually confirm we were past the 1998 foot towers to the east of the airport. During the first flight; we received a GPWS alert of 'TERRAIN; TERRAIN'; with no lights or other indications. The MFD's did not even activate the terrain function. There were no other indications. On the second flight; we received; 'TERRAIN; TERRAIN; PULL UP!' with no other indications; not even a whooper. The PF (Captain) began to respond by adding power but the warning cleared within a second so we took no further action. On the first flight; after the GPWS alert; I activated the MFD terrain function and saw no terrain or obstacle features that would have caused an issue. I was likely at a 10/5 scale and recall seeing all green; but there may have been some yellow further out; but definitely nowhere near the vicinity of us (the 1998 foot towers were behind us and therefore wouldn't have shown on the display.) After both instances we continued and landed with no further issues.
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.