Narrative:

Air carrier X was en route to pittsburgh, departed atlanta, J91 after knoxville, climbing to FL330. When air carrier X was approximately 10 mi northeast of knoxville, I was given a handoff on air carrier Y at FL310. Air carrier Y had departed baltimore en route to cleveland and was wbound about 10 mi south of the indianapolis boundary, deviating for WX. I called the salem sector for a 30 degree left turn on air carrier Y and was informed air carrier Y was NORDO. Air carrier X, still climbing, was asked to expedite to FL330, no response. About this time indianapolis called and said that air carrier Z was at FL310, which at this time was opposite direction from air carrier X. Also, air carrier Z was converging with air carrier Y still at FL310. I was informed that air carrier Z was also a NORDO. Air carrier X was again asked to expedite to FL330. The indianapolis controller re-entered air carrier Z flight plan in the computer. Air carrier Z was in atlanta airspace when the handoff was flashed to me. Separation was lost at FL324 and 1.75 mi. WX was a very important factor. By this time the indianapolis controller and myself were not controling but trying to miss other aircraft. All this deviation was due to WX present at this time. Other controllers I talked with experienced the same on other sectors. For awhile it was complete chaos and just about out of control. Air carrier Z, still at FL310, after passing air carrier X, made a right turn in front of air carrier Y and contacted atlanta center on my frequency 125.92. I immediately descended air carrier Z to FL290. Air carrier Y made a right turn into indianapolis airspace without a handoff or pointout. I came on duty at XX00 and was briefed on the WX. It did not improve during my tour of duty, or until the previous mentioned problems occurred, but I believe got worse. Something needs to be done. Maybe flow control needs to get involved.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR CAME IN CLOSE PROX TO ANOTHER ACR DURING ADVERSE WX CONDITIONS.

Narrative: ACR X WAS ENRTE TO PITTSBURGH, DEPARTED ATLANTA, J91 AFTER KNOXVILLE, CLIMBING TO FL330. WHEN ACR X WAS APPROX 10 MI NE OF KNOXVILLE, I WAS GIVEN A HANDOFF ON ACR Y AT FL310. ACR Y HAD DEPARTED BALTIMORE ENRTE TO CLEVELAND AND WAS WBOUND ABOUT 10 MI S OF THE INDIANAPOLIS BOUNDARY, DEVIATING FOR WX. I CALLED THE SALEM SECTOR FOR A 30 DEG LEFT TURN ON ACR Y AND WAS INFORMED ACR Y WAS NORDO. ACR X, STILL CLIMBING, WAS ASKED TO EXPEDITE TO FL330, NO RESPONSE. ABOUT THIS TIME INDIANAPOLIS CALLED AND SAID THAT ACR Z WAS AT FL310, WHICH AT THIS TIME WAS OPPOSITE DIRECTION FROM ACR X. ALSO, ACR Z WAS CONVERGING WITH ACR Y STILL AT FL310. I WAS INFORMED THAT ACR Z WAS ALSO A NORDO. ACR X WAS AGAIN ASKED TO EXPEDITE TO FL330. THE INDIANAPOLIS CTLR RE-ENTERED ACR Z FLT PLAN IN THE COMPUTER. ACR Z WAS IN ATLANTA AIRSPACE WHEN THE HANDOFF WAS FLASHED TO ME. SEPARATION WAS LOST AT FL324 AND 1.75 MI. WX WAS A VERY IMPORTANT FACTOR. BY THIS TIME THE INDIANAPOLIS CTLR AND MYSELF WERE NOT CTLING BUT TRYING TO MISS OTHER ACFT. ALL THIS DEVIATION WAS DUE TO WX PRESENT AT THIS TIME. OTHER CTLRS I TALKED WITH EXPERIENCED THE SAME ON OTHER SECTORS. FOR AWHILE IT WAS COMPLETE CHAOS AND JUST ABOUT OUT OF CONTROL. ACR Z, STILL AT FL310, AFTER PASSING ACR X, MADE A RIGHT TURN IN FRONT OF ACR Y AND CONTACTED ATLANTA CENTER ON MY FREQ 125.92. I IMMEDIATELY DESCENDED ACR Z TO FL290. ACR Y MADE A RIGHT TURN INTO INDIANAPOLIS AIRSPACE WITHOUT A HANDOFF OR POINTOUT. I CAME ON DUTY AT XX00 AND WAS BRIEFED ON THE WX. IT DID NOT IMPROVE DURING MY TOUR OF DUTY, OR UNTIL THE PREVIOUS MENTIONED PROBLEMS OCCURRED, BUT I BELIEVE GOT WORSE. SOMETHING NEEDS TO BE DONE. MAYBE FLOW CONTROL NEEDS TO GET INVOLVED.

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