Uncoord penetration of airspace. Operational deviation.

Attributes
ACN	126407
Time
Date	198910
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : blv
State Reference	IL
Altitude	msl bound lower : 4000 msl bound upper : 7400
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : bvl tracon : stl
Make Model Name	Small Aircraft, Low Wing, 1 Eng, Retractable Gear
Flight Phase	climbout : intermediate altitude
Route In Use	enroute : direct
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : departure
Qualification	controller : radar
ASRS Report	126407
Person 2
Affiliation	government : military
Function	controller : approach
Qualification	controller : military
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

I was working departure radar north at the end of a rush, moderate traffic, when small aircraft X departed stl downtown, IFR, filed cps direct bib...requested 90. Climb to 60 was approved by departure south. I accepted radar handoff on the small aircraft 20 mi southeast of stl level at 4000. Primary and secondary targets were adequate. I thought I heard him call me and issued him 6000. I diverted my attention to other aircraft, then 1 or 2 mins later, I looked back at small aircraft X. He was gone. I transmitted to small aircraft X: 'radar contact lost'. I then called scott AFB approach control, advised them I lost contact with the small aircraft on XXXX beacon code. They advised me that he was 7 mi northeast of blv, at 4000', in their airspace, and that they had had good primary and secondary radar with small aircraft X all along. ZKC sector 56 had no radar contact with the aircraft. I called scott again later to check on the progress, and they advised me the aircraft was 39 mi east of stl climbing through 7400. I had no radar contact. No evasive action was requested. The occurrence happened because stl radar coverage below 6000, 25-50 mi from stl is poor.

Original NASA ASRS Text

Title: UNCOORD PENETRATION OF AIRSPACE. OPERATIONAL DEVIATION.

Narrative: I WAS WORKING DEP RADAR NORTH AT THE END OF A RUSH, MODERATE TFC, WHEN SMA X DEPARTED STL DOWNTOWN, IFR, FILED CPS DIRECT BIB...REQUESTED 90. CLIMB TO 60 WAS APPROVED BY DEP SOUTH. I ACCEPTED RADAR HANDOFF ON THE SMA 20 MI SE OF STL LEVEL AT 4000. PRIMARY AND SECONDARY TARGETS WERE ADEQUATE. I THOUGHT I HEARD HIM CALL ME AND ISSUED HIM 6000. I DIVERTED MY ATTN TO OTHER ACFT, THEN 1 OR 2 MINS LATER, I LOOKED BACK AT SMA X. HE WAS GONE. I TRANSMITTED TO SMA X: 'RADAR CONTACT LOST'. I THEN CALLED SCOTT AFB APCH CTL, ADVISED THEM I LOST CONTACT WITH THE SMA ON XXXX BEACON CODE. THEY ADVISED ME THAT HE WAS 7 MI NE OF BLV, AT 4000', IN THEIR AIRSPACE, AND THAT THEY HAD HAD GOOD PRIMARY AND SECONDARY RADAR WITH SMA X ALL ALONG. ZKC SECTOR 56 HAD NO RADAR CONTACT WITH THE ACFT. I CALLED SCOTT AGAIN LATER TO CHECK ON THE PROGRESS, AND THEY ADVISED ME THE ACFT WAS 39 MI E OF STL CLIMBING THROUGH 7400. I HAD NO RADAR CONTACT. NO EVASIVE ACTION WAS REQUESTED. THE OCCURRENCE HAPPENED BECAUSE STL RADAR COVERAGE BELOW 6000, 25-50 MI FROM STL IS POOR.

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.