ZDV CTLR DOES NOT FOLLOW AUTOMATED INFO XFER PROCS CORRECTLY RESULTING IN AN OPDEV.

Date: 2000-07 · Aircraft: A319 · Phase: cruise

Anomalies: airspace-violation-all-types|deviation-discrepancy-procedural-published-material-policy

Synopsis

ZDV CTLR DOES NOT FOLLOW AUTOMATED INFO XFER PROCS CORRECTLY RESULTING IN AN OPDEV.

Narrative

I WAS WORKING SECTOR 9 (CBF HIGH) IN ZDV. I HANDED ACR X TO SECTOR 15; A WRONG SECTOR. THEN A LITTLE LATER; AFTER MAKING CERTAIN THAT SECTOR 15 DID IN FACT HAVE THE HDOF; I SHIPPED ACR X TO SECTOR 15; AS WOULD BE THE NORMAL PROC. THE PROB IS; I WAS SUPPOSED TO HAND OFF TO SECTOR 16 AND WAIT TO SEE IF THEY HANDED OFF TO SECTOR 15 OR NOT. WHEN I OBSERVED SECTOR 15 WITH THE HDOF; I THOUGHT SECTOR 16 HAD HANDED TO SECTOR 15. WHEN IN FACT I; SECTOR 9; HAD GONE TO SECTOR 15. SECTOR 9 HAS A VERY DIFFICULT TIME KNOWING THE HISTORY OF THE DATA BLOCK AND DEPENDING ON HOW QUICKLY SECTOR 15 ACCEPTS THE HDOF; SECTOR 9 HAS ALMOST NO WAY TO KNOW THAT THEY HAVE MADE A MISTAKE. OUR FLASH-THROUGH PROC FOR DEN LNDG TFC SETS THE SECTOR 9 CTLR UP FOR AN ERROR; AND THE CONSEQUENCES COULD BE VERY SERIOUS. I ENTERED SECTOR 16'S AIRSPACE WITHOUT A HDOF; AND WHAT'S WORSE -- DUE TO OUR PROCS; I ACCIDENTALLY GAVE AWAY CTL IN ANOTHER PERSON'S HIGH ALT SECTOR 16 TO LOW ALT SECTOR 15. WHEN ACR X LEFT MY AIRSPACE; EVERYTHING SEEMED NORMAL; BUT IN FACT I HAD CREATED A VERY DANGEROUS SIT AND I COULD NOT TELL ANYTHING WAS WRONG.

More incidents for this aircraft family →

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