37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1325395 |
Time | |
Date | 201601 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | LSE.Airport |
State Reference | WI |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Inflight Event / Encounter CFTT / CFIT Inflight Event / Encounter Unstabilized Approach |
Narrative:
[We] received a GPWS pull up advisory. On the way to (lse) the first officer who was the pilot flying along with the captain briefed the page noting the occurrences with GPWS at that airport. As well as briefed the cold temperature altitude chart. The first officer also remembers the recent emails from foqa committee reminding of these issues at this location. On the way to lse we received direct to the airport from center. Minneapolis center kept us high close to the airport. The first officer asked the captain if they know we are using 31 instead of 36 as both are active and in use. The captain waited and then called center at this point we were within 20 miles of the airport. We got a descent to 6000 and later to 3500 feet. We asked for vectors for final due to a hard time locating the runway and field due to night conditions. The center did a very poor job by not giving the requested vectors. We should have asked direct to a fix on the GPS approach into 31. We decide to declare runway in sight so were would able to descend and intercept the course better than what the center was providing. We descended from 3500 to 2800 and now were intercepting the course from the east. Due to the fact we were inside the FAF of mugde and still at 2800 we had to descend at a large FPM down. With this large descent the GPWS went off telling us to pull up. The captain advised and first officer followed the command bars and responded to the first officer as required when receiving the pull-up advisory. The first officer reestablished on the fpa but continued as a visual approach looking mostly outside. Intercepting east of course and descending caused the aircraft to be near towers in the area. With rolling hills and terrain and recent emails from the company about GPWS going off at this location causes this airport to be a high risk for potential concern. With possible warning fatigue at this airport it is always important to respond to the alerts of GPWS. Although most of the occurrences happen on 36 we received it on 31. The crew should have had center set them up better and use the GPS approach instead of taking the visual that center was trying to push onto the crew. The crew should done a better job tracking the fpa. The crew should have established on final course way before inside FAF. Due to multiple reports of this issue reported by foqa warning fatigue may happen to other pilots. Lse needs to be addressed better and center should be aware of this situation so aircraft are set up better for the approach.
Original NASA ASRS Text
Title: Regional jet First Officer reported receiving a GPWS terrain warning on approach to LSE.
Narrative: [We] received a GPWS pull up advisory. On the way to (LSE) the First Officer who was the pilot flying along with the Captain briefed the page noting the occurrences with GPWS at that airport. As well as briefed the cold temperature altitude chart. The First Officer also remembers the recent emails from FOQA Committee reminding of these issues at this location. On the way to LSE we received direct to the airport from center. Minneapolis Center kept us high close to the airport. The FO asked the captain if they know we are using 31 instead of 36 as both are active and in use. The Captain waited and then called Center at this point we were within 20 miles of the airport. We got a descent to 6000 and later to 3500 feet. We asked for vectors for final due to a hard time locating the runway and field due to night conditions. The Center did a very poor job by not giving the requested vectors. We should have asked direct to a fix on the GPS approach into 31. We decide to declare runway in sight so were would able to descend and intercept the course better than what the Center was providing. We descended from 3500 to 2800 and now were intercepting the course from the east. Due to the fact we were inside the FAF of MUGDE and still at 2800 we had to descend at a large FPM down. With this large descent the GPWS went off telling us to pull up. The Captain advised and FO followed the command bars and responded to the FO as required when receiving the Pull-up advisory. The FO reestablished on the FPA but continued as a Visual Approach looking mostly outside. Intercepting east of course and descending caused the aircraft to be near towers in the area. With rolling hills and terrain and recent emails from the company about GPWS going off at this location causes this airport to be a high risk for potential concern. With possible warning fatigue at this airport it is always important to respond to the alerts of GPWS. Although most of the occurrences happen on 36 we received it on 31. The crew should have had Center set them up better and use the GPS approach instead of taking the Visual that Center was trying to push onto the crew. The crew should done a better job tracking the FPA. The crew should have established on final course way before inside FAF. Due to multiple reports of this issue reported by FOQA warning fatigue may happen to other pilots. LSE needs to be addressed better and Center should be aware of this situation so aircraft are set up better for the approach.
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.