Narrative:

I was working a high altitude radar sector at ZKC. Thunderstorms are impacting the arrival fixes for st louis, mo. Air carrier Y, an MD80, filed stl-irw, landing dfw and air carrier Y, MD80, filed J141.sgf.TRAKE8.stl -- both at FL310. Air carrier X was right altitude for direction of flight at FL310. But, because of WX rerte, he made a 100 degree right turn at sgf putting him wrong altitude for direction of flight at FL310. Also, this put him in confliction with air carrier Y. Air carrier X and air carrier Y both received an RA. I thought I had shipped air carrier X to the next sector's frequency. Air carrier Y was already on the next sector's frequency. I had dropped the data blocks on both aircraft since they were out of my airspace. Air carrier X advised he had received an RA and was climbing out of FL310.

Google
 

Original NASA ASRS Text

Title: ZKC CTLR BELIEVES HE CHANGED FREQ TO ENRTE, WX DEVIATING MD80, WHICH CONFLICTS WITH ANOTHER ACR OUTSIDE OF HIS DELEGATED AIRSPACE.

Narrative: I WAS WORKING A HIGH ALT RADAR SECTOR AT ZKC. TSTMS ARE IMPACTING THE ARR FIXES FOR ST LOUIS, MO. ACR Y, AN MD80, FILED STL-IRW, LNDG DFW AND ACR Y, MD80, FILED J141.SGF.TRAKE8.STL -- BOTH AT FL310. ACR X WAS RIGHT ALT FOR DIRECTION OF FLT AT FL310. BUT, BECAUSE OF WX RERTE, HE MADE A 100 DEG R TURN AT SGF PUTTING HIM WRONG ALT FOR DIRECTION OF FLT AT FL310. ALSO, THIS PUT HIM IN CONFLICTION WITH ACR Y. ACR X AND ACR Y BOTH RECEIVED AN RA. I THOUGHT I HAD SHIPPED ACR X TO THE NEXT SECTOR'S FREQ. ACR Y WAS ALREADY ON THE NEXT SECTOR'S FREQ. I HAD DROPPED THE DATA BLOCKS ON BOTH ACFT SINCE THEY WERE OUT OF MY AIRSPACE. ACR X ADVISED HE HAD RECEIVED AN RA AND WAS CLBING OUT OF FL310.

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.