ZTL controller BE20 exit his delegated airspace without coordination with atl approach control.

Attributes
ACN	440803
Time
Date	199906
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : atl.vortac
State Reference	GA
Altitude	msl single value : 12000
Environment
Flight Conditions	IMC
Weather Elements	Ice Rain
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : ztl.artcc tracon : atl.tracon tracon : mke.tracon
Operator	general aviation : personal
Make Model Name	Super King Air 200/Huron
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : atl.tracon
Operator	common carrier : air carrier
Make Model Name	MD-88
Operating Under FAR Part	Part 121
Flight Phase	descent : intermediate altitude
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : flight data
Qualification	controller : radar
Experience	controller radar : 16
ASRS Report	440803
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	airspace violation : entry conflict : airborne less severe non adherence : published procedure non adherence : required legal separation other spatial deviation
Independent Detector	atc equipment : conflict alert other controllera
Resolutory Action	none taken : insufficient time
Consequence	faa : investigated
Miss Distance	horizontal : 27000 vertical : 600
Supplementary
Problem Areas	ATC Facility ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure Operational Deviation
Situations
ATC Facility	communication equipment : atl.tracon

Narrative:

A BE20 was en route from 30GA to dab. The aircraft was initially placed on a 120 degree heading and climbed to 12000 ft. When we gave the aircraft X on course, we thought the routing would not conflict with atl approach, but due to WX, we think he may have deviated into atl approach's airspace. The problem arose when I was unable to contact the arrival sector (logen) of atl approach and give them a pointout. Subsequently they descended a jet (type I believe was an MD88) aircraft Y from 13000 ft to 10000 ft. Conflict alert activated, but they had passed and there was really nothing we could do to stop the situation. After attempting to call atl approach for approximately 1 min, I advised the supervisor of the deviation and possible system error due to atl approach's inability to answer my call. Several mins passed and approach called for a line check and the speaker was turned up so they could begin accepting calls from ZTL.

Original NASA ASRS Text

Title: ZTL CTLR BE20 EXIT HIS DELEGATED AIRSPACE WITHOUT COORD WITH ATL APCH CTL.

Narrative: A BE20 WAS ENRTE FROM 30GA TO DAB. THE ACFT WAS INITIALLY PLACED ON A 120 DEG HDG AND CLBED TO 12000 FT. WHEN WE GAVE THE ACFT X ON COURSE, WE THOUGHT THE ROUTING WOULD NOT CONFLICT WITH ATL APCH, BUT DUE TO WX, WE THINK HE MAY HAVE DEVIATED INTO ATL APCH'S AIRSPACE. THE PROB AROSE WHEN I WAS UNABLE TO CONTACT THE ARR SECTOR (LOGEN) OF ATL APCH AND GIVE THEM A POINTOUT. SUBSEQUENTLY THEY DSNDED A JET (TYPE I BELIEVE WAS AN MD88) ACFT Y FROM 13000 FT TO 10000 FT. CONFLICT ALERT ACTIVATED, BUT THEY HAD PASSED AND THERE WAS REALLY NOTHING WE COULD DO TO STOP THE SIT. AFTER ATTEMPTING TO CALL ATL APCH FOR APPROX 1 MIN, I ADVISED THE SUPVR OF THE DEV AND POSSIBLE SYS ERROR DUE TO ATL APCH'S INABILITY TO ANSWER MY CALL. SEVERAL MINS PASSED AND APCH CALLED FOR A LINE CHK AND THE SPEAKER WAS TURNED UP SO THEY COULD BEGIN ACCEPTING CALLS FROM ZTL.

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.