37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1436467 |
Time | |
Date | 201703 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | PSP.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 104 Flight Crew Type 910 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
We were on a visual approach to [psp] runway 31L; when we got a 'terrain; terrain; pull up' (just one 'pull up') GPWS warning. We were northeast (right) of extended centerline; in a right bank to intercept centerline. The PAPI for 31L was showing one red light and three white lights. Weather was clear with unlimited visibility and we were over the city lights with the terrain to our left clearly in sight. Aircraft was fully configured for landing and on final approach speed. I was hand flying with the autothrottle off. Egpws was displaying normally with no faults annunciated. We never got a 'caution terrain; caution terrain' warning even though had we stopped our turn we would have been headed into steep terrain. Radar altimeter was showing appropriate altitude above valley floor for our distance from runway threshold. Radar altimeter never spiked lower subsequent to or during the warning because we were never over any high terrain.I'm fully aware of the SOP regarding this warning at night. But; based on all the information above; and the fact that I've flown this exact flight path dozens of times without a GPWS warning (this is my first one ever); I decided that a GPWS escape maneuver was not the safest course of action and continued to a normal landing.an escape maneuver would have to include a turn due to the very rapidly rising terrain; in this area; that we could never clear absent a turn. We were already in that turn and fully situationally aware throughout the approach.
Original NASA ASRS Text
Title: A320 flight crew reported continuing the night visual approach to PSP after receiving a GPWS terrain caution because they felt they were sufficiently clear of terrain to ignore the warning.
Narrative: We were on a visual approach to [PSP] RWY 31L; when we got a 'Terrain; Terrain; Pull Up' (just one 'Pull Up') GPWS warning. We were NE (right) of extended centerline; in a right bank to intercept centerline. The PAPI for 31L was showing one red light and three white lights. Weather was clear with unlimited visibility and we were over the city lights with the terrain to our left clearly in sight. Aircraft was fully configured for landing and on final approach speed. I was hand flying with the autothrottle off. EGPWS was displaying normally with no faults annunciated. We never got a 'Caution Terrain; Caution Terrain' warning even though had we stopped our turn we would have been headed into steep terrain. Radar altimeter was showing appropriate altitude above valley floor for our distance from runway threshold. Radar altimeter never spiked lower subsequent to or during the warning because we were never over any high terrain.I'm fully aware of the SOP regarding this warning at night. But; based on all the information above; and the fact that I've flown this exact flight path dozens of times without a GPWS warning (this is my first one ever); I decided that a GPWS escape maneuver was not the safest course of action and continued to a normal landing.An escape maneuver would have to include a turn due to the very rapidly rising terrain; in this area; that we could never clear absent a turn. We were already in that turn and fully situationally aware throughout 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.