Narrative:

Aircraft X, eastbound at FL330, had been rerted to avoid WX and was flying eastbound on a wbound airway. Aircraft Y, at FL350 inbound to stl, needed descent to comply with LOA. During the time prior to and subsequent to the incident, I was working 25 aircraft -- 8 of which were climbing, 2 were descending, an additional aircraft was climbing on a vector, and 7 more were descending on vectors. Traffic was heavy and complex. Traffic was heavy and complex. I was working with a handoff controller and radar associate. Aircraft Y had not yet cleared aircraft X when I issued descent. Oedp activated after aircraft had already passed each. There was no conflict alert. Due to heavy complex traffic, all 3 controllers working the sector failed to see the confliction with aircraft X and Y. Traffic management unit had warned the supervisor at XA15 briefing that this sector would be busy and traffic management unit had issued minimal restrs to adjacent ctrs. This sector is always busy during this time. A more aggressive traffic management plan is needed to prevent this situation from recurring. Supplemental information from acn 414482: the events or contributing factors in this error are as follows: chop was occurring which added to the complexity by forcing the stl arrs lower than normal which made it difficult to get the cvg arrs down. Also, the chop situation added to frequency congestion. The sector got out of control due to the number of airplanes and the complexity. This caused us to shut off ZAU which put their sector out of control and then they had an error. Oedp activated which is what drew my attention to the error. Neither aircraft knew of the other and neither took evasive action. There should have been more mi in trail and maybe even aircraft held on the ground. The 'big sky theory' does not work!

Google
 

Original NASA ASRS Text

Title: ARTCC RADAR CTLR ISSUED DSCNT CLRNC THROUGH THE ASSIGNED ALT AND PROX OF XING TFC IN CRUISE ALT. DUE TO SECTOR COMPLEXITY AND TFC VOLUME, RADAR TEAM DID NOT SEE THE POTENTIAL CONFLICT UNTIL THE COMPUTER DETECTED THE ERROR. RADAR TEAM MAINTAINS THAT TFC MGMNT UNIT AND SUPVR SHOULD HAVE INTERVENED TO REDUCE SECTOR TFC COMPLEXITY MORE TIMELY.

Narrative: ACFT X, EBOUND AT FL330, HAD BEEN RERTED TO AVOID WX AND WAS FLYING EBOUND ON A WBOUND AIRWAY. ACFT Y, AT FL350 INBOUND TO STL, NEEDED DSCNT TO COMPLY WITH LOA. DURING THE TIME PRIOR TO AND SUBSEQUENT TO THE INCIDENT, I WAS WORKING 25 ACFT -- 8 OF WHICH WERE CLBING, 2 WERE DSNDING, AN ADDITIONAL ACFT WAS CLBING ON A VECTOR, AND 7 MORE WERE DSNDING ON VECTORS. TFC WAS HVY AND COMPLEX. TFC WAS HVY AND COMPLEX. I WAS WORKING WITH A HDOF CTLR AND RADAR ASSOCIATE. ACFT Y HAD NOT YET CLRED ACFT X WHEN I ISSUED DSCNT. OEDP ACTIVATED AFTER ACFT HAD ALREADY PASSED EACH. THERE WAS NO CONFLICT ALERT. DUE TO HVY COMPLEX TFC, ALL 3 CTLRS WORKING THE SECTOR FAILED TO SEE THE CONFLICTION WITH ACFT X AND Y. TFC MGMNT UNIT HAD WARNED THE SUPVR AT XA15 BRIEFING THAT THIS SECTOR WOULD BE BUSY AND TFC MGMNT UNIT HAD ISSUED MINIMAL RESTRS TO ADJACENT CTRS. THIS SECTOR IS ALWAYS BUSY DURING THIS TIME. A MORE AGGRESSIVE TFC MGMNT PLAN IS NEEDED TO PREVENT THIS SIT FROM RECURRING. SUPPLEMENTAL INFO FROM ACN 414482: THE EVENTS OR CONTRIBUTING FACTORS IN THIS ERROR ARE AS FOLLOWS: CHOP WAS OCCURRING WHICH ADDED TO THE COMPLEXITY BY FORCING THE STL ARRS LOWER THAN NORMAL WHICH MADE IT DIFFICULT TO GET THE CVG ARRS DOWN. ALSO, THE CHOP SIT ADDED TO FREQ CONGESTION. THE SECTOR GOT OUT OF CTL DUE TO THE NUMBER OF AIRPLANES AND THE COMPLEXITY. THIS CAUSED US TO SHUT OFF ZAU WHICH PUT THEIR SECTOR OUT OF CTL AND THEN THEY HAD AN ERROR. OEDP ACTIVATED WHICH IS WHAT DREW MY ATTN TO THE ERROR. NEITHER ACFT KNEW OF THE OTHER AND NEITHER TOOK EVASIVE ACTION. THERE SHOULD HAVE BEEN MORE MI IN TRAIL AND MAYBE EVEN ACFT HELD ON THE GND. THE 'BIG SKY THEORY' DOES NOT WORK!

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.