2011-10 · NASA ASRS report 974528
TRACON Controller described a loss of separation event when coordination and direction to a military GCA Controller was not complied with; noting more specific directions to the GCA Controller would have likely prevented the event.
Aircraft X was under the control of the ZZZ GCA (Ground Control Approach) unit making an ILS approach to Runway XX for a practice approach; climb out; and then pick up an IFR on the go. I relayed climb out instructions to the GCA Controller of; 'Turn left heading 360; keep his turn close to the airport; climb and maintain 3;000 FT; and return to my frequency.' A few minutes later; I cleared a C650 for an ILS Runway YY approach into ZZZ1; which is located about 7 miles north/northwest of ZZZ. Seeing that the C650's approach might conflict with the climb out of aircraft X; I contacted ZZZ GCA while aircraft X was approximately 2 mile final and gave them traffic information on the C650. The GCA Controller responded; 'Traffic observed.' About this time; a Handoff Controller was plugging in to assist me at the position and he heard me make this call as I explained to him the traffic situation. About a minute or so later; we observed aircraft X; 2 to 3 miles north of ZZZ at 3;000 FT on a converging course with the C650; about 5 miles east of ZZZ1 also at 3;000 FT; westbound. My Handoff called the GCA to instruct them to turn aircraft X westbound immediately for traffic and also climb it to 4;000 FT. Simultaneously; I called ZZZ1 Tower and issued a traffic alert for the C650 just as the CA alert was going off on my display. Thankfully; the C650 started descending on the approach and aircraft X turned in time to avoid a calamity. Later; I had a phone conversation on a non-recorded line with the GCA Controller. During that conversation; he explained that he had issued the missed approach instructions to aircraft X and then turned control of the aircraft over to the Final Controller. However; it was the Final Controller whom I had issued the traffic information to and who replied that the traffic was observed. I explained to the Controller whom I had on the phone that it was imperative that the other Controller understand that he was accepting responsibility for separating from the exchanged traffic; even if that meant giving the aircraft a stop and go to delay it's climb out; extending its upwind before allowing it to turn to the 360 heading; or requesting an alternate climb out. This was not withstanding the climb out instructions issued by me previously. I explained that he basically should have done anything but what he did! Recommendation; if I had it to do all over again; I would have given very specific suggestions to the GCA Controller on how to make the assigned climb out work; or asked him to advise me if he required a different climb out. Many times these controllers at military installations are not experienced and need to be properly trained on the creative use of control instructions to avoid a suspected conflict.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.