37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1406316 |
Time | |
Date | 201612 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | MDPP.Airport |
State Reference | FO |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Check Pilot |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
On RNAV 08 approach to mdpp; we received a 'too low terrain' aural and a red GPWS warning light on instrument panel. We were in IMC conditions so we executed the GPWS escape maneuver.during the cruise portion of the flight we reviewed all jepp pages relating to mdpp. We saw that there is a note that states in order to avoid possible egpws warnings have the aircraft fully configured by PP351. We briefed the RNAV visual to runway 8 which at that point; was the approach we thought we might be assigned. On initial contact with mdpp approach we were assigned the RNAV26 with a circle to land 8. Later; we were offered the RNAV 08 which we accepted. The audio quality of mdpp approach radios was poor. Most of the transmissions cut out half way through. This caused a higher work level as we tried to understand the instructions. Once established on the approach we were at flaps 3 and gear down with a flaps full landing planned. While established on final between PP351 and keslo FAF fix we received the 'too low terrain' warning from the GPWS system while the egpws did not show a threat. Since we were IMC and knew there was terrain in the area we executed an escape maneuver; climbed to the MSA and followed the missed approach path.we clearly got a GPWS warning. The note says to expect an egpws warning when not fully configured. A little bit confusing as there were no egpws threats shown on the navigation display. Additionally; the note about being fully configured by PP351 could be better worded with a comment that PP351 is located 13.2 miles from the runway. This would be very helpful so pilots could better visualize where they needed to be fully configured.
Original NASA ASRS Text
Title: Large transport Check Pilot reported executing the escape maneuver after receiving a 'Too Low Terrain' warning from the GPWS on approach to Runway 08 at MDPP.
Narrative: On RNAV 08 approach to MDPP; we received a 'Too Low Terrain' aural and a Red GPWS warning light on instrument panel. We were in IMC conditions so we executed the GPWS escape maneuver.During the cruise portion of the flight we reviewed all Jepp pages relating to MDPP. We saw that there is a note that states in order to avoid possible EGPWS warnings have the aircraft fully configured by PP351. We briefed the RNAV Visual to runway 8 which at that point; was the approach we thought we might be assigned. On initial contact with MDPP approach we were assigned the RNAV26 with a circle to land 8. Later; we were offered the RNAV 08 which we accepted. The audio quality of MDPP Approach radios was poor. Most of the transmissions cut out half way through. This caused a higher work level as we tried to understand the instructions. Once established on the approach we were at flaps 3 and gear down with a flaps full landing planned. While established on final between PP351 and KESLO FAF fix we received the 'too low terrain' warning from the GPWS system while the EGPWS did not show a threat. Since we were IMC and knew there was terrain in the area we executed an escape maneuver; climbed to the MSA and followed the missed approach path.We clearly got a GPWS warning. The note says to expect an EGPWS warning when not fully configured. A little bit confusing as there were no EGPWS threats shown on the navigation display. Additionally; the note about being fully configured by PP351 could be better worded with a comment that PP351 is located 13.2 miles from the runway. This would be very helpful so pilots could better visualize where they needed to be fully configured.
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.