DISPATCHER RPT REF ACFT WITH NO TCASII LISTED ON FLT PLAN BUT RESPONDS TO TCASII RA. ATC CALLS WITH FOLLOW-UP.

Date: 1992-09 · Aircraft: Light Transport

Anomalies: deviation-discrepancy-procedural-far|other-no-specific-anomaly-occurred|other-unspecified

Synopsis

DISPATCHER RPT REF ACFT WITH NO TCASII LISTED ON FLT PLAN BUT RESPONDS TO TCASII RA. ATC CALLS WITH FOLLOW-UP.

Narrative

THE FLT I DISPATCHED WAS RETURNING TO THE HUB. WHILE ON DSCNT (IN STEPS) THE TCASII ALARM SOUNDED. THE ACFT AT THAT TIME WAS IN THE CLOUDS. EVEN THOUGH THE BASIC WX WAS CLR EXCEPT FOR ISOLATED CLOUD BANKS; THE CAPT DECIDED TO DEVIATE FROM HIS ASSIGNED ALT BY APPROX 500 FT. AFTER CLRING THE AIRSPACE HE RETURNED TO HIS ASSIGNED ALT (I AGREE WITH HIS ACTION). WHEN THE CAPT GOT BACK TO OPS THERE WAS A MESSAGE TO CALL THE ATC TWR. HE CALLED ME AND 3-WAYED THE CALL TO ATC. ATC STATED THERE WAS NOT TCASII LISTED ON THE CLRNC AND THE ACFT HAD IT INSTALLED. AFTER FOLLOWING UP ON IT; I FOUND OUT THE MAINT CTL SUPVR DIDN'T MAKE AN ENTRY INTO THE COMPUTER SHOWING TCASII INSTALLED; SO THE COMPUTER GENERATED FLT PLAN DIDN'T SHOW THE TCASII FOR ATC. THE CAPT AND I BOTH OVERLOOKED THE ERROR ON THE RELEASE. I ALSO FOUND 7 OTHER ENTRIES THAT WERE NOT MADE ON OTHER ACFT. WORKLOAD IS A MAIN CONTRIBUTOR TO THE PROBLEM. NOT ENOUGH TIME BTWN FLTS DISPATCHED TO FULLY VIEW THE RELEASES ENTIRELY. NOT ENOUGH TIME BTWN FLTS ON THE GND FOR THE CREWS TO VIEW THEIR RELEASES EITHER.

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