SMA X UNAUTH UNCOORD PENETRATION OF ZOB AIRSPACE. ARTCC ARTCC INTERFAC COORD. OPDEV.
Synopsis
SMA X UNAUTH UNCOORD PENETRATION OF ZOB AIRSPACE. ARTCC ARTCC INTERFAC COORD. OPDEV.
Narrative
I WAS WORKING EKN LOW (R1) WHEN THE SECTOR WAS COMBINED WITH BLR (R15). AT THE TIME THE SECTORS WERE COMBINED I WAS WORKING 2 ACFT; SMA X AT 120 FLT PLANNED SHD BSV CAK; AND AN SMA AT 230 NEBOUND GOING DIRECT TO HGR-HAR-ETX- ABE. I HAD BEEN WORKING WBOUND ON J6 AT FL200; HANDED OFF AND SWITCHED TO ZID. I HANDED AN SMA AND SMA X OFF TO R15 AND POINTED OUT AN ACR TO R15 ALSO. I DROPPED THE DATA TAG ON SMA TO CLEAN UP THE EKN SCOPE; I DID THE SAME ON SMA X; HOWEVER; R15 HAD NOT TAKEN THE HDOF AS I HAD THOUGHT. SO INSTEAD OF DROPPING THE DATA TAG; I TOOK THE HDOF BACK WITHOUT REALIZING I WAS DOING SO. THE ACFT PROCEEDED INTO ZCC AIRSPACE WITHOUT A HDOF CREATING AN AIRSPACE VIOLATION. SUPPLEMENTAL INFO FROM ACN 195858. JUST COMBINED THE ELKINS SECTOR WITH THE BLUE RIDGE SECTOR. CLEVELAND CENTER CALLED AND ASKED IF I WAS WORKING THE CODE X S OF MGW. I SAID NO. I LOOKED AT THE NOW CLOSED ELKINS SCOPE AND SAW THE DATA BLOCK ON THE CLOSED SCOPE. I TOLD CLEVELAND CENTER THAT WHEN THE SECTORS COMBINED; HE FORGOT TO HDOF THE SMA X TO MY SECTOR. I DID NOT HAVE A FORCED LIMITED DATA BLOCK ON MY SCOPE.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.