Narrative:

It's been 4 days since an rdo; I worked; [then took] sick leave [the following two days]; back at it today. As I was relieving the previous controller at kokomo (okk) I noticed the conflict alert activating. The MOA was in use; three military aircraft were leaving. Aircraft X remained; one was flashing conflict alert with the overflight; aircraft Y and the mode-C for aircraft X showed FL184. The previous controller broadcast on tactical for aircraft X flight to check altitude; then issued traffic for the overflight. As I assumed the position; aircraft X again showed 300 ft high; I broadcast on tactical and guard; no response; and issued traffic to aircraft Y. Aircraft Y did not report aircraft X in sight. Aircraft X later showed 300 ft high; I broadcast on guard and tactical; no response; but each time aircraft X descended back into the MOA (up to but not including FL180). Later I was descending two mdw arrivals; immediately east of the military airspace. The first; a prop; was descending through 14;000 for 11;000 and the second was a commercial aircraft at 17;000. Aircraft X then requested an IFR clearance after he had departed the airspace; without prior communication. I told him an IFR clearance was unavailable due to traffic at 17;000 and FL190; no altimeters for FL180. I issued the traffic to the commercial aircraft. Aircraft X repeated his request for an IFR clearance; I reiterated none was available; and then transferred communication to olk.it seems aircraft X; was unfamiliar with hilltop procedures; which require them to monitor our tactical frequency in event of a spill out. Aircraft X's mode-C showed him high 3 times; we never received a response any instance we tried to descend him back into the MOA. All participants in hilltop must monitor our tactical. Aircraft X did not respond any instance where I transmitted on 243.0. We need better compliance from the participants.

Related reports:

Google
 

Original NASA ASRS Text

Title: Enroute Controller reports military aircraft in MOA spilling out and causing issues with overflight traffic.

Narrative: It's been 4 days since an RDO; I worked; [then took] sick leave [the following two days]; back at it today. As I was relieving the previous Controller at Kokomo (OKK) I noticed the conflict alert activating. The MOA was in use; three military aircraft were leaving. Aircraft X remained; one was flashing conflict alert with the overflight; Aircraft Y and the Mode-C for Aircraft X showed FL184. The previous Controller broadcast on tactical for Aircraft X flight to check altitude; then issued traffic for the overflight. As I assumed the position; Aircraft X again showed 300 FT high; I broadcast on tactical and guard; no response; and issued traffic to Aircraft Y. Aircraft Y did not report Aircraft X in sight. Aircraft X later showed 300 FT high; I broadcast on guard and tactical; no response; but each time Aircraft X descended back into the MOA (up to but not including FL180). Later I was descending two MDW arrivals; immediately east of the military airspace. The first; a prop; was descending through 14;000 for 11;000 and the second was a Commercial aircraft at 17;000. Aircraft X then requested an IFR clearance after he had departed the airspace; without prior communication. I told him an IFR clearance was unavailable due to traffic at 17;000 and FL190; no altimeters for FL180. I issued the traffic to the Commercial aircraft. Aircraft X repeated his request for an IFR clearance; I reiterated none was available; and then transferred communication to OLK.It seems Aircraft X; was unfamiliar with Hilltop Procedures; which require them to monitor our tactical frequency in event of a spill out. Aircraft X's Mode-C showed him high 3 times; we never received a response any instance we tried to descend him back into the MOA. All participants in Hilltop must monitor our tactical. Aircraft X did not respond any instance where I transmitted on 243.0. We need better compliance from the participants.

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.