Narrative:

Cleveland has a very confusing area near runways 28/23L/right for taxi operations. We were cleared to taxi via the runway 28 hold short of runway 23L call tower. As we held short ground switched us to the tower. Then tower gave us clearance to runway 23R position and hold. We did just that via runway 28 to cross runway 23L and position and hold runway 23R at runway 28. Tower told us that we were on runway 28 which we rogered and asked if we could depart from runway 28 on runway 23R. Tower thought we would taxi via taxiway Z to runway 23R, but did not specify which route to take. Callback conversation with reporter revealed the following information: the reporter said that he and his captain do not often operate through cle and the lighting system and txwys were new to them. The first officer said that the new flashing hold line at runway 23L on runway 28 and the new centerline taxi lights on runway 28 are a great aid, particularly at night. Although the flight crew discussed the various potential taxi routes to runway 23R they did not know that the controller intended them to turn to the right and use taxiway Z to get to runway 23R and he does not recall the controllers mentioning taxiway Z. After takeoff they did discover that their data was based on using all of the runway although the intersection was more than adequate. After arrival at their destination the captain called the cle tower and spoke to a supervisor. Allegedly, the supervisor told the captain that the controller's only concern was that they not attempt a takeoff on runway 28. Otherwise the supervisor was not concerned about the intersection takeoff.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN ACR B737 FLC STAYED ON RWY 28 DURING THEIR TAXI ACROSS RWY 23L AND INTO POS ON RWY 23R INSTEAD OF USING TXWY Z. THE ATCT LCL CTLR WAS CONCERNED THAT THE FLC KNEW THAT THEY WERE ON RWY 28 INITIALLY AND LATER THAT THEY WERE NOT AT THE VERY END OF RWY 23R.

Narrative: CLEVELAND HAS A VERY CONFUSING AREA NEAR RWYS 28/23L/R FOR TAXI OPS. WE WERE CLRED TO TAXI VIA THE RWY 28 HOLD SHORT OF RWY 23L CALL TWR. AS WE HELD SHORT GND SWITCHED US TO THE TWR. THEN TWR GAVE US CLRNC TO RWY 23R POS AND HOLD. WE DID JUST THAT VIA RWY 28 TO CROSS RWY 23L AND POS AND HOLD RWY 23R AT RWY 28. TWR TOLD US THAT WE WERE ON RWY 28 WHICH WE ROGERED AND ASKED IF WE COULD DEPART FROM RWY 28 ON RWY 23R. TWR THOUGHT WE WOULD TAXI VIA TXWY Z TO RWY 23R, BUT DID NOT SPECIFY WHICH RTE TO TAKE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR SAID THAT HE AND HIS CAPT DO NOT OFTEN OPERATE THROUGH CLE AND THE LIGHTING SYS AND TXWYS WERE NEW TO THEM. THE FO SAID THAT THE NEW FLASHING HOLD LINE AT RWY 23L ON RWY 28 AND THE NEW CTRLINE TAXI LIGHTS ON RWY 28 ARE A GREAT AID, PARTICULARLY AT NIGHT. ALTHOUGH THE FLC DISCUSSED THE VARIOUS POTENTIAL TAXI ROUTES TO RWY 23R THEY DID NOT KNOW THAT THE CTLR INTENDED THEM TO TURN TO THE R AND USE TXWY Z TO GET TO RWY 23R AND HE DOES NOT RECALL THE CTLRS MENTIONING TXWY Z. AFTER TKOF THEY DID DISCOVER THAT THEIR DATA WAS BASED ON USING ALL OF THE RWY ALTHOUGH THE INTXN WAS MORE THAN ADEQUATE. AFTER ARR AT THEIR DEST THE CAPT CALLED THE CLE TWR AND SPOKE TO A SUPVR. ALLEGEDLY, THE SUPVR TOLD THE CAPT THAT THE CTLR'S ONLY CONCERN WAS THAT THEY NOT ATTEMPT A TKOF ON RWY 28. OTHERWISE THE SUPVR WAS NOT CONCERNED ABOUT THE INTXN TKOF.

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.