 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A phoenix TRACON (P50) controller reports of a pilot issue with communications. The controller climbed the aircraft to a higher altitude; but it wasn't climbing well. The controller asked the pilot if he had the terrain insight and issued two vectors away from the higher terrain. The pilot reported he was looking for traffic. The controller continued to vector the aircraft; and the pilot took the second heading.
| Attributes | |
| ACN | 1270831 |
| Time | |
| Date | 201506 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | P50.TRACON |
| State Reference | AZ |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
| Flight Phase | Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach Departure |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3 |
| Events | |
| Anomaly | Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X was a departure off of sdl; he was given an altitude of 070 and direct to the first fix in our airspace. I climbed him to FL210. He read it back but wasn't climbing well he was headed for higher terrain so I issued a vector to clear. Once I saw he was descending and I verified he was on the appropriate altimeter setting as this has happened quite a few times to pilots in the last week. I asked if he had the terrain in sight; he said he was looking for traffic. I had given him two vectors to clear terrain he read back both but never turned to the first heading I gave but took the second vector. I asked if he had the terrain in sight and needed assistance; he replied he was looking for traffic and needed no assistance.
Original NASA ASRS Text
Title: A Phoenix TRACON (P50) Controller reports of a pilot issue with communications. The Controller climbed the aircraft to a higher altitude; but it wasn't climbing well. The Controller asked the pilot if he had the terrain insight and issued two vectors away from the higher terrain. The pilot reported he was looking for traffic. The Controller continued to vector the aircraft; and the pilot took the second heading.
Narrative: Aircraft X was a departure off of SDL; he was given an altitude of 070 and direct to the first fix in our airspace. I climbed him to FL210. He read it back but wasn't climbing well he was headed for higher terrain so I issued a vector to clear. Once I saw he was descending and I verified he was on the appropriate altimeter setting as this has happened quite a few times to pilots in the last week. I asked if he had the terrain in sight; he said he was looking for traffic. I had given him two vectors to clear terrain he read back both but never turned to the first heading I gave but took the second vector. I asked if he had the terrain in sight and needed assistance; he replied he was looking for traffic and needed no assistance.
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.