 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Prc tower controller reported an IFR aircraft was given incorrect missed approach instructions. Reporter stated 'runway heading' cannot be issued unless the pilot is maintaining terrain separation; which was not the case.
| Attributes | |
| ACN | 934141 |
| Time | |
| Date | 201102 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | PRC.Airport |
| State Reference | AZ |
| Aircraft 1 | |
| Make Model Name | Piper Single Undifferentiated or Other Model |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Landing |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X was IFR on an ILS approach and wanted to execute the published missed approach. As previously reported; we have a lame procedure for IFR departures that allows them to either fly the odp or proceed on course after a certain altitude. Aircraft X was told to fly runway heading after going missed to avoid the traffic on the northwest side of the airport; but the aircraft was never asked if they could provide their own terrain separation and we basically assumed responsibility for the aircraft.there needs to be a better solution for handling of IFR departures; including IFR aircraft going missed to drk; that allows the controller flexibility in assigning runway heading to departures to separate them from traffic on the northwest side of the airport.
Original NASA ASRS Text
Title: PRC Tower Controller reported an IFR aircraft was given incorrect missed approach instructions. Reporter stated 'runway heading' cannot be issued unless the pilot is maintaining terrain separation; which was not the case.
Narrative: Aircraft X was IFR on an ILS approach and wanted to execute the published missed approach. As previously reported; we have a lame procedure for IFR departures that allows them to either fly the ODP or proceed on course after a certain altitude. Aircraft X was told to fly runway heading after going missed to avoid the traffic on the northwest side of the airport; but the aircraft was never asked if they could provide their own terrain separation and we basically assumed responsibility for the aircraft.There needs to be a better solution for handling of IFR departures; including IFR aircraft going missed to DRK; that allows the Controller flexibility in assigning runway heading to departures to separate them from traffic on the northwest side of the airport.
Data retrieved from NASA's ASRS site as of April 2012 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.