37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1285336 |
Time | |
Date | 201508 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZAB.ARTCC |
State Reference | NM |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | Small Transport Low Wing 2 Turbojet Eng |
Flight Phase | Initial Climb |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6 |
Events | |
Anomaly | Airspace Violation All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
I released aircraft X to 130; syd [subject your discretion] with the inbound rove. Aircraft X checks in saying he's flying runway heading; despite his filed flight plan and assumed clearance to be ksaf..ZZZ. I ask him if he was assigned runway heading by saf and they said no. He appeared unsure what to do. Had a little back and forth with him and basically told him to turn on course. I tried not to imply course guidance below the mia as best I could; but he was flying directly at mountainous terrain immediately northeast of the airport and needed to start his turn. This has happened more than a few times at saf lately; though I don't know if it's purely pilot action or in concert with tower instructions. Scary situation for him and me both though. Pilots simply don't appear to respect the terrain; and when they file routes; they just expect ATC to take care of the problem. Incidentally; I had planned on putting in a new route to ZZZ for him for weather; but never got around to it before saf called for release because my workload was too high with traffic with the combined sector 94.this appears to be a pilot problem; and someone is going to get themselves killed eventually. From my end everything was normal until he checked in.
Original NASA ASRS Text
Title: ZAB Controller reported of traffic coming off SAF airport that do not know where they should be heading and enter a lower MIA [Minimum IFR Altitude]. Controller states this has happened more than a few times and is concerned that the terrain is higher on the route they are flying as opposed to what they file.
Narrative: I released Aircraft X to 130; SYD [Subject Your Discretion] with the inbound ROVE. Aircraft X checks in saying he's flying runway heading; despite his filed flight plan and assumed clearance to be KSAF..ZZZ. I ask him if he was assigned runway heading by SAF and they said no. He appeared unsure what to do. Had a little back and forth with him and basically told him to turn on course. I tried not to imply course guidance below the MIA as best I could; but he was flying directly at mountainous terrain immediately NE of the airport and needed to start his turn. This has happened more than a few times at SAF lately; though I don't know if it's purely pilot action or in concert with tower instructions. Scary situation for him and me both though. Pilots simply don't appear to respect the terrain; and when they file routes; they just expect ATC to take care of the problem. Incidentally; I had planned on putting in a new route to ZZZ for him for weather; but never got around to it before SAF called for release because my workload was too high with traffic with the combined sector 94.This appears to be a pilot problem; and someone is going to get themselves killed eventually. From my end everything was normal until he checked in.
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.