Narrative:

Cga X, a bjc departure, on a rocki 3 departure, blue mesa transition on his route of flight, in flat track, level at FL310. Cga X did not automatic handoff to sector 25. Cga X was 3.75 mi from the boundary along his route of flight, 2.5 mi to the closest boundary point. I initiated a handoff to sector 25. 2 seconds after the handoff, conflict alert activated between cga X and air carrier Y, a den arrival, out of FL323 descending to FL270. The conflict was traffic in sector 25. 26 seconds later, no coordination had been initiated by sector 25, so I turned cga X 20 degrees right to avoid the traffic. At about this time, cga X crossed the sector 5/25 boundary, without a handoff. I coordinated the turn with sector 25. Moments later, I turned cga X further to a 255 degree heading. Sector 25 called back to ask why cga X was in their airspace. They did not know who he was even though they had strips and flight plan data on the aircraft. After cga X and air carrier Y were no longer a traffic factor, I cleared cga X on course to tnp, re-handed the aircraft off to sector 25. 15-20 seconds later, sector 25 still had not taken the handoff, and I had to call the sector to take the handoff. When I last observed the limited data block on air carrier Y, he was level at FL330. I did not have a full data block displayed. Automatic handoff did not occur, and I had to initiate the handoff. I had no flight data on air carrier Y, the aircraft did not transition my airspace. Sector 25 failed to perform a proper traffic scan and failed to maintain awareness of potential conflicts before descending air carrier Y. When conflict alert activated, sector 25 failed to provide restrs or clrncs in a timely manner forcing me to take independent action to avoid an operational error.

Google
 

Original NASA ASRS Text

Title: ARTCC RADAR CTLR ATTEMPTING TO MAKE AN AUTOMATED HDOF TO THE ADJACENT SECTOR, ALLOWED A CGA ACFT TO ENTER THE AIRSPACE WITHOUT A PROPER HDOF. THE CTLR INITIATED A RADAR VECTOR TO AVOID LOSS OF SEPARATION FROM A DSNDING ACR ACFT.

Narrative: CGA X, A BJC DEP, ON A ROCKI 3 DEP, BLUE MESA TRANSITION ON HIS RTE OF FLT, IN FLAT TRACK, LEVEL AT FL310. CGA X DID NOT AUTO HDOF TO SECTOR 25. CGA X WAS 3.75 MI FROM THE BOUNDARY ALONG HIS RTE OF FLT, 2.5 MI TO THE CLOSEST BOUNDARY POINT. I INITIATED A HDOF TO SECTOR 25. 2 SECONDS AFTER THE HDOF, CONFLICT ALERT ACTIVATED BTWN CGA X AND ACR Y, A DEN ARR, OUT OF FL323 DSNDING TO FL270. THE CONFLICT WAS TFC IN SECTOR 25. 26 SECONDS LATER, NO COORD HAD BEEN INITIATED BY SECTOR 25, SO I TURNED CGA X 20 DEGS R TO AVOID THE TFC. AT ABOUT THIS TIME, CGA X CROSSED THE SECTOR 5/25 BOUNDARY, WITHOUT A HDOF. I COORDINATED THE TURN WITH SECTOR 25. MOMENTS LATER, I TURNED CGA X FURTHER TO A 255 DEG HDG. SECTOR 25 CALLED BACK TO ASK WHY CGA X WAS IN THEIR AIRSPACE. THEY DID NOT KNOW WHO HE WAS EVEN THOUGH THEY HAD STRIPS AND FLT PLAN DATA ON THE ACFT. AFTER CGA X AND ACR Y WERE NO LONGER A TFC FACTOR, I CLRED CGA X ON COURSE TO TNP, RE-HANDED THE ACFT OFF TO SECTOR 25. 15-20 SECONDS LATER, SECTOR 25 STILL HAD NOT TAKEN THE HDOF, AND I HAD TO CALL THE SECTOR TO TAKE THE HDOF. WHEN I LAST OBSERVED THE LIMITED DATA BLOCK ON ACR Y, HE WAS LEVEL AT FL330. I DID NOT HAVE A FULL DATA BLOCK DISPLAYED. AUTO HDOF DID NOT OCCUR, AND I HAD TO INITIATE THE HDOF. I HAD NO FLT DATA ON ACR Y, THE ACFT DID NOT TRANSITION MY AIRSPACE. SECTOR 25 FAILED TO PERFORM A PROPER TFC SCAN AND FAILED TO MAINTAIN AWARENESS OF POTENTIAL CONFLICTS BEFORE DSNDING ACR Y. WHEN CONFLICT ALERT ACTIVATED, SECTOR 25 FAILED TO PROVIDE RESTRS OR CLRNCS IN A TIMELY MANNER FORCING ME TO TAKE INDEPENDENT ACTION TO AVOID AN OPERROR.

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.