Narrative:

On a schedule flight from atl to eglin AFB, in VFR conditions, we were cleared from 11000 to 8000'. While passing through 9500' we were asked to go up to 10000'. At the time we did that, advised of traffic at 9000', 10 O'clock position. We saw traffic on a climb, 2 fgt's coming our way. One made a right turn, the other decided to keep going toward us, made a pass over us at the last minute. I acknowledged to eglin approach of how close he was. Eglin approach then apologized for mishap and told us they had all corridors full, no place to put us. We were talking to 119.3 the time XA45Z. Callback conversation with reporter revealed the following: reporter called the facility on landing. The facility supervisor advised in vague terms that they would be counseled concerning this incident. They are unknown to the reporter and he is not now sure whether this was an operational error or pilot deviation. Reporter thought the fgt's were climbing VFR but wasn't sure. The on the air apology by the controller would seem to indicate that controller error was involved, but when giving the traffic advisory, the controller stated that the traffic was climbing to 9000'. Neither the reporter nor this analyst can tell what kind of incident this was. Reporter did state that the fgt was so close that there was no time for evasive action. The speed of the fgt was very high. All of the passenger on this flight saw the fgt's and were very disturbed. Finally, the reporter stated that when the climb corridors at eglin are in use by the fgt's, air carrier's are normally cleared so they do not enter these corridors. In this way, the controller apparently erred.

Related reports:

Google
 

Original NASA ASRS Text

Title: LESS THAN STANDARD SEPARATION BETWEEN INBOUND ACR-LTT AND CLIMBING FGT.

Narrative: ON A SCHEDULE FLT FROM ATL TO EGLIN AFB, IN VFR CONDITIONS, WE WERE CLRED FROM 11000 TO 8000'. WHILE PASSING THROUGH 9500' WE WERE ASKED TO GO UP TO 10000'. AT THE TIME WE DID THAT, ADVISED OF TFC AT 9000', 10 O'CLOCK POS. WE SAW TFC ON A CLB, 2 FGT'S COMING OUR WAY. ONE MADE A RIGHT TURN, THE OTHER DECIDED TO KEEP GOING TOWARD US, MADE A PASS OVER US AT THE LAST MINUTE. I ACKNOWLEDGED TO EGLIN APCH OF HOW CLOSE HE WAS. EGLIN APCH THEN APOLOGIZED FOR MISHAP AND TOLD US THEY HAD ALL CORRIDORS FULL, NO PLACE TO PUT US. WE WERE TALKING TO 119.3 THE TIME XA45Z. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: RPTR CALLED THE FAC ON LNDG. THE FAC SUPVR ADVISED IN VAGUE TERMS THAT THEY WOULD BE COUNSELED CONCERNING THIS INCIDENT. THEY ARE UNKNOWN TO THE RPTR AND HE IS NOT NOW SURE WHETHER THIS WAS AN OPERROR OR PLTDEV. RPTR THOUGHT THE FGT'S WERE CLBING VFR BUT WASN'T SURE. THE ON THE AIR APOLOGY BY THE CTLR WOULD SEEM TO INDICATE THAT CTLR ERROR WAS INVOLVED, BUT WHEN GIVING THE TFC ADVISORY, THE CTLR STATED THAT THE TFC WAS CLBING TO 9000'. NEITHER THE RPTR NOR THIS ANALYST CAN TELL WHAT KIND OF INCIDENT THIS WAS. RPTR DID STATE THAT THE FGT WAS SO CLOSE THAT THERE WAS NO TIME FOR EVASIVE ACTION. THE SPD OF THE FGT WAS VERY HIGH. ALL OF THE PAX ON THIS FLT SAW THE FGT'S AND WERE VERY DISTURBED. FINALLY, THE RPTR STATED THAT WHEN THE CLB CORRIDORS AT EGLIN ARE IN USE BY THE FGT'S, ACR'S ARE NORMALLY CLRED SO THEY DO NOT ENTER THESE CORRIDORS. IN THIS WAY, THE CTLR APPARENTLY ERRED.

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.