37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1415043 |
Time | |
Date | 201701 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | Large Transport |
Flight Phase | Initial Climb |
Route In Use | None |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Medium Transport |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
Right after a runway change from runway xy to runway xx; aircraft X checked in with the incorrect ATIS requesting an approach into ZZZ. I issued the correct ATIS; told him which approach to expect; and since he was only requesting one approach issued his abnormal missed instructions. Those instructions were runway heading; maintain 3000. At this time my sector became saturated with inbounds to ZZZ; it was abnormally busy because the airport was ground stopped earlier in the day due to hard IMC conditions. After clearing aircraft X for the approach; another controller helped by coordinating the missed instructions to the tower. About this time we were notified of a priority handling inbound to ZZZ; requesting to land runway xy; I started breaking air carriers out of my sequence; notifying them of the priority handling and aircraft X would be the last approach to runway xx before aircraft Y. I switched aircraft X to the tower. I was then informed after getting relieved from the position; we possibly had a loss between aircraft X going around runway xx and aircraft Y landing runway xy.
Original NASA ASRS Text
Title: Approach Controller reported of a possible loss of separation when an aircraft went around and was in conflict with an inbound opposite direction aircraft.
Narrative: Right after a runway change from RWY XY to RWY XX; Aircraft X checked in with the incorrect ATIS requesting an approach into ZZZ. I issued the correct ATIS; told him which approach to expect; and since he was only requesting one approach issued his abnormal missed instructions. Those instructions were runway heading; maintain 3000. At this time my sector became saturated with inbounds to ZZZ; it was abnormally busy because the airport was ground stopped earlier in the day due to hard IMC conditions. After clearing Aircraft X for the approach; another controller helped by coordinating the missed instructions to the tower. About this time we were notified of a priority handling inbound to ZZZ; requesting to land runway XY; I started breaking air carriers out of my sequence; notifying them of the priority handling and Aircraft X would be the last approach to RWY XX before Aircraft Y. I switched Aircraft X to the tower. I was then informed after getting relieved from the position; we possibly had a loss between Aircraft X going around RWY XX and Aircraft Y landing RWY XY.
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.