Operational deviation. Uncoordinated penetration of airspace.

Attributes
ACN	198632
Time
Date	199201
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : rod
State Reference	OH
Altitude	msl bound lower : 7000 msl bound upper : 7000
Environment
Flight Conditions	Marginal
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zid tracon : tol
Make Model Name	Small Aircraft, Low Wing, 1 Eng, Retractable Gear
Flight Phase	cruise other
Route In Use	enroute airway : tol enroute airway : zid
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller non radar : 3 controller radar : 4
ASRS Report	198632
Person 2
Affiliation	government : faa
Function	controller : flight data
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

Aircraft X was northbound on V275 at 7000 ft. An aircraft with a similar call sign was being worked in zanesville, oh, area by myself. The radar associated controller (D side) removed the strip (and flight plan) on aircraft X instead of aircraft Y at zanesville. The disappearance of X's data block was not noticed and as a result, X violated toledo approach airspace. The aircraft was 20-25 mi in toledo's airspace before the controller noticed the limited data block. The aircraft was in indianapolis center's airspace (rosewood sector) for approximately 15 mi undetected before entering toledo's airspace. The data block on aircraft X was dropped while still in dayton approach airspace (south of rosewood airspace) and I was relieved before aircraft X entered our airspace. However, initial radio contact with the aircraft was made before I was relieved.

Original NASA ASRS Text

Title: OPDEV. UNCOORDINATED PENETRATION OF AIRSPACE.

Narrative: ACFT X WAS NBOUND ON V275 AT 7000 FT. AN ACFT WITH A SIMILAR CALL SIGN WAS BEING WORKED IN ZANESVILLE, OH, AREA BY MYSELF. THE RADAR ASSOCIATED CTLR (D SIDE) REMOVED THE STRIP (AND FLT PLAN) ON ACFT X INSTEAD OF ACFT Y AT ZANESVILLE. THE DISAPPEARANCE OF X'S DATA BLOCK WAS NOT NOTICED AND AS A RESULT, X VIOLATED TOLEDO APCH AIRSPACE. THE ACFT WAS 20-25 MI IN TOLEDO'S AIRSPACE BEFORE THE CTLR NOTICED THE LIMITED DATA BLOCK. THE ACFT WAS IN INDIANAPOLIS CENTER'S AIRSPACE (ROSEWOOD SECTOR) FOR APPROX 15 MI UNDETECTED BEFORE ENTERING TOLEDO'S AIRSPACE. THE DATA BLOCK ON ACFT X WAS DROPPED WHILE STILL IN DAYTON APCH AIRSPACE (S OF ROSEWOOD AIRSPACE) AND I WAS RELIEVED BEFORE ACFT X ENTERED OUR AIRSPACE. HOWEVER, INITIAL RADIO CONTACT WITH THE ACFT WAS MADE BEFORE I WAS RELIEVED.

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.