DELAY IN TRANSFER OF ATC JURISDICTION SET UP POTENTIAL LOSS OF SEPARATION BETWEEN TWO ACR.

1988-03 · NASA ASRS report 83605

Date: 1988-03 · Aircraft: Large Transport; Low Wing; 3 Turbojet Eng

Anomalies: conflict-airborne-conflict|other-no-specific-anomaly-occurred

Synopsis

DELAY IN TRANSFER OF ATC JURISDICTION SET UP POTENTIAL LOSS OF SEPARATION BETWEEN TWO ACR.

Narrative

ACR X WAS AT FL330 ON J209 EBOUND IN THE VICINITY OF CLT. ACR Y WAS AT FL330 CAE DIRECT PSK. THESE TWO ROUTINGS CROSS APPROX 60 NM NORTH OF CAE VORTAC. THE JACKSONVILLE ATLANTA CENTER BOUNDARY IS APPROX 40 NM NORTH OF CAE VORTAC. I WAS WORKING THE RADAR AND MANUAL POSITIONS (COMBINED) AT SECTOR 31 ATLANTA CENTER. I WAS IN CONTACT AND WORKING ACR X WHEN JAX CENTER INITIATED AN AUTOMATED HANDOFF OF ACR Y TO ME. I NOTICED THAT THE TWO ACFT WERE IN CONFLICT. BEFORE ACCEPTING THE HANDOFF I CALLED JAX CENTER R69 TO DESCEND ACR Y TO FL290. THE CALL WAS DELAYED BECAUSE I DISCOVERED R31 DOES NOT HAVE A HANDOFF LINE (VOICE LINE) TO SEC 69 AT JAX CENTER. I WAS UNAWARE OF THIS BECAUSE OF OUR NEW SECTOR CONFIGN. THE CALL WAS COMPLETED AND R69 JAX DESCENDED ACR Y TO FL 290. I ACCEPTED THE HANDOFF ON Y AND THE TRACK START BEGAN FLASHING FAIL. THE DATA BLOCK THEN JUMPED TO ANOTHER TARGET AND THE MODE C READOUT WENT TO XXX FORMAT (UNRELIABLE INFORMATION). A FEW SECONDS LATER THE CONFLICT ALERT ACTIVATED. I WAS NOT TALKING TO ACR Y YET SO I CALLED R69 JAX AGAIN TO GET AN ALTITUDE REPORT. R69 DID NOT RESPOND TO THE CALL. I WAS RUNNING OUT OF ROOM SO I HUNG UP AND TURNED ACR X TO A 360 DEG HEADING. THE CTLR WORKING THE SECTOR NEXT TO ME CALLED R69 JAX AND ASKED FOR AN ALTITUDE REPORT ON ACR Y. R69 JAX REPLIED Y WAS OUT OF FL322 AND EXPEDITING HIS DESCENT. R69 JAX ADVISED HIS COMPUTER DID NOT INDICATE THAT I HAD ACCEPTED THE HANDOFF. THE CTLR NEXT TO ME CALLED RADAR CONTACT AND Y WAS SWITCHED TO MY FREQUENCY. SEPARATION WAS ESTABLISHED AT APPROX 8 NM AND ACR X WAS CLRED ON COURSE. CALLBACK CONVERSATION WITH REPORTER REVEALED THE FOLLOWING: LONG CONVERSATION WHICH INCLUDED RUNDOWN BY RPTR ON EQUIP PROBLEMS AT ZTL. ALSO BRIEFED ANALYST ON EFFECTS OF EECP AT ZTL. THERE WAS NO LOSS OF SEPARATION IN THIS INCIDENT BECAUSE HE TURNED ACR X BEFORE LAT SEP WAS LOST. SINCE INCIDENT THERE HAS BEEN A LANDLINE INSTALLED BETWEEN ZTL R-31 AND ZJX R-69. THREE PARALLEL AIRWAYS J-14; J-208; AND J-209 ARE DEST EXCLUSIVE AND ARE ALL HEAVY TFC AIRWAYS. J-209 IS ALSO PARALLEL TO ZJX AREA BOUNDARY AND IS ONLY ABOUT 1.5 MIN FLT TIME FROM BOUNDARY. RPTR STATES THAT THERE IS PROBLEM WITH GETTING EQUIP PROBLEMS RECORDED AND MADE MATTER OF THE RECORD IN ZTL FAC. SAYS SUPVR WAS THROWING AWAY RADAR BULLSEYE FORMS THAT HE WAS TURNING IN REF THE MAIDEN; N.C. RADAR SITE QUALITY OF RADAR DATA. ALSO SAYS HE HAS SUBMITTED UCR FORMS AND HAS RECEIVED NO REPLIES FOR MORE THAN 45 DAYS SO FAR.

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.