Narrative:

While working east departure/south a military aircraft called with a broken, unreadable transmission. About 20 seconds later, military aircraft calls again. I asked if that was aircraft #1 calling ind approach. They advised that they were VFR at 9500 ft northbound 20 mi east, 25 mi north of R3401. I asked what altitude they were leaving and they said level at 9500 ft VFR. I issued a squawk code of xyza and told them to maintain VFR. I immediately called ZID, mie sector, for aircraft #1 was getting close to their airspace. I advised mie that just tagging up at the homar intersection on a code of xyza, was a flight of 4 A10's still VFR at 9500 ft. Mie asked if I had departed him. I said no and told arrival data to 'dm.' aircraft #1 tagged up and I started the flash to ZID. The controller asked again if had issued the clearance yet and I said no. He told me to issue the clearance and maintain 10000 ft. Before issuing the clearance, day approach called to coordinate for the 3RD time on a non-ARTS tagged IFR aircraft. I told day to keep him coming. I then radar idented and climbed aircraft #2, who called off of ind. I then went back to aircraft #1 and issued the IFR clearance. Aircraft X said the clearance had been blocked. I reissued the clearance, told him to maintain 10000 ft and contact ZID on XXXX. About 2 mins later, I heard the conflict alert sound. At the pends intersection (in indy airspace), I saw aircraft Z at 10600 ft and aircraft Z at 10000 ft. Ind arrival controller had descended aircraft Z to 6000 ft, as is allowed by an LOA between ind approach and ZID. Prior to entering ZID airspace, aircraft X flight had clipped about 1 1/2 mi of ind arrival airspace. And because I had not pointed out the aircraft #1 flight to the arrival controller, he did not see the crossing traffic and descended aircraft #2. Furthermore, I have a habit of dropping tracks that leave my airspace, and I probably dropped the track of the aircraft X flight. Some issues that contributed to my workload were, prior to aircraft X calling on, day approach calls with a manual handoff. I advised day to keep him coming. This was the 1ST thing in the back of my mind to keep an eye on. The next thing was aircraft xx called looking for an IFR clearance off of hfy. So this was also in my mind, find a clearance for him. ZID, abb sector called for a pointout. And while trying to respond to the aircraft X flight, day called 2 more times to coordinate a non-ARTS tagged aircraft. Once I was able to issue the clearance to aircraft X, it had been blocked by aircraft yy calling to get his IFR off of ZL8. All the while in the TRACON, the volume level was increasing with a shift change. Also the departure controller next to me, was becoming very busy and his volume level increased also.

Related reports:

Google
 

Original NASA ASRS Text

Title: IND DEP CTLR FAILED TO COORDINATE A FLT OF 4 A10 MIL ACFT WITH THE IND ARR SECTOR CAUSING A LOSS OF SEPARATION WITH AN ACR JET DSNDING INTO IND ARPT.

Narrative: WHILE WORKING E DEP/S A MIL ACFT CALLED WITH A BROKEN, UNREADABLE XMISSION. ABOUT 20 SECONDS LATER, MIL ACFT CALLS AGAIN. I ASKED IF THAT WAS ACFT #1 CALLING IND APCH. THEY ADVISED THAT THEY WERE VFR AT 9500 FT NBOUND 20 MI E, 25 MI N OF R3401. I ASKED WHAT ALT THEY WERE LEAVING AND THEY SAID LEVEL AT 9500 FT VFR. I ISSUED A SQUAWK CODE OF XYZA AND TOLD THEM TO MAINTAIN VFR. I IMMEDIATELY CALLED ZID, MIE SECTOR, FOR ACFT #1 WAS GETTING CLOSE TO THEIR AIRSPACE. I ADVISED MIE THAT JUST TAGGING UP AT THE HOMAR INTXN ON A CODE OF XYZA, WAS A FLT OF 4 A10'S STILL VFR AT 9500 FT. MIE ASKED IF I HAD DEPARTED HIM. I SAID NO AND TOLD ARR DATA TO 'DM.' ACFT #1 TAGGED UP AND I STARTED THE FLASH TO ZID. THE CTLR ASKED AGAIN IF HAD ISSUED THE CLRNC YET AND I SAID NO. HE TOLD ME TO ISSUE THE CLRNC AND MAINTAIN 10000 FT. BEFORE ISSUING THE CLRNC, DAY APCH CALLED TO COORDINATE FOR THE 3RD TIME ON A NON-ARTS TAGGED IFR ACFT. I TOLD DAY TO KEEP HIM COMING. I THEN RADAR IDENTED AND CLBED ACFT #2, WHO CALLED OFF OF IND. I THEN WENT BACK TO ACFT #1 AND ISSUED THE IFR CLRNC. ACFT X SAID THE CLRNC HAD BEEN BLOCKED. I REISSUED THE CLRNC, TOLD HIM TO MAINTAIN 10000 FT AND CONTACT ZID ON XXXX. ABOUT 2 MINS LATER, I HEARD THE CONFLICT ALERT SOUND. AT THE PENDS INTXN (IN INDY AIRSPACE), I SAW ACFT Z AT 10600 FT AND ACFT Z AT 10000 FT. IND ARR CTLR HAD DSNDED ACFT Z TO 6000 FT, AS IS ALLOWED BY AN LOA BTWN IND APCH AND ZID. PRIOR TO ENTERING ZID AIRSPACE, ACFT X FLT HAD CLIPPED ABOUT 1 1/2 MI OF IND ARR AIRSPACE. AND BECAUSE I HAD NOT POINTED OUT THE ACFT #1 FLT TO THE ARR CTLR, HE DID NOT SEE THE XING TFC AND DSNDED ACFT #2. FURTHERMORE, I HAVE A HABIT OF DROPPING TRACKS THAT LEAVE MY AIRSPACE, AND I PROBABLY DROPPED THE TRACK OF THE ACFT X FLT. SOME ISSUES THAT CONTRIBUTED TO MY WORKLOAD WERE, PRIOR TO ACFT X CALLING ON, DAY APCH CALLS WITH A MANUAL HDOF. I ADVISED DAY TO KEEP HIM COMING. THIS WAS THE 1ST THING IN THE BACK OF MY MIND TO KEEP AN EYE ON. THE NEXT THING WAS ACFT XX CALLED LOOKING FOR AN IFR CLRNC OFF OF HFY. SO THIS WAS ALSO IN MY MIND, FIND A CLRNC FOR HIM. ZID, ABB SECTOR CALLED FOR A POINTOUT. AND WHILE TRYING TO RESPOND TO THE ACFT X FLT, DAY CALLED 2 MORE TIMES TO COORDINATE A NON-ARTS TAGGED ACFT. ONCE I WAS ABLE TO ISSUE THE CLRNC TO ACFT X, IT HAD BEEN BLOCKED BY ACFT YY CALLING TO GET HIS IFR OFF OF ZL8. ALL THE WHILE IN THE TRACON, THE VOLUME LEVEL WAS INCREASING WITH A SHIFT CHANGE. ALSO THE DEP CTLR NEXT TO ME, WAS BECOMING VERY BUSY AND HIS VOLUME LEVEL INCREASED ALSO.

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