Narrative:

I took control of the sector after observing the previous controller for 10-15 mins. Sector workload prevented a standard briefing. (The serving radar site was OTS, WX deviations were occurring, and traffic was moderate.) the king air was climbing in the adjoining sector's airspace when I assumed control of the position. I attempted to send the king air to the next sector's frequency, however, the king air failed to acknowledge the change. I was immediately distracted by conversations (from the d-side controller) about a land line outage I had not been briefed on, and (from the area supervisor) about my request for a return of the radar site being denied. These two events prevented me from realizing that the king air had not acknowledged the change. A short time later, the king air requested to level at FL230 instead of the previously requested FL250. The full data block on the aircraft was no longer displayed as it was out of my sector. I searched my memory, located the aircraft and brought the data block back up to confirm. The aircraft had traversed the adjoining sector and was south of their boundary by a few mi. The adjoining sector controller had failed to point the king air out to the sector south of his airspace and an operational deviation had occurred.

Google
 

Original NASA ASRS Text

Title: ARTCC CTLR RELIEVES A SECTOR AT ZMP AND INSTRUCTS A KING AIR IN ADJOINING AIRSPACE TO CONTACT THE SECTOR. THE KING AIR DOES NOT ACKNOWLEDGE THE FREQ CHANGE AND CTLR IS DISTRACTED AND FORGETS TO NOTIFY THE SECTOR.

Narrative: I TOOK CTL OF THE SECTOR AFTER OBSERVING THE PREVIOUS CTLR FOR 10-15 MINS. SECTOR WORKLOAD PREVENTED A STANDARD BRIEFING. (THE SERVING RADAR SITE WAS OTS, WX DEVS WERE OCCURRING, AND TFC WAS MODERATE.) THE KING AIR WAS CLBING IN THE ADJOINING SECTOR'S AIRSPACE WHEN I ASSUMED CTL OF THE POS. I ATTEMPTED TO SEND THE KING AIR TO THE NEXT SECTOR'S FREQ, HOWEVER, THE KING AIR FAILED TO ACKNOWLEDGE THE CHANGE. I WAS IMMEDIATELY DISTRACTED BY CONVERSATIONS (FROM THE D-SIDE CTLR) ABOUT A LAND LINE OUTAGE I HAD NOT BEEN BRIEFED ON, AND (FROM THE AREA SUPVR) ABOUT MY REQUEST FOR A RETURN OF THE RADAR SITE BEING DENIED. THESE TWO EVENTS PREVENTED ME FROM REALIZING THAT THE KING AIR HAD NOT ACKNOWLEDGED THE CHANGE. A SHORT TIME LATER, THE KING AIR REQUESTED TO LEVEL AT FL230 INSTEAD OF THE PREVIOUSLY REQUESTED FL250. THE FULL DATA BLOCK ON THE ACFT WAS NO LONGER DISPLAYED AS IT WAS OUT OF MY SECTOR. I SEARCHED MY MEMORY, LOCATED THE ACFT AND BROUGHT THE DATA BLOCK BACK UP TO CONFIRM. THE ACFT HAD TRAVERSED THE ADJOINING SECTOR AND WAS S OF THEIR BOUNDARY BY A FEW MI. THE ADJOINING SECTOR CTLR HAD FAILED TO POINT THE KING AIR OUT TO THE SECTOR S OF HIS AIRSPACE AND AN OPDEV HAD OCCURRED.

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.