A RADAR CTLR BUSY VECTORING ACFT DUE TO WX ALLOWS AN ATX BE58 AND AN OPPOSITE DIRECTION L1011 TO PASS AT THE SAME ALT APPROX ONE HALF MI APART.

1997-09 · NASA ASRS report 379602

Date: 1997-09 · Aircraft: Baron 58/58TC · Phase: climb

Anomalies: atc-issue-all-types|conflict-airborne-conflict|deviation-discrepancy-procedural-published-material-policy

Synopsis

A RADAR CTLR BUSY VECTORING ACFT DUE TO WX ALLOWS AN ATX BE58 AND AN OPPOSITE DIRECTION L1011 TO PASS AT THE SAME ALT APPROX ONE HALF MI APART.

Narrative

THE EVENT WAS AN NMAC WITH A COMMERCIAL AIRLINER. THE ENTIRE INCIDENT TOOK PLACE OVER ABOUT 30-40 SECONDS. WHILE ON A SW/W VECTOR FROM ATL DEP CTL AND CLRED FOR A CLB FROM 4000 FT TO 5000 FT MSL; I RECOGNIZED ANOTHER ACFT AT MY 2-3 O'CLOCK POS AND ABOUT 4 MI AWAY (NO TA WAS GIVEN AND THE DEP FREQ WAS CONGESTED). AFTER DETERMINING THEIR DIRECTION OF FLT AND ALT (THEY WERE ALSO CLBING); IT BECAME OBVIOUS THAT WE WERE ON A COLLISION COURSE. I DEVIATED FROM MY ASSIGNED HDG WITH A DSNDING TURN TO THE L. THE OTHER ACFT RESPONDED WITH A CLBING L TURN. I ESTIMATE THAT WE WERE WITHIN 100-300 FT OF A COLLISION. AFTER THE DEV; I NOTIFIED ATL DEP CTL OF A 'NEAR MISS' AND VERIFIED THAT I WAS CLRED FOR CLB TO 5000 FT. THE CTLR VERIFIED MY CLB AND INDICATED THAT THEY WERE 'LOOKING INTO THE INCIDENT.' PRIOR TO BEING HANDED OFF TO THE NEXT DEP CTLR; I RESTATED MY CONCERN ABOUT THE INCIDENT TO THE CTLR. I STATED THAT A COLLISION WAS AVOIDED BY APPROX 1-2 SECONDS. THE CTLR RESPONDED BY STATING; 'WE ARE INVESTIGATING AND WE WEREN'T SURE WHY HE WAS DOWN THAT LOW.' I ASSUMED THAT HE MEANT THE OTHER ACFT. NO OTHER INFO WAS GIVEN TO ME. I AM UNSURE AS TO THE TYPE OF ACFT OR THE AIRLINE TO WHICH THE OTHER ACFT WAS AFFILIATED. ADDITIONALLY; THEY WERE NOT ASSIGNED THE SAME RADIO FREQ THAT I WAS USING SO I COULDN'T HEAR THEIR RESPONSES. I DSNDED FROM 4800 FT TO 4000 FT AND TURNED L BY APPROX 40 DEGS. I ESTIMATE THE OTHER ACFT CLBED 500- 1000 FT ABOVE HIS/HER ALT AND TURNED L BY 30-80 DEGS. SUPPLEMENTAL INFO FROM ACN 379607: ACR Y L1011 AND ATX X BE58 NMAC; APPROX 10 MI SW ATL AT 5000 FT. THE FOLLOWING FACTORS WERE INVOLVED: LACK OF STAFFING DURING ABNORMAL WX CONDITIONS; MULTIPLE COORD; WX CONDITIONS THAT WERE CAUSING ACFT TO DEV FROM NORMAL DEP ARR RTES; TFC DENSITY; UNUSUAL REQUESTS; FREQ CONGESTION; XOVER TFC; MISAPPLICATION OF DEP PROCS BY THE TWR. I TURNED THE L1011 TO A HDG OF 150 DEGS FOR COURSE DIVERGENCE AND TO CONTINUE CLBING THE L1011. THE L1011 AND THE BE58 WERE AT THE SAME ALT. TCASII ACTIVATED AND DIRECTED THE L1011 TO DSND. THE BE58 SAW THE L1011 AT HIS ALT AND HE DSNDED AS WELL. BOTH ACFT WERE DSNDING TO AVOID BUT NOTHING WAS BEING RESOLVED. CONFLICT ALERT ACTIVATED AT 1.5 MI BUT 5 DATA TAGS WERE ALL OVERLAPPING. I COULD NOT TELL WHO WAS IN CONFLICT WITH WHO AND WAS UNABLE TO REACT TO THE ALERT.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

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.

Which aircraft types can I filter by?

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.

Is FlightFinder free to use?

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.

Where does the route data come from?

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.