37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1307596 |
Time | |
Date | 201511 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.TRACON |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Other RNAV Approach |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 22 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
I had no aircraft on frequency; adjacent sector had two aircraft on frequency; the first of which was aircraft X; which was cleared for the RNAV approach. The adjacent sector controller switched communication to ZZZ tower; and a few miles later; the tower calls over the hot line; adjacent sector controller picks up; and the controller tells her that aircraft X wants vectors for the ILS. Aircraft X then comes up on my frequency; and in shock that he is below my minimum vectoring altitude and heading due south to a higher minimum vectoring altitude; I immediately issue a heading of 230 and climb and maintain three thousand five hundred feet; which is the minimum vectoring altitude in the area he is currently in. The aircraft was not still on the RNAV approach; because then he would have been in a turn. Aircraft X then said he had the airport in sight; and I gave him a visual approach. I asked him if he had a problem on the approach. I forget what he said; but I reissued the visual approach; then gave him the brasher warning about possible pilot deviation; and then switched him to the tower.
Original NASA ASRS Text
Title: TRACON Controller reported an aircraft was cleared for an RNAV Approach and switched to Tower frequency. The aircraft broke off from the approach and turned away from the airport below the minimum vectoring altitude. The Controller did not get a clear explanation from the flight crew. The flight crew reported the airport in sight and the Controller cleared them for a visual approach.
Narrative: I had no aircraft on frequency; adjacent sector had two aircraft on frequency; the first of which was Aircraft X; which was cleared for the RNAV Approach. The adjacent sector controller switched communication to ZZZ Tower; and a few miles later; the tower calls over the hot line; adjacent sector controller picks up; and the controller tells her that Aircraft X wants vectors for the ILS. Aircraft X then comes up on my frequency; and in shock that he is below my Minimum Vectoring Altitude and heading due south to a higher Minimum Vectoring Altitude; I immediately issue a heading of 230 and climb and maintain three thousand five hundred feet; which is the Minimum Vectoring Altitude in the area he is currently in. The aircraft was NOT still on the RNAV approach; because then he would have been in a turn. Aircraft X then said he had the airport in sight; and I gave him a visual approach. I asked him if he had a problem on the approach. I forget what he said; but I reissued the visual approach; then gave him the Brasher warning about possible pilot deviation; and then switched him to the tower.
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.