Narrative:

Fgt X called waycross radar controller with low fuel requesting FL240 and direct moody AFB. One flight plan was already active because fgt X was a flight of 4 and the 2 aircraft apparently split off from the others. The fgt X aircraft were in another sector and pointout was made to that sector (brunswick low). The brunswick low controller stated that he had no traffic for fgt X and the aircraft was released to the waycross low radar controller. The waycross low controller cleared fgt X direct moody and cleared the fgt X flight to climb to FL230 where near jessup, GA and at FL230 fgt X early hit an air carrier medium large transport Y. The air carrier medium large transport Y call sign was not noted, because I was sure a full investigation would soon follow. However, I had squawked fgt X mayday on code 7700 when he declared a low fuel emergency as I was in the process of a pointout to the brunswick low controller. Apparently no systems error was noted due to the emergency condition of fgt X. I was working radar at waycross low and had only a newly certified non radar controller as an assistant and 2 supervisors on looking. At the same time the emergency was in progress, I got one aircraft on my frequency at FL180 with no handoff--also an unknown aircraft was apparently returning from east coast warning areas to moody at FL180. I had to turn and descend 1 aircraft to avoid the unknown aircraft at FL180. This near midair collision was spotted only by C/a on fgt X and medium large transport Y.

Related reports:

Google
 

Original NASA ASRS Text

Title: FGT FLT DECLARED EMERGENCY AND WAS CLIMBED TO ALT IN ANOTHER CTLR'S SECTOR, AFTER COORD, BUT FGT HAD NMAC WITH ACR-MLG DUE TO POOR COORD.

Narrative: FGT X CALLED WAYCROSS RADAR CTLR WITH LOW FUEL REQUESTING FL240 AND DIRECT MOODY AFB. ONE FLT PLAN WAS ALREADY ACTIVE BECAUSE FGT X WAS A FLT OF 4 AND THE 2 ACFT APPARENTLY SPLIT OFF FROM THE OTHERS. THE FGT X ACFT WERE IN ANOTHER SECTOR AND POINTOUT WAS MADE TO THAT SECTOR (BRUNSWICK LOW). THE BRUNSWICK LOW CTLR STATED THAT HE HAD NO TFC FOR FGT X AND THE ACFT WAS RELEASED TO THE WAYCROSS LOW RADAR CTLR. THE WAYCROSS LOW CTLR CLRED FGT X DIRECT MOODY AND CLRED THE FGT X FLT TO CLB TO FL230 WHERE NEAR JESSUP, GA AND AT FL230 FGT X EARLY HIT AN ACR MLG Y. THE ACR MLG Y CALL SIGN WAS NOT NOTED, BECAUSE I WAS SURE A FULL INVESTIGATION WOULD SOON FOLLOW. HOWEVER, I HAD SQUAWKED FGT X MAYDAY ON CODE 7700 WHEN HE DECLARED A LOW FUEL EMER AS I WAS IN THE PROCESS OF A POINTOUT TO THE BRUNSWICK LOW CTLR. APPARENTLY NO SYSTEMS ERROR WAS NOTED DUE TO THE EMER CONDITION OF FGT X. I WAS WORKING RADAR AT WAYCROSS LOW AND HAD ONLY A NEWLY CERTIFIED NON RADAR CTLR AS AN ASSISTANT AND 2 SUPVRS ON LOOKING. AT THE SAME TIME THE EMER WAS IN PROGRESS, I GOT ONE ACFT ON MY FREQ AT FL180 WITH NO HDOF--ALSO AN UNKNOWN ACFT WAS APPARENTLY RETURNING FROM E COAST WARNING AREAS TO MOODY AT FL180. I HAD TO TURN AND DSND 1 ACFT TO AVOID THE UNKNOWN ACFT AT FL180. THIS NMAC WAS SPOTTED ONLY BY C/A ON FGT X AND MLG Y.

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.