Automated handoff from TRACON to ARTCC goes to wrong ARTCC.

Attributes
ACN	253869
Time
Date	199310
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : dec
State Reference	IL
Altitude	msl bound lower : 10000 msl bound upper : 10000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zau artcc : zkc tracon : cmi
Operator	general aviation : corporate
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	climbout : initial
Route In Use	departure other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : departure
Qualification	controller : radar
ASRS Report	253869
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : unable
Consequence	Other
Supplementary
Primary Problem	Navigational Facility
Air Traffic Incident	other
Situations
Navigational Aid	Unspecified

Narrative:

Cga X, an light transport, departed decatur, il (dec), filed first fix of fwa. After departure I coordinated climbing to FL230 with ZKC sector 58 (which overlays dec) and ZAU pnt sector for pointouts and initiated a handoff to ZAU dnu sector. Both sector 58 and pnt sectors approved the pointouts and I saw the automated handoff accepted. The handoff was initiated by the ARTS keyboard entry of '1' which is supposed to send the handoff to dnu sector. After the handoff was shown as accepted, I shipped cga X to dnu sector frequency. Just after I shipped cga X, I received a call from ZKC, sector 58 and was informed that the handoff actually went to ZKC sector 42. ZKC sector 42 is near kansas city. This is a recurring problem with automation which seems to not get the proper attention. This could lead to a loss of separation. Callback conversation with reporter revealed the following information: reporter states that this occurred approximately 15 mi northeast of dec at 10000 ft. This has been an ongoing problem for at least several yrs with no cure in sight. Reporter thinks it happens about once a week. No deals have occurred. Facility management aware of problem, but no big effort to rectify it. Facility troops have been briefed on the possibility of a missed directed handoff. Seems to only happen with dec departures. Cmi airspace goes up to 10000 ft. No ucr filed.

Original NASA ASRS Text

Title: AUTOMATED HDOF FROM TRACON TO ARTCC GOES TO WRONG ARTCC.

Narrative: CGA X, AN LTT, DEPARTED DECATUR, IL (DEC), FILED FIRST FIX OF FWA. AFTER DEP I COORDINATED CLBING TO FL230 WITH ZKC SECTOR 58 (WHICH OVERLAYS DEC) AND ZAU PNT SECTOR FOR POINTOUTS AND INITIATED A HDOF TO ZAU DNU SECTOR. BOTH SECTOR 58 AND PNT SECTORS APPROVED THE POINTOUTS AND I SAW THE AUTOMATED HDOF ACCEPTED. THE HDOF WAS INITIATED BY THE ARTS KEYBOARD ENTRY OF '1' WHICH IS SUPPOSED TO SEND THE HDOF TO DNU SECTOR. AFTER THE HDOF WAS SHOWN AS ACCEPTED, I SHIPPED CGA X TO DNU SECTOR FREQ. JUST AFTER I SHIPPED CGA X, I RECEIVED A CALL FROM ZKC, SECTOR 58 AND WAS INFORMED THAT THE HDOF ACTUALLY WENT TO ZKC SECTOR 42. ZKC SECTOR 42 IS NEAR KANSAS CITY. THIS IS A RECURRING PROB WITH AUTOMATION WHICH SEEMS TO NOT GET THE PROPER ATTN. THIS COULD LEAD TO A LOSS OF SEPARATION. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES THAT THIS OCCURRED APPROX 15 MI NE OF DEC AT 10000 FT. THIS HAS BEEN AN ONGOING PROB FOR AT LEAST SEVERAL YRS WITH NO CURE IN SIGHT. RPTR THINKS IT HAPPENS ABOUT ONCE A WK. NO DEALS HAVE OCCURRED. FACILITY MGMNT AWARE OF PROB, BUT NO BIG EFFORT TO RECTIFY IT. FACILITY TROOPS HAVE BEEN BRIEFED ON THE POSSIBILITY OF A MISSED DIRECTED HDOF. SEEMS TO ONLY HAPPEN WITH DEC DEPS. CMI AIRSPACE GOES UP TO 10000 FT. NO UCR FILED.

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.