ZTL controller resolves incorrect frequency change, alerting the xferring controller of his error.

Attributes
ACN	532446
Time
Date	200112
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : jau.ndb
State Reference	TN
Altitude	msl single value : 21000
Environment
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : ztl.artcc artcc : zid.artcc
Operator	common carrier : air carrier
Make Model Name	Brasilia EMB-120 All Series
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar controller : supervisor
Qualification	controller : radar
Experience	controller limited radar : 19 controller radar : 19 controller supervisory : 0.25 controller time certified in position1 : 19.08
ASRS Report	532446
Person 2
Affiliation	government : faa
Function	controller : radar
Events
Anomaly	non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Consequence	faa : investigated
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure

Narrative:

Aircraft X was ssebound from lex to atl via direct vxv MACEY2, and level at FL210. I was working at ZTL sector 41 (sfc -- FL230, in the vicinity of csv, crossville, tn). At approximately XA50Z, aircraft X called on my frequency at FL210. At this time, I had no prior knowledge of aircraft X (no flight plan on the sector, no handoff, no pointout). When the aircraft called, I answered his call and typed in the call sign into the computer to try and locate the aircraft. When I located the aircraft, it was 5 or 6 mi from the extreme northeastern corner of my airspace, and would enter my airspace in about 1 min. I was able to determine that the ZID controller had handed off the aircraft to an adjacent sector (ZTL-41) and I xferred communications to that sector. I then called the ZID controller to complete coordination, so that the aircraft would not enter my airspace without coordination, causing a deviation by the ZID controller. This error, or near error, was caused by a lack of attention by the ZID's controller who apparently thought the aircraft had been handed off to my sector (ZTL-41) but was actually handed off to ZTL-45.

Original NASA ASRS Text

Title: ZTL CTLR RESOLVES INCORRECT FREQ CHANGE, ALERTING THE XFERRING CTLR OF HIS ERROR.

Narrative: ACFT X WAS SSEBOUND FROM LEX TO ATL VIA DIRECT VXV MACEY2, AND LEVEL AT FL210. I WAS WORKING AT ZTL SECTOR 41 (SFC -- FL230, IN THE VICINITY OF CSV, CROSSVILLE, TN). AT APPROX XA50Z, ACFT X CALLED ON MY FREQ AT FL210. AT THIS TIME, I HAD NO PRIOR KNOWLEDGE OF ACFT X (NO FLT PLAN ON THE SECTOR, NO HDOF, NO POINTOUT). WHEN THE ACFT CALLED, I ANSWERED HIS CALL AND TYPED IN THE CALL SIGN INTO THE COMPUTER TO TRY AND LOCATE THE ACFT. WHEN I LOCATED THE ACFT, IT WAS 5 OR 6 MI FROM THE EXTREME NORTHEASTERN CORNER OF MY AIRSPACE, AND WOULD ENTER MY AIRSPACE IN ABOUT 1 MIN. I WAS ABLE TO DETERMINE THAT THE ZID CTLR HAD HANDED OFF THE ACFT TO AN ADJACENT SECTOR (ZTL-41) AND I XFERRED COMS TO THAT SECTOR. I THEN CALLED THE ZID CTLR TO COMPLETE COORD, SO THAT THE ACFT WOULD NOT ENTER MY AIRSPACE WITHOUT COORD, CAUSING A DEV BY THE ZID CTLR. THIS ERROR, OR NEAR ERROR, WAS CAUSED BY A LACK OF ATTN BY THE ZID'S CTLR WHO APPARENTLY THOUGHT THE ACFT HAD BEEN HANDED OFF TO MY SECTOR (ZTL-41) BUT WAS ACTUALLY HANDED OFF TO ZTL-45.

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.