ACR Y HAD LTSS FROM ATX X. SYS ERROR.

Date: 1995-06 · Aircraft: King Air C90 E90

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

Synopsis

ACR Y HAD LTSS FROM ATX X. SYS ERROR.

Narrative

ACR Z (B737) INBOUND TO ELP WAS ISSUED A CLRNC TO FL210 FOR: ATX X (OUTBOUND FROM ELP) CLBING TO FL200 AND ACR Y (OUTBOUND FROM ELP) CLBING TO FL200; BOTH DEPS WERE LATERALLY SEPARATED. X WAS CLRED DIRECT TO TCS AND WAS ISSUED Z AS TFC. TO HELP PROVIDE Z AND Y SOME SVC THEY WERE BOTH ISSUED TURNS; Z WAS TURNED 15 DEGS L AND Y WAS TURNED 10 DEGS R; AND WERE BOTH ISSUED THE TFC. WHEN Z WAS CLR HE WAS ISSUED A DSCNT TO FL130 AND THE ELP ALTIMETER (I GAVE HIM THE CLRNC FIRST SINCE HE WAS LNDG AND ALSO THERE WAS SOME OTHER TFC FOR HIM). I NOTICED THE OVERTAKE THAT Y HAD ON X; BUT WAS DISTRACTED BY 2 THINGS: A RADAR ASSOCIATE CAME TO HELP AND I WAS PREPARING FOR A BRIEFING BUT A PRIORITY CTL ACTION INTERRUPTED AS FOLLOWS: A PA34 WAS WBOUND LNDG LRU AT FL200 AND WAS TFC FOR Z INBOUND TO ELP. ELP APCH CALLED AND I ANSWERED TO COORDINATE A HDG AND LOWER FOR Z. ELP APCH REQUESTED A RADAR VECTOR OF 110 DEGS AND DSNDING TO FL110. I AGREED AND ADVISED THAT PA34 WOULD REMAIN ABOVE Z AND I WOULD PROTECT THE Z. AS I CAME BACK ONTO THE FREQS; THE RADAR ASSOCIATE SAID THAT PA34 HAD JUST CHKED ON FREQ BUT HAD NOT BEEN ANSWERED. I ANSWERED PA34 AND ADVISED I WOULD HAVE LOWER MOMENTARILY. THEN; I WENT BACK TO Y AND GAVE A CLRNC TO CLB TO FL250 EXPECTING THE B727 TO CLB FAST ENOUGH TO 'TOP' X. CONFLICT ALERT ACTIVATED AND I ISSUED A 30 DEG L TURN TO Y AND A 30 DEG R TURN TO X (RESPONSES WERE RECEIVED). I ADVISED Y TO EXPEDITE THROUGH FL210 AND Y RESPONDED THAT HE HAD THE TFC IN SIGHT. Y WAS AGAIN ASKED TO EXPEDITE THROUGH FL210 AND HE RPTED LEAVING FL215. THE 2 ACFT WERE RESUMED ON THEIR COURSES.

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