Narrative:

I was working all radar sectors combined. The approach control was also consolidated to the tower due to low traffic. I accepted a hand off east of little rock airspace on an IFR over flight. The aircraft was a BE36 bonanza. The aircraft originated in dts and was enroute to cbf at 8000 ft. After accepting the hand off; I entered the aircraft's first fix outside of lit airspace which was sgf into the scratch pad. I spoke to a couple of other airplanes and then the BE36 checked in with me. I gave him the little rock altimeter. A few minutes later; and before the BE36 entered lit airspace the radar data disappeared. I did not see the data disappear. Approximately 5 minutes later the radar west position called to commence briefing for bringing the approach control to the TRACON. I gave the briefing and issued all traffic that was tagged on my scope. I still had no idea that BE36 data had disappeared; and failed to remember him in the position relief briefing. Approximately 30 minutes after the session; a flm came to me asking if I remembered the BE36; and said that memphis center was looking for him; and he was missing. The controller that took the position from me was able to contact the BE36 on frequency and switch him to center. The aircraft had entered center airspace without being handed off. Do not combine all radar positions to the tower. The monitor used in the tower is significantly smaller than the radar scopes in the TRACON. Also; there are many more distractions in the tower; than in the TRACON. Had I been working on a larger scope I might have noticed the tag disappear and been able to re-tag the aircraft to accomplish the hand off. Additionally; investigate if the radar data was terminated by another keyboard within the facility by mistake. I have never seen radar data disappear for no reason. The data could have been dropped by someone in the facility by mistake.

Google
 

Original NASA ASRS Text

Title: LIT Tower Controller described airspace entry event when failing to note an aircraft data block disappearing and failing to include the traffic during a relief briefing; listing position combining procedure and equipment as causal factors.

Narrative: I was working all RADAR sectors combined. The Approach Control was also consolidated to the Tower due to low traffic. I accepted a hand off east of Little Rock airspace on an IFR over flight. The aircraft was a BE36 Bonanza. The aircraft originated in DTS and was enroute to CBF at 8000 FT. After accepting the hand off; I entered the aircraft's first fix outside of LIT airspace which was SGF into the scratch pad. I spoke to a couple of other airplanes and then the BE36 checked in with me. I gave him the Little Rock altimeter. A few minutes later; and before the BE36 entered LIT airspace the RADAR data disappeared. I did not see the data disappear. Approximately 5 minutes later the RADAR west position called to commence briefing for bringing the Approach Control to the TRACON. I gave the briefing and issued all traffic that was tagged on my scope. I still had no idea that BE36 data had disappeared; and failed to remember him in the position relief briefing. Approximately 30 minutes after the session; a FLM came to me asking if I remembered the BE36; and said that Memphis Center was looking for him; and he was missing. The Controller that took the position from me was able to contact the BE36 on frequency and switch him to Center. The aircraft had entered Center airspace without being handed off. Do not combine all RADAR positions to the Tower. The monitor used in the Tower is significantly smaller than the RADAR scopes in the TRACON. Also; there are many more distractions in the Tower; than in the TRACON. Had I been working on a larger scope I might have noticed the tag disappear and been able to re-tag the aircraft to accomplish the hand off. Additionally; investigate if the RADAR data was terminated by another keyboard within the facility by mistake. I have never seen RADAR data disappear for no reason. The data could have been dropped by someone in the facility by mistake.

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