A80 controller described a confused and uncoordinated departure operation possibly resulting in an a...

Narrative:

Working north departure and aircraft called off the south side that appeared to be on a 250 track but had summt in the data block. There was a wall of aircraft off the north side of west and north gates. I could not figure out what the tower was doing because the aircraft on the 250 track had to go out the north gates. I called tower control. I am advised that the 250 track does not have his summt clearance. Had an aircraft say he may have to return to atl because of equipment issues. I turn the 250 track north and top other departures. An E1 dawgs checks in with no heads up from the tower. He is approximately 2 miles behind the B757 but separated by altitude. I think I can climb the dawgs aircraft because he is at the pivot point where he turns east. I notice he is not turning east. I ask if he is on the dawgs. He says no he is on the summt. The aircraft with the equipment issue says he's ok and is ready to continue on the summt departure. I stop departures at some point. I believe one of the aircraft that I stopped below the 250 track may have entered satellite airspace. Tower rolled another aircraft even though I have stopped departures. South departure is trying to help and coordinate. The supervisor is trying to help and coordinate. I call ZTL and coordinate the end result of speed restrictions to the 4 or 5 summt. It was a cluster; I controller in charge the departure wall on a regular basis. It is quite common for the tower to send 1 aircraft off the north and 1 off the south heading for the same gates that are a tie. But what happened last night was inexcusable in my opinion. It put the aircraft and me; in a bad position and caused numerous delays. I was told later that the tower screwed up the 250 track aircraft but the aircraft on the dawgs (summt) was an automation issue. The tower needs a better way of coordinating aircraft that are departing the wrong runway.

Original NASA ASRS Text

Title: A80 Controller described a confused and uncoordinated departure operation possibly resulting in an airspace infraction; the reporter suggesting improved coordination procedures by the Tower regarding non standard departures.

Narrative: Working North Departure and aircraft called off the south side that appeared to be on a 250 track but had SUMMT in the Data Block. There was a wall of aircraft off the north side of west and north gates. I could not figure out what the Tower was doing because the aircraft on the 250 track had to go out the north gates. I called Tower Control. I am advised that the 250 track does not have his SUMMT clearance. Had an aircraft say he may have to return to ATL because of equipment issues. I turn the 250 track north and top other departures. An E1 DAWGS checks in with no heads up from the Tower. He is approximately 2 miles behind the B757 but separated by altitude. I think I can climb the DAWGS aircraft because he is at the pivot point where he turns east. I notice he is not turning east. I ask if he is on the DAWGS. He says no he is on the SUMMT. The aircraft with the equipment issue says he's OK and is ready to continue on the SUMMT departure. I stop departures at some point. I believe one of the aircraft that I stopped below the 250 track may have entered satellite airspace. Tower rolled another aircraft even though I have stopped departures. South departure is trying to help and coordinate. The supervisor is trying to help and coordinate. I call ZTL and coordinate the end result of speed restrictions to the 4 or 5 SUMMT. It was a cluster; I CIC the departure wall on a regular basis. It is quite common for the Tower to send 1 aircraft off the north and 1 off the south heading for the same gates that are a tie. But what happened last night was inexcusable in my opinion. It put the aircraft and me; in a bad position and caused numerous delays. I was told later that the tower screwed up the 250 track aircraft but the aircraft on the DAWGS (SUMMT) was an automation issue. The Tower needs a better way of coordinating aircraft that are departing the wrong runway.

Data retrieved from NASA's ASRS site as of July 2013 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.

Attributes
ACN	1013493
Time
Date	201206
Local Time Of Day	0001-0600
Place
Locale Reference	A80.TRACON
State Reference	GA
Aircraft 1
Make Model Name	B757 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

A80 controller described a confused and uncoordinated departure operation possibly resulting in an airspace infraction; the reporter suggesting improved coordination procedures by the tower regarding non standard departures.