TRACON controller described an airspace incursion event when the data tag on an IFR aircraft failed ...

Narrative:

Aircraft X was handed off to approach from the west. I accepted the hand off; but did not have a strip for the aircraft. After some research; I looked in the fdio and there was no active flight plan for the aircraft. After communication with aircraft X; I confirmed that he did have routing; and was IFR. I then asked approach X to confirm they had flight information on him; and what routing they showed him on. They said he was direct ZZZ and then direct ZZZ1. I then asked aircraft X what his routing was; and he confirmed it was direct ZZZ1. At this time there was still no flight plan information on the aircraft; so I put in a flight plan. In the process of doing this; his call sign dropped off the screen. After getting the flight plan in; and talking to several other aircraft; I completed a scan to confirm where aircraft X was located. I did not see his tag; and assumed it had dropped off. Next; approach Y called asking if I was still working aircraft X; and advised that he was in their airspace. I then called aircraft X to make sure he was still on frequency. After I made sure he was I called approach Y to confirm they were seeing him on radar; because at this time; I was not. I then switched the aircraft to approach Y so that they could identify him. I am not sure how the tag of the aircraft dropped off; but this should not be able to happen. I would recommend that there be a stop in place for aircraft being handed off without having any type of flight plan information; while still being on a NAS code. This aircraft should not have been able to be handed off without have a flight plan; and still be IFR. This is what led to the distraction of having to put a new flight plan in; which evidently led to the tag dropping off. As with any scenario; the controller could try to pay more attention to the aircraft. I don't want to say that I was not paying attention; because I was. In fact; I was at a normal workload steadily performing my duties. I do not feel that I neglected my aircraft at all. Another suggestion would be that when an aircraft is entering or departing the airspace on a NAS code; but not tagged up; the tag highlights of flashes to alert the controller that this is not supposed to be there.

Original NASA ASRS Text

Title: TRACON Controller described an airspace incursion event when the data tag on an IFR aircraft failed to remain with the target. The reporter suggested several automated prevention stops that may have prevented the incursion.

Narrative: Aircraft X was handed off to Approach from the west. I accepted the hand off; but did not have a strip for the aircraft. After some research; I looked in the FDIO and there was no active flight plan for the aircraft. After communication with Aircraft X; I confirmed that he did have routing; and was IFR. I then asked Approach X to confirm they had flight information on him; and what routing they showed him on. They said he was direct ZZZ and then direct ZZZ1. I then asked Aircraft X what his routing was; and he confirmed it was direct ZZZ1. At this time there was still no flight plan information on the aircraft; so I put in a flight plan. In the process of doing this; his call sign dropped off the screen. After getting the flight plan in; and talking to several other aircraft; I completed a scan to confirm where Aircraft X was located. I did not see his tag; and assumed it had dropped off. Next; Approach Y called asking if I was still working Aircraft X; and advised that he was in their airspace. I then called Aircraft X to make sure he was still on frequency. After I made sure he was I called Approach Y to confirm they were seeing him on RADAR; because at this time; I was not. I then switched the aircraft to Approach Y so that they could identify him. I am not sure how the tag of the aircraft dropped off; but this should not be able to happen. I would recommend that there be a stop in place for aircraft being handed off without having any type of flight plan information; while still being on a NAS code. This aircraft should not have been able to be handed off without have a flight plan; and still be IFR. This is what led to the distraction of having to put a new flight plan in; which evidently led to the tag dropping off. As with any scenario; the controller could try to pay more attention to the aircraft. I don't want to say that I was not paying attention; because I was. In fact; I was at a normal workload steadily performing my duties. I do not feel that I neglected my aircraft at all. Another suggestion would be that when an aircraft is entering or departing the airspace on a NAS code; but not tagged up; the tag highlights of flashes to alert the controller that this is not supposed to be there.

Data retrieved from NASA's ASRS site as of July 2013 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	993184
Time
Date	201202
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Aircraft 1
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	Descent
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types

TRACON controller described an airspace incursion event when the data tag on an IFR aircraft failed to remain with the target. The reporter suggested several automated prevention stops that may have prevented the incursion.