Narrative:

I was working the d-side at sector xx; the traffic volume was steady and increasing. An eclipse 500 was climbing out of approach on a vector climbing to 150. A beechjet 400 crossed the border of approach and sector xx level at FL190 approximately 30-40 miles in trail of the eclipse. The r-side was climbing the eclipse reference some other traffic in the sector. Once the eclipse was clear of the other traffic in the sector he continued the eclipse's climb to FL230. I didn't hear him issue the climb to the eclipse and I continued to work the d-side looking at routes; answering lines; and making point outs. When I went to do a traffic search I noticed that the beechjet 400 had overtaken the eclipse at the same time the r-side did and he issued vectors to both aircraft to diverge their courses; but separation was not maintained and the aircraft came within approximately 4 miles and 500 feet of each other. Recommendation; I could've listened more a tentatively and heard the r-side issue the climb to the eclipse. Also I should of noticed there was an overtake situation earlier and brought it to the r-side's attention. Additionally sector xx should be looked at for changes in procedures. Sector xx shared boundaries with three different approach controls; all of which have air traffic area's and dta's that the same location with aircraft climbing and descending within close proximity will exit and entering the approach control airspace. This causes many head on situations in proximity to the VORTAC. The r-side has to spend a lot of time focusing on this area. This is made even more difficult when the military uses two MOA's that causes a compression of traffic and extremely complex situations with aircraft climbing and descending head on and no room to turn them. When [one of the] MOA[s] is active it causes frequency congestion and confusion due to student pilots and aircraft talking on multiple frequencies.

Google
 

Original NASA ASRS Text

Title: Enroute Controller described a loss of separation event and provided a number of recommendations to lessen the chance of future same type occurrences.

Narrative: I was working the D-Side at Sector XX; the traffic volume was steady and increasing. An Eclipse 500 was climbing out of Approach on a vector climbing to 150. A Beechjet 400 crossed the border of Approach and Sector XX level at FL190 approximately 30-40 miles in trail of the Eclipse. The R-Side was climbing the Eclipse reference some other traffic in the sector. Once the Eclipse was clear of the other traffic in the sector he continued the Eclipse's climb to FL230. I didn't hear him issue the climb to the Eclipse and I continued to work the D-Side looking at routes; answering lines; and making point outs. When I went to do a traffic search I noticed that the Beechjet 400 had overtaken the Eclipse at the same time the R-Side did and he issued vectors to both aircraft to diverge their courses; but separation was not maintained and the aircraft came within approximately 4 miles and 500 feet of each other. Recommendation; I could've listened more a tentatively and heard the R-Side issue the climb to the Eclipse. Also I should of noticed there was an overtake situation earlier and brought it to the R-side's attention. Additionally Sector XX should be looked at for changes in procedures. Sector XX shared boundaries with three different approach controls; all of which have ATA's and DTA's that the same location with aircraft climbing and descending within close proximity will exit and entering the Approach Control airspace. This causes many head on situations in proximity to the VORTAC. The R-Side has to spend a lot of time focusing on this area. This is made even more difficult when the military uses two MOA's that causes a compression of traffic and extremely complex situations with aircraft climbing and descending head on and no room to turn them. When [one of the] MOA[s] is active it causes frequency congestion and confusion due to student pilots and aircraft talking on multiple frequencies.

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