Narrative:

I was working the [fix] sector and it was fairly busy with tankers inside the MOA airspace and fighters also; in addition to my normal traffic load. All three tanker flights were getting ready to leave and return to [destination] and they all wanted to depart separately. I pre-planned the departures and searched for the flight plans and had them ready. First aircraft called and I radar identified them and got them going. The second aircraft called for return and I radar identified them and got them going towards the airport. After all these calls I was coordinating with [facility] approach to ensure the aircraft would be able to enter and on what heading/altitudes they'd prefer. After I coordinated aircraft X going in; I hung up to see aircraft Y just short of [fix] at 13500 feet descending to 11000 feet and my conflict alert going off with a military aircraft at 13000 feet. I quickly glanced up to see the DME was 4.44 NM which caused us to lose a safe separation minima. I originally was calling on tactical frequency to have the aircraft X return to the military airspace and issue a traffic call to alert them they were on a collision course. The aircraft never responded because I was calling by the wrong call sign to which I made the error on. After the call on tactical I went on my frequency to alert the aircraft Y of the aircraft X spilling out and his position and DME. Aircraft Y reported aircraft X in sight and did not get any RA's. The military needs to be reminded that we can't be spilling out of the assigned airspace as IFR traffic runs right around the boundary. Additionally; we should've assigned discrete beacon codes to ensure we knew who each aircraft is when multiple are participating. I needed to issue a warning of wake turbulence as the aircraft was a heavy and less than 5 miles from it on the spill out.

Google
 

Original NASA ASRS Text

Title: Two instances of military aircraft exiting the confines of the MOA without clearance. In one case an aircraft came into conflict with an air carrier. In a separate instance an aircraft exited below the base of the MOA and returned to its base without clearance or contacting the ATC Facility.

Narrative: I was working the [fix] sector and it was fairly busy with tankers inside the MOA airspace and fighters also; in addition to my normal traffic load. All three tanker flights were getting ready to leave and return to [destination] and they all wanted to depart separately. I pre-planned the departures and searched for the flight plans and had them ready. First aircraft called and I radar identified them and got them going. The second aircraft called for return and I radar identified them and got them going towards the airport. After all these calls I was coordinating with [facility] approach to ensure the aircraft would be able to enter and on what heading/altitudes they'd prefer. After I coordinated Aircraft X going in; I hung up to see Aircraft Y just short of [fix] at 13500 feet descending to 11000 feet and my conflict alert going off with a military aircraft at 13000 feet. I quickly glanced up to see the DME was 4.44 NM which caused us to lose a safe separation minima. I originally was calling on tactical frequency to have the Aircraft X return to the military airspace and issue a traffic call to alert them they were on a collision course. The aircraft never responded because I was calling by the wrong call sign to which I made the error on. After the call on tactical I went on my frequency to alert the Aircraft Y of the Aircraft X spilling out and his position and DME. Aircraft Y reported Aircraft X in sight and did not get any RA's. The military needs to be reminded that we can't be spilling out of the assigned airspace as IFR traffic runs right around the boundary. Additionally; we should've assigned discrete beacon codes to ensure we knew who each aircraft is when multiple are participating. I needed to issue a warning of wake turbulence as the aircraft was a heavy and less than 5 miles from it on the spill out.

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