Narrative:

Flight of 4 military fighters requested non-standard formation not to exceed 6 NM leaving a MOA. When apreq'd with an adjacent sector; their hesitation motivated me to assist them by breaking the flight up into 2- flights of two. During the breakup; the remaining two flights of 2 departed the same MOA about 20 NM in trail of the ones I was breaking up. While trying to update and put in new flight plans on break-up; one aircraft declared an emergency. I tried to radar identify the emergency aircraft (squawk 7700) but was thinking it was the fourth aircraft of the flight I was breaking up; based on the call sign. But then; another aircraft announced that he should have called himself 'flight XXX' not flight YYY. Now realizing that it was one of the VFR aircraft; I continued to try to identify the emergency aircraft location; nature; (low fuel); etc.; but could not see the plane. I thought I heard the emergency aircraft report leaving a flight level during this time. I asked the flm for help. Realizing I was not getting the proper coordination or flight plan information done in a timely manner. When I finally saw the emergency code; it was inside the adjacent lateral airspace; but I didn't see a mode C; so I issued traffic on a departing MD80 climbing through 150 or 160. This whole time; the first two flights of two entered the adjacent airspace not at LOA altitudes; appropriate flight plans (VFR/IFR or #/type status); or hand off (2nd flight). Recommendation; don't offer to break up flights to help fellow sectors unless I have a d-side to do the paperwork/coordination.

Related reports:

Google
 

Original NASA ASRS Text

Title: Enroute Controller described a multiple military aircraft flight break up event that eventually resulted in an airspace incursion; the reporter noting any future similar break up attempts should mandate a D-Side Controller.

Narrative: Flight of 4 military fighters requested non-standard formation not to exceed 6 NM leaving a MOA. When APREQ'd with an adjacent sector; their hesitation motivated me to assist them by breaking the flight up into 2- flights of two. During the breakup; the remaining two flights of 2 departed the same MOA about 20 NM in trail of the ones I was breaking up. While trying to update and put in new flight plans on break-up; one aircraft declared an emergency. I tried to RADAR identify the emergency aircraft (squawk 7700) but was thinking it was the fourth aircraft of the flight I was breaking up; based on the call sign. But then; another aircraft announced that he should have called himself 'Flight XXX' not Flight YYY. Now realizing that it was one of the VFR aircraft; I continued to try to identify the emergency aircraft location; nature; (low fuel); etc.; but could not see the plane. I thought I heard the emergency aircraft report leaving a flight level during this time. I asked the FLM for help. Realizing I was not getting the proper coordination or flight plan information done in a timely manner. When I finally saw the emergency code; it was inside the adjacent lateral airspace; but I didn't see a Mode C; so I issued traffic on a departing MD80 climbing through 150 or 160. This whole time; the first two flights of two entered the adjacent airspace not at LOA altitudes; appropriate flight plans (VFR/IFR or #/type status); or hand off (2nd flight). Recommendation; don't offer to break up flights to help fellow sectors unless I have a D-Side to do the paperwork/coordination.

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