NMM MIL CTLR FORGETS TO INITIATE AUTOMATION CORRECTIONS TO CHANGED BE40 DATA BLOCK AND ACFT ENTERS GPT APCH CTL AIRSPACE WITHOUT A HDOF.
Synopsis
NMM MIL CTLR FORGETS TO INITIATE AUTOMATION CORRECTIONS TO CHANGED BE40 DATA BLOCK AND ACFT ENTERS GPT APCH CTL AIRSPACE WITHOUT A HDOF.
Narrative
I WAS WORKING AT NMM RATCF IN THE SUPVR 1 POS (EVERYTHING COMBINED) AND HAD A BE40 MAKING PRACTICE APCHS AT MEI. AFTER HIS LAST APCH; HE WAS GOING ON DOWN TO GPT. I CLRED HIM TO GPT AND CLBED HIM TO 12000 FT. I CHANGED HIS BEACON CODE FOR THE NEW FLT PLAN AND HE NEVER TAGGED UP (DATA BLOCK). I DIDN'T REALIZE THAT THE ACFT DIDN'T COME UP ON HIS NEW DATA BLOCK AND HE ENTERED THE ADJACENT SECTOR'S AIRSPACE WITHOUT A HDOF. THIS IS NOT AN UNCOMMON PROB AT THIS FACILITY. WE PROBABLY HAVE 30-40 ACFT A DAY THAT COME IN; DO APCHS; THEN DEPART ON A NEW FLT PLAN. THERE'S SEVERAL THINGS THAT CAN CAUSE THE DATA TAG NOT TO TAG UP. THE OLD FLT PLAN MUST BE REMOVED; THE OLD DATA TAG MUST BE DROPPED; THE ACFT MUST BE WITHIN A CERTAIN DISTANCE OF THE DEP POINT. THE ONLY THING I CAN THINK OF THAT MIGHT HELP TO ALLEVIATE THIS PROB IS TO HAVE THE SYS SET UP SO THAT ANY ACFT ON A DISCRETE BEACON AND WITHIN YOUR ALT STRUCTURE AND WITHOUT AN ASSOCIATED DATA TAG; WILL AUTOMATICALLY FLASH TO DRAW ATTN TO ITSELF.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.