SUS CTLR DESCRIBES OPDEV BECAUSE OF FAILURE TO ENSURE THAT AN IFR DEP WAS PROPERLY TAGGED IN COMPLIANCE OF AN LOA.
Synopsis
SUS CTLR DESCRIBES OPDEV BECAUSE OF FAILURE TO ENSURE THAT AN IFR DEP WAS PROPERLY TAGGED IN COMPLIANCE OF AN LOA.
Narrative
AFTER VERBAL RELEASE FROM RADAR CTLR; I CLRED ACFT FOR TKOF. RADAR CTLR ADVISED OF MULTIPLE FLT PLANS IN SYS. ACFT IS OFF DEP END OF RWY. ACFT ASKED FOR FREQ CHANGE TO DEP. I GAVE FREQ CHANGE. I OBSERVED ACFT IDENT AND LEAVE ASSIGNED ALT. DATA TAG DID NOT ACQUIRE. LOA MAKES ME RESPONSIBLE FOR DATA ACQUISITION. AFTER OBSERVING IDENT AND CLB; I ASSUMED RADAR CTLR HAD RADAR CONTACT AND DID NOT PERFORM VERBAL HDOF. ACFT LATER ENTERED MIZZU APCH AIRSPACE WITHOUT BEING HANDED OFF. CONTRIBUTING FACTORS: LOA THAT PUTS RESPONSIBILITY OF DATA ACQUISITION ON THE VFR TWR CTLR WHO IS SUPPOSED TO BE LOOKING OUT THE WINDOW AND NOT WATCHING THE RADAR DISPLAY. FLT DATA STRIP PRINTER BEING OTS. THIS DID NOT ALLOW US TO RECEIVE ALL FLT PLANS. THUS; NOT ALLOWING THE TWR OPERATORS TO REMOVE DUPLICATES. RADAR CTLR'S WORKLOAD. KEEPING HIM FROM ANSWERING THE INTERPHONE FOR COORD. ACTIONS OR INACTIONS: JUST BECAUSE THE RADAR CTLR CLBS AN ACFT ON INITIAL CONTACT DOES NOT MEAN HE IS RADAR IDENTED. TWR CTLR SHOULD STILL VERBALLY HAND OFF IF DATA TAG DOES NOT ACQUIRE.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.