Narrative:

When we were #2 for departure in denver on runway 35R, tower informed us to contact clearance for a rerte. The first officer contacted them and I monitored tower frequency. After receiving the new clearance, I informed the tower we were ready and were cleared for takeoff. While I had thought our clearance from sny took us over onl, the first officer had written down routing over obh. While I was tracking out of sny slightly south of track due to thunderstorm avoid, the first officer informed me that we should have been proceeding direct to obh via J84. By this time the center questioned us as to whether we were deviating for WX without clearance and we informed him that we were just slightly, and then having looked at J84 I realized that if that was our route we were way north. The center cleared us direct to dbq J94 and I informed him that we had not received that routing and read back to him the routing that I had thought the first officer received. Center reclred us direct dbq J94 obk J584 sct. After that conversation the first officer showed me that he had written down sny J94 obh J584 slt which didn't make any sense. I do recall having heard clearance say obh instead of obk. I spoke to the center supervisor that evening on the phone and he said that no conflicts had occurred, although at 31000 eastbound had we continued south it could have. I believe that this could have been avoided if I had also listened to clearance and verified the routing before we left den. I believe the denver clearance controller was in error by saying obh instead of obk and should spell it out phonetically with the 3 letter identify instead of saying the name to avoid mistake.

Related reports:

Google
 

Original NASA ASRS Text

Title: THE FO OF AN ACR MLG FAILED TO COPY A RERTED CLRNC CORRECTLY JUST PRIOR TO TKOF RESULTING IN A GROSS DEV FROM ASSIGNED TRACK.

Narrative: WHEN WE WERE #2 FOR DEP IN DENVER ON RWY 35R, TWR INFORMED US TO CONTACT CLRNC FOR A RERTE. THE FO CONTACTED THEM AND I MONITORED TWR FREQ. AFTER RECEIVING THE NEW CLRNC, I INFORMED THE TWR WE WERE READY AND WERE CLRED FOR TKOF. WHILE I HAD THOUGHT OUR CLRNC FROM SNY TOOK US OVER ONL, THE FO HAD WRITTEN DOWN ROUTING OVER OBH. WHILE I WAS TRACKING OUT OF SNY SLIGHTLY S OF TRACK DUE TO TSTM AVOID, THE FO INFORMED ME THAT WE SHOULD HAVE BEEN PROCEEDING DIRECT TO OBH VIA J84. BY THIS TIME THE CTR QUESTIONED US AS TO WHETHER WE WERE DEVIATING FOR WX WITHOUT CLRNC AND WE INFORMED HIM THAT WE WERE JUST SLIGHTLY, AND THEN HAVING LOOKED AT J84 I REALIZED THAT IF THAT WAS OUR RTE WE WERE WAY N. THE CTR CLRED US DIRECT TO DBQ J94 AND I INFORMED HIM THAT WE HAD NOT RECEIVED THAT ROUTING AND READ BACK TO HIM THE ROUTING THAT I HAD THOUGHT THE FO RECEIVED. CTR RECLRED US DIRECT DBQ J94 OBK J584 SCT. AFTER THAT CONVERSATION THE FO SHOWED ME THAT HE HAD WRITTEN DOWN SNY J94 OBH J584 SLT WHICH DIDN'T MAKE ANY SENSE. I DO RECALL HAVING HEARD CLRNC SAY OBH INSTEAD OF OBK. I SPOKE TO THE CTR SUPVR THAT EVENING ON THE PHONE AND HE SAID THAT NO CONFLICTS HAD OCCURRED, ALTHOUGH AT 31000 EBOUND HAD WE CONTINUED S IT COULD HAVE. I BELIEVE THAT THIS COULD HAVE BEEN AVOIDED IF I HAD ALSO LISTENED TO CLRNC AND VERIFIED THE ROUTING BEFORE WE LEFT DEN. I BELIEVE THE DENVER CLRNC CTLR WAS IN ERROR BY SAYING OBH INSTEAD OF OBK AND SHOULD SPELL IT OUT PHONETICALLY WITH THE 3 LETTER IDENT INSTEAD OF SAYING THE NAME TO AVOID MISTAKE.

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.