Aircraft entered adjacent facility airspace without a handoff.

Attributes
ACN	118187
Time
Date	198907
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : lan
State Reference	MI
Altitude	msl bound lower : 23000 msl bound upper : 23000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zau
Operator	other
Make Model Name	Fighter
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Experience	controller radar : 3
ASRS Report	118187
Person 2
Affiliation	government : military
Function	flight crew : captain oversight : pic
Qualification	pilot : military
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

This event did not involve 2 aircraft in conflict, it was a situation where the aircraft described above entered the airspace of another sector in a different ARTCC without a handoff. It occurred shortly after I had assumed duties at the pmm sector at ZAU. The first task I had performed after sitting down was to release control of an mke area inbound aircraft to the squib sector, which was followed by coordination of an altitude for an aircraft entering the bae sector. After completing this, I answered the ZAU/zcc landline from lan sector. They were asking if I was going to handoff the aircraft in question. This is when I noticed the data block of fgt X had a 'carrot' symbol on it, indicating that the aircraft would not automatic handoff since I still had control of the data block.

Original NASA ASRS Text

Title: ACFT ENTERED ADJACENT FAC AIRSPACE WITHOUT A HANDOFF.

Narrative: THIS EVENT DID NOT INVOLVE 2 ACFT IN CONFLICT, IT WAS A SITUATION WHERE THE ACFT DESCRIBED ABOVE ENTERED THE AIRSPACE OF ANOTHER SECTOR IN A DIFFERENT ARTCC WITHOUT A HANDOFF. IT OCCURRED SHORTLY AFTER I HAD ASSUMED DUTIES AT THE PMM SECTOR AT ZAU. THE FIRST TASK I HAD PERFORMED AFTER SITTING DOWN WAS TO RELEASE CTL OF AN MKE AREA INBND ACFT TO THE SQUIB SECTOR, WHICH WAS FOLLOWED BY COORD OF AN ALT FOR AN ACFT ENTERING THE BAE SECTOR. AFTER COMPLETING THIS, I ANSWERED THE ZAU/ZCC LANDLINE FROM LAN SECTOR. THEY WERE ASKING IF I WAS GOING TO HANDOFF THE ACFT IN QUESTION. THIS IS WHEN I NOTICED THE DATA BLOCK OF FGT X HAD A 'CARROT' SYMBOL ON IT, INDICATING THAT THE ACFT WOULD NOT AUTO HANDOFF SINCE I STILL HAD CONTROL OF THE DATA BLOCK.

Data retrieved from NASA's ASRS site as of August 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.