BA32 crew had runway incursion at cle.

Attributes
ACN	440050
Time
Date	199906
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : cle.airport
State Reference	OH
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Jetstream 32
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 240 flight time total : 3200 flight time type : 700
ASRS Report	440050
Person 2
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial pilot : multi engine
Events
Anomaly	incursion : runway non adherence : clearance non adherence : published procedure
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance Airport FAA
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation
Situations
Airport	markings : cle.airport procedure or policy : cle.airport signage : cle.airport

Narrative:

Aircraft just landed on runway 5R at cleveland. Another aircraft position and hold on runway 5L. We were instructed to cross runway 5R hold short runway 5L. We crossed runway 5R and crossed over the first set of 2 hold short lines thinking we would be clear of runway 5R and stopped short of the second set of hold short lines thinking we would be holding short of runway 5L. After setting the parking brake, we realized we had already crossed the runway 5L hold short line and we were on the active runway 5L with the other aircraft still in position. Then they were cleared for takeoff and we were cleared to position and hold. It is not possible to be clear of runway 5R and holding short of runway 5L at the same time. The signage is poor and should include flashing lights same as hold short for runway 5R. This was never a safety of flight issue, but it could have been.

Original NASA ASRS Text

Title: BA32 CREW HAD RWY INCURSION AT CLE.

Narrative: ACFT JUST LANDED ON RWY 5R AT CLEVELAND. ANOTHER ACFT POS AND HOLD ON RWY 5L. WE WERE INSTRUCTED TO CROSS RWY 5R HOLD SHORT RWY 5L. WE CROSSED RWY 5R AND CROSSED OVER THE FIRST SET OF 2 HOLD SHORT LINES THINKING WE WOULD BE CLR OF RWY 5R AND STOPPED SHORT OF THE SECOND SET OF HOLD SHORT LINES THINKING WE WOULD BE HOLDING SHORT OF RWY 5L. AFTER SETTING THE PARKING BRAKE, WE REALIZED WE HAD ALREADY CROSSED THE RWY 5L HOLD SHORT LINE AND WE WERE ON THE ACTIVE RWY 5L WITH THE OTHER ACFT STILL IN POS. THEN THEY WERE CLRED FOR TKOF AND WE WERE CLRED TO POS AND HOLD. IT IS NOT POSSIBLE TO BE CLR OF RWY 5R AND HOLDING SHORT OF RWY 5L AT THE SAME TIME. THE SIGNAGE IS POOR AND SHOULD INCLUDE FLASHING LIGHTS SAME AS HOLD SHORT FOR RWY 5R. THIS WAS NEVER A SAFETY OF FLT ISSUE, BUT IT COULD HAVE BEEN.

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.