Unauthorized runway crossing.

Attributes
ACN	299085
Time
Date	199503
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : day
State Reference	OH
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	ground other : taxi
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private pilot : instrument pilot : commercial
Experience	flight time last 90 days : 25 flight time total : 2100
ASRS Report	299085
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	incursion : runway non adherence : clearance
Independent Detector	other controllera other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Originally cleared to taxi to runway 24L. Requested runway 18 departure and approved by ground control. While taxiing parallel to runway 18, momentarily diverted, then I saw aircraft taxiing to runway 24R, on taxiway, other side of runway 18. I turned to cross runway 18 to other side for runway 24R departure, now thinking this was my assigned runway. Bothered by idea of crossing runway 18, I called ground controller to assure clearance to cross runway 18, I was at runway edge where told I had been cleared to runway 18, but I could taxi down runway 18 to departure end. Did so and departed without incident. Corrective: allow no diversions during taxi operations, such as setting radios. Particularly important with multiple active runways. Further recommendations: perhaps ground control could state 'taxi FBO to departure runway 18 remain parallel taxiway without runway crossover.'

Original NASA ASRS Text

Title: UNAUTH RWY XING.

Narrative: ORIGINALLY CLRED TO TAXI TO RWY 24L. REQUESTED RWY 18 DEP AND APPROVED BY GND CTL. WHILE TAXIING PARALLEL TO RWY 18, MOMENTARILY DIVERTED, THEN I SAW ACFT TAXIING TO RWY 24R, ON TXWY, OTHER SIDE OF RWY 18. I TURNED TO CROSS RWY 18 TO OTHER SIDE FOR RWY 24R DEP, NOW THINKING THIS WAS MY ASSIGNED RWY. BOTHERED BY IDEA OF XING RWY 18, I CALLED GND CTLR TO ASSURE CLRNC TO CROSS RWY 18, I WAS AT RWY EDGE WHERE TOLD I HAD BEEN CLRED TO RWY 18, BUT I COULD TAXI DOWN RWY 18 TO DEP END. DID SO AND DEPARTED WITHOUT INCIDENT. CORRECTIVE: ALLOW NO DIVERSIONS DURING TAXI OPS, SUCH AS SETTING RADIOS. PARTICULARLY IMPORTANT WITH MULTIPLE ACTIVE RWYS. FURTHER RECOMMENDATIONS: PERHAPS GND CTL COULD STATE 'TAXI FBO TO DEP RWY 18 REMAIN PARALLEL TXWY WITHOUT RWY CROSSOVER.'

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.