Narrative:

Line of broken thunderstorms grr to apn. ZAU refused extra dtw descent traffic. ZAU had no WX on southwest arrival (fwa.MIZAR3) to dtw. ZMP tmu accepted flow restriction from ZOB for dtw descent traffic routed aircraft 10 mi in trail and assigned it to my sector. In order to comply with this flow restriction the controller had to space the aircraft 20 mi in trail; then let them deviate at FL230 through a hole over htl; and finally descend them to FL210 expeditiously after they topped the line of thunderstorms. As I relieved the trainer and trainee on tvc low (FL230 descending) there was a heated exchange over aircraft X to be routed over tvc direct mbs. I took over the sector and looked at aircraft X flight strip (original) and it said 'tvc direct mbs.' I worked aircraft X over the thunderstorm at htl; descended to FL210 and handed off to ZOB by computer. I put aircraft on ZOB fnt frequency. One hour later I was called on a deviation. The previous high altitude controller rerouted aircraft X grb direct mbs which goes to ZOB lan sector. The high altitude controller never rerouted the aircraft back over tvc direct mbs. The trainer/trainee never rerouted the aircraft. I saw the first strip (good routing) and assumed it was good. The revision strips were still in the printer because staffing was short due to thunderstorms. Because I assumed the right route was in the machine; I did not take time to check which ZOB sector had the handoff -- I only made sure ZOB had the handoff. So ZOB lan sector had the handoff and aircraft X deviated ZOB fnt sector for 15 mi.

Google
 

Original NASA ASRS Text

Title: ZMP CTLR EXPERIENCED OPDEV WHEN HDOF WAS MADE TO WRONG SECTOR BECAUSE OF INACCURATE FP INFO ON THE STRIP AT THE SECTOR.

Narrative: LINE OF BROKEN TSTMS GRR TO APN. ZAU REFUSED EXTRA DTW DESCENT TFC. ZAU HAD NO WX ON SOUTHWEST ARR (FWA.MIZAR3) TO DTW. ZMP TMU ACCEPTED FLOW RESTRICTION FROM ZOB FOR DTW DESCENT TFC ROUTED ACFT 10 MI IN TRAIL AND ASSIGNED IT TO MY SECTOR. IN ORDER TO COMPLY WITH THIS FLOW RESTRICTION THE CTLR HAD TO SPACE THE ACFT 20 MI IN TRAIL; THEN LET THEM DEVIATE AT FL230 THROUGH A HOLE OVER HTL; AND FINALLY DESCEND THEM TO FL210 EXPEDITIOUSLY AFTER THEY TOPPED THE LINE OF TSTMS. AS I RELIEVED THE TRAINER AND TRAINEE ON TVC LOW (FL230 DESCENDING) THERE WAS A HEATED EXCHANGE OVER ACFT X TO BE ROUTED OVER TVC DIRECT MBS. I TOOK OVER THE SECTOR AND LOOKED AT ACFT X FLIGHT STRIP (ORIGINAL) AND IT SAID 'TVC DIRECT MBS.' I WORKED ACFT X OVER THE TSTM AT HTL; DESCENDED TO FL210 AND HANDED OFF TO ZOB BY COMPUTER. I PUT ACFT ON ZOB FNT FREQ. ONE HOUR LATER I WAS CALLED ON A DEV. THE PREVIOUS HIGH ALT CTLR REROUTED ACFT X GRB DIRECT MBS WHICH GOES TO ZOB LAN SECTOR. THE HIGH ALT CONTROLLER NEVER REROUTED THE ACFT BACK OVER TVC DIRECT MBS. THE TRAINER/TRAINEE NEVER REROUTED THE ACFT. I SAW THE FIRST STRIP (GOOD ROUTING) AND ASSUMED IT WAS GOOD. THE REVISION STRIPS WERE STILL IN THE PRINTER BECAUSE STAFFING WAS SHORT DUE TO TSTMS. BECAUSE I ASSUMED THE RIGHT ROUTE WAS IN THE MACHINE; I DID NOT TAKE TIME TO CHECK WHICH ZOB SECTOR HAD THE HDOF -- I ONLY MADE SURE ZOB HAD THE HDOF. SO ZOB LAN SECTOR HAD THE HDOF AND ACFT X DEVIATED ZOB FNT SECTOR FOR 15 MI.

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