PA28 pilot properly crossed a runway when given clearance to taxi to a different runway.

Attributes
ACN	477640
Time
Date	200007
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : mfd.airport
State Reference	OH
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	PA-28 Cherokee/Archer II/Dakota/Pillan/Warrior
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Flight Plan	None
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private pilot : instrument
Experience	flight time last 90 days : 8 flight time total : 689 flight time type : 615
ASRS Report	477640
Person 2
Affiliation	government : faa
Function	controller : combined local
Qualification	controller : non radar
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

On jul/xa/00 at approximately XA15, I was at mfd taxiing to the active runway. At this time, ATIS information was in effect. ATIS information gave runway 23 as the active runway. I contacted ground for taxi instructions. Initially, ground gave me clearance to depart runway 23. I corrected ground that I was ready to taxi with current ATIS information. Ground cleared me to 'taxi to runway 23, hold short runway 23.' at least that is what I understood. In taxiing to runway 23, I was required to cross runway 32. In doing so, ground indicated to me that I had not been cleared to cross runway 32, but it was no problem. The controller was functioning as both tower and ground. It was apparent that the controller was a little rattled when she cleared me for takeoff instead of taxi. I should have been cleared to taxi to taxiway B, hold short runway 32. Having runways 32 and 23 can be confusing unless instructions are more clear. I believed that I had been cleared to taxi to the active runway, but not cleared to take the runway. Runway 23 was the active runway per ATIS and I had no reason to believe that I had not been cleared to taxi to the active, including crossing the inactive runway 32.

Original NASA ASRS Text

Title: PA28 PLT PROPERLY CROSSED A RWY WHEN GIVEN CLRNC TO TAXI TO A DIFFERENT RWY.

Narrative: ON JUL/XA/00 AT APPROX XA15, I WAS AT MFD TAXIING TO THE ACTIVE RWY. AT THIS TIME, ATIS INFO WAS IN EFFECT. ATIS INFO GAVE RWY 23 AS THE ACTIVE RWY. I CONTACTED GND FOR TAXI INSTRUCTIONS. INITIALLY, GND GAVE ME CLRNC TO DEPART RWY 23. I CORRECTED GND THAT I WAS READY TO TAXI WITH CURRENT ATIS INFO. GND CLRED ME TO 'TAXI TO RWY 23, HOLD SHORT RWY 23.' AT LEAST THAT IS WHAT I UNDERSTOOD. IN TAXIING TO RWY 23, I WAS REQUIRED TO CROSS RWY 32. IN DOING SO, GND INDICATED TO ME THAT I HAD NOT BEEN CLRED TO CROSS RWY 32, BUT IT WAS NO PROB. THE CTLR WAS FUNCTIONING AS BOTH TWR AND GND. IT WAS APPARENT THAT THE CTLR WAS A LITTLE RATTLED WHEN SHE CLRED ME FOR TKOF INSTEAD OF TAXI. I SHOULD HAVE BEEN CLRED TO TAXI TO TXWY B, HOLD SHORT RWY 32. HAVING RWYS 32 AND 23 CAN BE CONFUSING UNLESS INSTRUCTIONS ARE MORE CLR. I BELIEVED THAT I HAD BEEN CLRED TO TAXI TO THE ACTIVE RWY, BUT NOT CLRED TO TAKE THE RWY. RWY 23 WAS THE ACTIVE RWY PER ATIS AND I HAD NO REASON TO BELIEVE THAT I HAD NOT BEEN CLRED TO TAXI TO THE ACTIVE, INCLUDING XING THE INACTIVE RWY 32.

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.