Narrative:

On taxi out from cle, we were given a clearance to taxi onto runway 28 and hold short of runway 23L for a runway 23R takeoff. At about the time we entered onto runway 28, we were told to go to tower frequency. Tower gave us a clearance to taxi up to runway 23L and hold short via runway 28. Because of miscom between tower, myself, and the captain, we taxied over the hold short line by about 10 ft. The tower then told us to stop, followed by cross runway 23L and position and hold runway 23R. He then told us to expedite. During this time a turboprop commuter was on an approximately 1-2 NM final for runway 23L. We took off from runway 23R without incident. I feel that this area on the airport is very confusing. Because of the 2 parallel runways and the crossing runways all within 100 yards of each other runway 28 should not be used for taxi. There were 3 different runways mentioned in our ground clearance causing some of the confusion. Callback conversation with reporter revealed the following information: reporter states the runway confign at cle is difficult to avoid such problems. When they were cleared to cross they felt the proximity of the landing aircraft was a bit closer than they would have liked. Reporter feels there is a better option to taxiing to runway 23R which is to have aircraft cross runway 23L and runway 23R at taxiway south for access to runway 23R. An additional problem is that there is a very short taxi from the terminal and checklists are in progress during the taxi so there is distraction in the cockpit. Of course the best solution would be to lengthen runway 23R and have traffic land on that runway and depart from runway 23L so there would not be a xover of traffic.

Google
 

Original NASA ASRS Text

Title: FLC OF B737-200 FAILS TO HOLD SHORT AS CLRED. TWR THEN CLRS THEM TO EXPEDITE ACROSS THE L RWY AND INTO POS ON THE R.

Narrative: ON TAXI OUT FROM CLE, WE WERE GIVEN A CLRNC TO TAXI ONTO RWY 28 AND HOLD SHORT OF RWY 23L FOR A RWY 23R TKOF. AT ABOUT THE TIME WE ENTERED ONTO RWY 28, WE WERE TOLD TO GO TO TWR FREQ. TWR GAVE US A CLRNC TO TAXI UP TO RWY 23L AND HOLD SHORT VIA RWY 28. BECAUSE OF MISCOM BTWN TWR, MYSELF, AND THE CAPT, WE TAXIED OVER THE HOLD SHORT LINE BY ABOUT 10 FT. THE TWR THEN TOLD US TO STOP, FOLLOWED BY CROSS RWY 23L AND POS AND HOLD RWY 23R. HE THEN TOLD US TO EXPEDITE. DURING THIS TIME A TURBOPROP COMMUTER WAS ON AN APPROX 1-2 NM FINAL FOR RWY 23L. WE TOOK OFF FROM RWY 23R WITHOUT INCIDENT. I FEEL THAT THIS AREA ON THE ARPT IS VERY CONFUSING. BECAUSE OF THE 2 PARALLEL RWYS AND THE XING RWYS ALL WITHIN 100 YARDS OF EACH OTHER RWY 28 SHOULD NOT BE USED FOR TAXI. THERE WERE 3 DIFFERENT RWYS MENTIONED IN OUR GND CLRNC CAUSING SOME OF THE CONFUSION. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES THE RWY CONFIGN AT CLE IS DIFFICULT TO AVOID SUCH PROBS. WHEN THEY WERE CLRED TO CROSS THEY FELT THE PROX OF THE LNDG ACFT WAS A BIT CLOSER THAN THEY WOULD HAVE LIKED. RPTR FEELS THERE IS A BETTER OPTION TO TAXIING TO RWY 23R WHICH IS TO HAVE ACFT CROSS RWY 23L AND RWY 23R AT TXWY S FOR ACCESS TO RWY 23R. AN ADDITIONAL PROB IS THAT THERE IS A VERY SHORT TAXI FROM THE TERMINAL AND CHKLISTS ARE IN PROGRESS DURING THE TAXI SO THERE IS DISTR IN THE COCKPIT. OF COURSE THE BEST SOLUTION WOULD BE TO LENGTHEN RWY 23R AND HAVE TFC LAND ON THAT RWY AND DEPART FROM RWY 23L SO THERE WOULD NOT BE A XOVER OF TFC.

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.