Eclipse 500
Air Traffic Control Developmental
Situational Awareness
ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Human Factors
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.
An Eclipse 500 was climbing out and was previously on vectors. A Beechjet 400 also came out level and on course. I cleared the Eclipse on course which turned him left about 20 degrees and put him in the path of the Beechjet. I never saw the Beechjet as traffic for the Eclipse; I was much more concerned with all the other departing traffic mixing with the inbounds. Also; I think I may have thought the Eclipse was a Phenom instead of an Eclipse jet. I had a j-ring up on the Eclipse for some previous traffic and it was actually the R-Side Trainee at R11 that leaned over and pointed out the traffic. The Eclipse was at [FL] 189 climbing and the Beechjet was at [FL] 190 about 5.5 miles behind and overtaking. It was too late to avoid a loss of separation but nobody was in danger so I turned the Beechjet left 30 degrees and the other 30 degrees right. I may not have been paying as much attention to the Beechjet because that type of flight comes out of approach level at [FL] 190 and on course. It was a much less active scan that with the Eclipse who was being laddered up and vectored for climb. This was all me; just a bad and incomplete scan.
Enroute Controller described a loss of separation event and provided a number of recommendations to lessen the chance of future same type occurrences.