APCH CTLR FORGOT TO MAKE A MANUAL HDOF TO HIS NEXT SECTOR DUE TO THE NEXT CTLR BEING BUSY ON THE FIRST TRY AND THEN SUBSEQUENTLY BOTH PARTIES FORGETTING TO CALL EACH OTHER.

Date: 2000-04 · Aircraft: Baron 55/Cochise · Phase: cruise

Anomalies: deviation-discrepancy-procedural-published-material-policy|other-lock-atc-hand-off

Synopsis

APCH CTLR FORGOT TO MAKE A MANUAL HDOF TO HIS NEXT SECTOR DUE TO THE NEXT CTLR BEING BUSY ON THE FIRST TRY AND THEN SUBSEQUENTLY BOTH PARTIES FORGETTING TO CALL EACH OTHER.

Narrative

WHILE WORKING S RADAR; I HAD A BE55 THAT WAS ON A FLT PLAN (ENRTE) FROM IAG TO TLH. HIS FLT STRIP WAS UNSUCCESSFUL WITH THE NEXT SECTOR; OZR APCH. AN UNSUCCESSFUL FLT PROGRESS STRIP INDICATES THAT A MANUAL HDOF MUST TAKE PLACE; AS WELL AS PASSING MANUAL FLT INFO TO THE NEXT FACILITY. THIS HAPPENS WHEN ONE HOST COMPUTER DOESN'T AGREE WITH THE NEXT; USUALLY TAKING PLACE WHEN 2 DIFFERENT CTRS ARE INVOLVED. IN THIS CASE; ZTL AND ZJX. I WAS WORKING APPROX 6 ACFT; 4 ARRS TO PRIMARY ARPT; AND 2 TO SECONDARY; AS WELL AS THE BE55 ENRTE. ABOUT 7 MI N OF THE BOUNDARY TO OZR AIRSPACE; I CALLED TO MANUALLY COORDINATE THE UNSUCCESSFUL FLT PLAN. THE OZR CTLR SAID SHE WAS BUSY AND SHE WOULD CALL ME RIGHT BACK. SUBSEQUENTLY; I WENT BACK TO SEQUENCING MY ARRS AND FORGOT TO CALL OZR BACK; AND SHE DIDN'T CALL ME 'RIGHT BACK.' THE BE55 ENDED UP 3 MI INTO OZR AIRSPACE BEFORE THE OZR CTLR CALLED. I THEN REALIZED THE BARON HAD ENTERED OZR AIRSPACE WITHOUT A PROPER HDOF. CAUSAL FACTORS WERE THE JAX COMPUTER NOT RECOGNIZING THE FLT PLAN; MY FAILURE TO ENSURE A HDOF; AND THE OZR CTLR NOT TAKING THE INFO WHEN INITIALLY CALLED.

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