Crw flight data controller described operational deviation when aircraft with no data block informat...

Narrative:

I was working TRACON data and I was also the ocic of the shift. Due to lack of staffing; operational supervisor mr X was working south radar and he was giving a relief briefing to atcs mr Y. In the middle of the briefing mr X came upon aircraft X strip; a northbound overflt at 8000 ft. The aircraft was not on the scope and mr X and I thought it was a pointout that he received earlier. Later in the briefing ZID center controller called on the 01 line and asked mr X if he was still working aircraft X. Mr X transmitted to the aircraft and he answered. ZID ordered mr X to climb aircraft X to 9000 ft for traffic. The aircraft was observed about 5 mi inside of ZID's airspace; however; aircraft X's aircraft data tag had dropped and mr X had not handed off the aircraft to ZID (less than the applicable separation minima existed between the aircraft and adjacent airspace without prior approval). Another 8000 ft aircraft was observed approximately 8 mi north of aircraft X but that aircraft was descending and at this time aircraft X was climbing. Mr X called ZID watch desk and they determined there was no loss of separation and operational supervisor mr X advised he would handle the situation from there. I advised the atm; mr west; the operational deviation.

Original NASA ASRS Text

Title: CRW FLT DATA CTLR DESCRIBED OPDEV WHEN ACFT WITH NO DATA BLOCK INFO WAS ALLOWED TO ENTER ZID AIRSPACE WITHOUT COORD OR HDOF.

Narrative: I WAS WORKING TRACON DATA AND I WAS ALSO THE OCIC OF THE SHIFT. DUE TO LACK OF STAFFING; OPERATIONAL SUPVR MR X WAS WORKING S RADAR AND HE WAS GIVING A RELIEF BRIEFING TO ATCS MR Y. IN THE MIDDLE OF THE BRIEFING MR X CAME UPON ACFT X STRIP; A NBOUND OVERFLT AT 8000 FT. THE ACFT WAS NOT ON THE SCOPE AND MR X AND I THOUGHT IT WAS A POINTOUT THAT HE RECEIVED EARLIER. LATER IN THE BRIEFING ZID CTR CTLR CALLED ON THE 01 LINE AND ASKED MR X IF HE WAS STILL WORKING ACFT X. MR X XMITTED TO THE ACFT AND HE ANSWERED. ZID ORDERED MR X TO CLB ACFT X TO 9000 FT FOR TFC. THE ACFT WAS OBSERVED ABOUT 5 MI INSIDE OF ZID'S AIRSPACE; HOWEVER; ACFT X'S ACFT DATA TAG HAD DROPPED AND MR X HAD NOT HANDED OFF THE ACFT TO ZID (LESS THAN THE APPLICABLE SEPARATION MINIMA EXISTED BTWN THE ACFT AND ADJACENT AIRSPACE WITHOUT PRIOR APPROVAL). ANOTHER 8000 FT ACFT WAS OBSERVED APPROX 8 MI N OF ACFT X BUT THAT ACFT WAS DSNDING AND AT THIS TIME ACFT X WAS CLBING. MR X CALLED ZID WATCH DESK AND THEY DETERMINED THERE WAS NO LOSS OF SEPARATION AND OPERATIONAL SUPVR MR X ADVISED HE WOULD HANDLE THE SITUATION FROM THERE. I ADVISED THE ATM; MR W; THE OPDEV.

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

Attributes
ACN	733163
Time
Date	200703
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : hvq.airport
State Reference	WV
Altitude	msl bound lower : 8000 msl bound upper : 9000
Environment
Light	Daylight
Person 1
Affiliation	government : faa
Function	controller : flight data
Qualification	controller : radar
Experience	controller radar : 24
ASRS Report	733163
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	flight crew : took evasive action
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Crw flight data controller described operational deviation when aircraft with no data block information was allowed to enter ZID airspace without coordination or handoff.