ACR Y HAD LTSS FROM ACR X. SYS ERROR.

Date: 1991-08 · Aircraft: Large Transport; Low Wing; 3 Turbojet Eng

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

Synopsis

ACR Y HAD LTSS FROM ACR X. SYS ERROR.

Narrative

ACR X ENRTE TO DFW AT FL330. ACR Y NEBOUND ORIGINALLY AT FL330 AND THE R-MAN DSNDED TO FL310 FOR TFC. AT THE TIME OF THE INCIDENT I WAS BRIEFING MY RELIEF. JUST PRIOR TO ACR Y BEING CLBED I TOLD MY RELIEF THAT ACR Y NEEDED TO GO BACK TO FL330 WHEN CLR OF TFC. JUST PRIOR TO UNPLUGGING I HEARD THE R-MAN CLB ACR Y TO FL330. I MARKED THE STRIP AND UNPLUGGED. ONLY 3 OR 4 ACFT TO THE SECTOR. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR EXPERIENCE 1 YR FPL AND 4 YRS MIL. ACR X AND Y PROX 3 MI AND 1000 FT. RPTR STATED WHEN CONFLICT ALERT ACTIVATED THE RADAR CTLR DSNDED ACR Y BACK TO FL310. THE RADAR CTLR HAD STATED HE FORGOT ACR X WAS AT FL330 DATA TAGS WERE OVERLAPPING SO HE CLBED ACR Y. SYS ERROR WAS FILED. SUPPLEMENTAL INFO FROM ACN 187432: I JUST SAT DOWN TO WORK SECTOR D-46 AT ZLC. DURING THE BRIEFING I WAS ADVISED THAT ACR Y WAS AT FL310 FOR TFC AND WAS TO BE CLBED TO FL330 CLR OF TFC. DURING THE BRIEFING; THE CLRNC TO FL330 WAS GIVEN. I STARTED TO SEQUENCE FLT PROGRESS STRIPS WHEN I NOTICED THE CONFLICT ALERT GO OFF. I ASKED THE RADAR CTLR WHAT WAS GOING ON. HE SAID THAT ACR Y WAS CLBING. I ASKED IF HE WAS ASSIGNED FL310 (THE DATA BLOCK SHOWED FL330). HE SAID HE WAS ASSIGNED FL330. I ASKED 'WHAT ABOUT ACR X.' IT WAS AT THIS TIME WE REALIZED WHAT HAD HAPPENED.

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