Narrative:

I was splitting a super hi sector to combine with another sector. I pointed out the aircraft to sector 12 and handed off the aircraft in his airspace, called sector 16 and handed off the aircraft in his airspace. I gathered up strips and took them to sector 16, came back to my sector and started to clean my scope by suppressing data blocks when I tried to suppress air carrier X. It would not suppress. I looked at the location of air carrier X in chicago's airspace, thought the sector 16 controller had handed aircraft to ZAU. So I punched cancel track button and suppressed the data block. But what had really happened, I had never given sector 16 a handoff. So the aircraft went through 2 sectors without being tracked. The next sector called ZAU and asked if that was air carrier X on code XXXX. ZAU said they didn't know, a sector had pointed it out to them and didn't know where the aircraft had come from, but sector 84 didn't try to identify aircraft. No other aircraft were involved. The chief at ZKC is trying to fire or suspend controllers that have operational deviations, or system errors. This is making the working conditions at ZKC most stressful. Everyone is working on pins and needles. On this situation he suspended my supervisor who has been a controller and supervisor for 23 yrs.

Google
 

Original NASA ASRS Text

Title: ACR ENTERED ADJACENT FAC AIRSPACE WITHOUT A HANDOFF.

Narrative: I WAS SPLITTING A SUPER HI SECTOR TO COMBINE WITH ANOTHER SECTOR. I POINTED OUT THE ACFT TO SECTOR 12 AND HANDED OFF THE ACFT IN HIS AIRSPACE, CALLED SECTOR 16 AND HANDED OFF THE ACFT IN HIS AIRSPACE. I GATHERED UP STRIPS AND TOOK THEM TO SECTOR 16, CAME BACK TO MY SECTOR AND STARTED TO CLEAN MY SCOPE BY SUPPRESSING DATA BLOCKS WHEN I TRIED TO SUPPRESS ACR X. IT WOULD NOT SUPPRESS. I LOOKED AT THE LOCATION OF ACR X IN CHICAGO'S AIRSPACE, THOUGHT THE SECTOR 16 CTLR HAD HANDED ACFT TO ZAU. SO I PUNCHED CANCEL TRACK BUTTON AND SUPPRESSED THE DATA BLOCK. BUT WHAT HAD REALLY HAPPENED, I HAD NEVER GIVEN SECTOR 16 A HANDOFF. SO THE ACFT WENT THROUGH 2 SECTORS WITHOUT BEING TRACKED. THE NEXT SECTOR CALLED ZAU AND ASKED IF THAT WAS ACR X ON CODE XXXX. ZAU SAID THEY DIDN'T KNOW, A SECTOR HAD POINTED IT OUT TO THEM AND DIDN'T KNOW WHERE THE ACFT HAD COME FROM, BUT SECTOR 84 DIDN'T TRY TO IDENTIFY ACFT. NO OTHER ACFT WERE INVOLVED. THE CHIEF AT ZKC IS TRYING TO FIRE OR SUSPEND CTLRS THAT HAVE OPERATIONAL DEVIATIONS, OR SYSTEM ERRORS. THIS IS MAKING THE WORKING CONDITIONS AT ZKC MOST STRESSFUL. EVERYONE IS WORKING ON PINS AND NEEDLES. ON THIS SITUATION HE SUSPENDED MY SUPVR WHO HAS BEEN A CTLR AND SUPVR FOR 23 YRS.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.