Narrative:

I was working the d-side at sandusky (07). My r-side asked me to route air carrier X in direct drk. I did; he issued it to the pilot; and the pilot accepted it. About 30 seconds after it was issued; the pilot came back and asked for the spelling of the drk. The r-side gave it to the pilot and then the pilot said that they wanted to stay on their original route. My r-side put the aircraft back on its route and I went to the user request evaluation tool (uret) to put the previous route back in on the aircraft; [but] the computer would not accept it. I tried one or two more times and was still unsuccessful. After that; I tried unsuccessfully to enter the information manually. By this time the aircraft was level at FL260. While I was doing that my r-side pointed air carrier X out to the dayton (I88) sector and told them we were putting the routing in on the aircraft and would flash the aircraft to them when we were done. Dayton agreed and told us to leave the aircraft at FL260. The r-side then pointed the aircraft out to the fwa (G36) sector. My r-side tried 3 times to give the routing information to ZID after we discovered we could not get it in the machine and they said they would call us back. Finally; I called dayton and forwarded the route information and they called r-side contact and the r-side person put the aircraft on the dayton sector. Don't get into a bad situation of shortcutting an aircraft so close to the boundary; because the information might not pass successfully.

Google
 

Original NASA ASRS Text

Title: ZOB D-Side Controller described a confused re-routing/coordination event when the RADAR Controller attempted to reroute an aircraft close to another sectors boundary requiring multiple coordination and automation actions.

Narrative: I was working the D-Side at Sandusky (07). My R-Side asked me to route Air Carrier X in direct DRK. I did; he issued it to the pilot; and the pilot accepted it. About 30 seconds after it was issued; the pilot came back and asked for the spelling of the DRK. The R-Side gave it to the pilot and then the pilot said that they wanted to stay on their original route. My R-Side put the aircraft back on its route and I went to the User Request Evaluation Tool (URET) to put the previous route back in on the aircraft; [but] the computer would not accept it. I tried one or two more times and was still unsuccessful. After that; I tried unsuccessfully to enter the information manually. By this time the aircraft was level at FL260. While I was doing that my R-Side pointed Air Carrier X out to the Dayton (I88) Sector and told them we were putting the routing in on the aircraft and would flash the aircraft to them when we were done. Dayton agreed and told us to leave the aircraft at FL260. The R-Side then pointed the aircraft out to the FWA (G36) Sector. My R-Side tried 3 times to give the routing information to ZID after we discovered we could not get it in the machine and they said they would call us back. Finally; I called Dayton and forwarded the route information and they called R-Side contact and the R-Side person put the aircraft on the Dayton sector. Don't get into a bad situation of shortcutting an aircraft so close to the boundary; because the information might not pass successfully.

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