37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1436232 |
Time | |
Date | 201703 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | SCT.TRACON |
State Reference | CA |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
We were assigned the RNAV rnp 31L into psp. It was nighttime and the captain (pilot flying) had briefed the approach and said to tell approach control that we did not want the RNAV visual. They left us high and we were having difficulty getting down and asked for vectoring turns. We originally wanted a right 360 but the controller kept asking us if we could see the airport and whether we wanted 'just the good old fashioned visual'; in his words. Finally the captain said he could see the field and we accepted the visual but used the RNAV as a course backup. As we were angling right toward final and descending; I called out terrain that I could see right in front of us but the captain said he had a visual on it. Right after that we got a momentary GPWS warning 'terrain; terrain' and then 'pull up' just as he was aligning with the final to 31L and intercepting the course for the RNAV (backup). He was hand flying at the time. No other warnings were heard and the captain reiterated that he had the terrain in sight. He was configured and stable by 1000 ft AGL. We landed on 31L without further incident.poor vectoring on approach control's part in their haste to give us clearance for a visual rather than the requested approach. Stick to the original plan and fly the approach as briefed. Insist on more appropriate descent profile from approach and also vectoring turns or a 360 to lose altitude.
Original NASA ASRS Text
Title: B737 First Officer reported poor vectoring by ATC; and that the Captain continued a night visual approach into PSP after receiving a GPWS terrain warning; stating the terrain was in sight.
Narrative: We were assigned the RNAV RNP 31L into PSP. It was nighttime and the Captain (Pilot Flying) had briefed the approach and said to tell Approach Control that we did not want the RNAV Visual. They left us high and we were having difficulty getting down and asked for vectoring turns. We originally wanted a right 360 but the Controller kept asking us if we could see the airport and whether we wanted 'just the good old fashioned visual'; in his words. Finally the Captain said he could see the field and we accepted the visual but used the RNAV as a course backup. As we were angling right toward final and descending; I called out terrain that I could see right in front of us but the Captain said he had a visual on it. Right after that we got a momentary GPWS warning 'Terrain; Terrain' and then 'Pull up' just as he was aligning with the final to 31L and intercepting the course for the RNAV (backup). He was hand flying at the time. No other warnings were heard and the Captain reiterated that he had the terrain in sight. He was configured and stable by 1000 ft AGL. We landed on 31L without further incident.Poor vectoring on Approach Control's part in their haste to give us clearance for a visual rather than the requested approach. Stick to the original plan and fly the approach as briefed. Insist on more appropriate descent profile from approach and also vectoring turns or a 360 to lose altitude.
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.