FLC OF B737 IS GIVEN CLRNC TO CROSS RWY AND MAKE AN INTXN TKOF. UNABLE TO COMPLY WITH CLRNC DUE TO COMPANY PROCS THEY BELIEVE THEY ARE CLRED TO BACK TAXI AND POS AND HOLD. ACFT ON FINAL IS GIVEN A GAR.

Narrative

FOLLOWING PUSHBACK FROM GATE AT CLEVELAND HOPKINS INTL ARPT; I WAS CLRED TO TAXI TO RWY 23L AT TXWY W. THAT POINT IS AN INTXN TKOF POINT THAT IS LEGAL FOR MY ACFT SO I BEGAN TO TAXI. THAT INTXN IS FREQUENTLY USED FOR DEP WITH ARRS FLYING THE ILS TO RWY 23L WITH A SIDESTEP TO RWY 23R. WE SWITCHED TO TWR FREQ AND COULD SEE ANOTHER ACFT ON AN APPROX 4-5 MI FINAL. WE COULD NOT TELL THAT ACFT'S ALIGNMENT BECAUSE RWYS 23L AND 23R ARE ONLY ABOUT 200 FT APART. ADDITIONALLY; THERE HAD NOT BEEN ANY COM BTWN TWR AND THAT ACFT SINCE WE HAD TUNED IN TWR FREQ. I WAS EXPECTING A CLRNC FOR TKOF ON RWY 23L AT TXWY W SINCE THAT WAS THE 'NORM.' WE HAVE A LAPTOP COMPUTER LOCATED IN A RECHARGING CRADLE BEHIND THE FO'S SEAT THAT HAS UPDATED TKOF AND LNDG DATA FOR ALL OUR OPS. THIS PARTICULAR INTXN IS PUBLISHED ON THE LAPTOP AND IS LEGAL FOR OUR USE. WHEN A CLRNC IS GIVEN OTHER THAN THE PLANNED WE GO IMMEDIATELY TO THE COMPUTER TO SEE IF IT IS LEGAL. CLEVELAND TWR GAVE US THE FOLLOWING CLRNC; 'CALL SIGN CROSS RWY 23L; CLRED FOR TKOF RWY 23R AT INTXN W.' MY FO AND I HAD THE SAME THOUGHT; CAN WE DO IT. HE IMMEDIATELY REACHED FOR THE COMPUTER WHILE I ACKNOWLEDGED AND STARTED A SLOW TAXI. QUICKLY; THE FO DISCOVERED WE WERE NOT LEGAL FOR THAT CLRNC. I CALLED TWR AND TOLD THEM WE COULDN'T ACCEPT THAT CLRNC AND HE REPLIED; 'CANCEL TKOF CLRNC AND BACK TAXI INTO POS (WHAT I THINK I HEARD) RWY 23L AND HOLD.' I HAD TAXIED REALLY SLOW WHILE THIS WAS OCCURRING SO I TURNED R TO BACK TAXI ON RWY 23L. MY FO DIDN'T CHALLENGE ME WHEN I REPEATED THE CLRNC BACK TAXI INTO POS AND HOLD RWY 23L. HIS ATTN WAS DIVERTED RESTOWING THE LAPTOP COMPUTER. I TURNED ON ALL MY LNDG LIGHTS TO MAKE SURE THE ACFT ON FINAL WOULD SEE ME. AT THIS POINT TWR SAID; 'CALL SIGN; YOU'RE ON RWY 23L.' I REPLIED; 'ROGER I'M INTO POS RWY 23L TO HOLD.' ABOUT THAT TIME THE ACFT ON FINAL QUERIED TWR AND TWR SENT HIM AROUND. I TOLD TWR THAT I HAD HEARD BACK TAXI TO RWY 23L AND HOLD. HE REPLIED WE WOULD TALK ABOUT IT LATER. I REPLIED ROGER. TWR SUBSEQUENTLY CLRED US FOR TKOF AND WE DEPARTED WITHOUT INCIDENT. TWR SWITCHED US TO DEP WITHOUT GIVING US A PHONE NUMBER SO I ASKED FOR THE NUMBER FROM DEP AND GAVE THEM A CALL WHEN I REACHED MY DEST. I CALLED THE TWR SUPVR AND EXPLAINED MY VERSION OF THE INCIDENT AND ABOUT THE TKOF DATA POLICIES OF OUR COMPANY. HE WAS NOT AWARE WE COULD NOT USE THE INTXN THAT HAD BEEN GIVEN TO US. HE SAID THAT NO ACTION WOULD BE TAKEN SINCE WE HAD BEEN GIVEN ACCESS TO THE RWY AND THAT WE HAD ALL LEARNED FROM THIS INCIDENT. I CALLED THE CLEVELAND OPS MGR THE NEXT DAY FOR A FOLLOW UP AND HE PRETTY MUCH GAVE ME THE SAME REPLY AS THE TWR SUPVR THE NIGHT BEFORE. IN MY MIND I HEARD RWY 23L BUT COULD HAVE BEEN MISTAKEN DUE TO MY EXPECTATIONS COUPLED WITH THE UNUSUAL CLRNC AND INCREASED ACTIVITY IN THE COCKPIT. BETTER COM BTWN TWR AND MY ACFT AND BETTER FAMILIARIZATION OF OUR PROCS BY TWR COULD HAVE PREVENTED THIS INCIDENT. AS THE TWR SUPVR STATED; BOTH OF US LEARNED FROM THIS INCIDENT.