A C410 pilot, taxiing for takeoff at slc, taxied across his assigned runway without a clearance.

Attributes
ACN	546353
Time
Date	200205
Day	Tue
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : slc.airport
State Reference	UT
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tower : syr.tower
Operator	general aviation : personal
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Flight Plan	None
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : cfi
Experience	controller non radar : 2 controller radar : 2 flight time last 90 days : 60 flight time total : 320 flight time type : 15
ASRS Report	546353
Person 2
Affiliation	government : faa
Function	controller : ground
Events
Anomaly	non adherence : far non adherence : clearance non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

It was early tuesday morning approximately XA30. The regular runway 35 has been closed for servicing. I was given a different taxi instruction, but was fairly familiar with airport to know what ATC wanted. I was cleared to taxi to and hold short of runway 32. The airport is laid out so runway 32 and runway 35 intersect each other at 30 degrees at the thresholds. My perception of the airport layout was that they were 2 separate runways. I taxied across runway 35 to hold short of runway 32, but unknowingly taxied across runway 32. I had seen the red signs indicating the runways 32 and 35, but they did not register to me. Luckily, no aircraft were on final and no one was endangered. However, I had failed to stop and hold short at the intersection. The contributing factors that I believed that played a role in this situation were fatigue, lack of proper preflight planning (I had the taxi layout of the airport in the flight bag but did not study it), and failure to comprehend the red runway signs posted. This event has taught me there is no substitute for proper preflight planning and being at 1000/0 attentive to the flight.

Original NASA ASRS Text

Title: A C410 PLT, TAXIING FOR TKOF AT SLC, TAXIED ACROSS HIS ASSIGNED RWY WITHOUT A CLRNC.

Narrative: IT WAS EARLY TUESDAY MORNING APPROX XA30. THE REGULAR RWY 35 HAS BEEN CLOSED FOR SVCING. I WAS GIVEN A DIFFERENT TAXI INSTRUCTION, BUT WAS FAIRLY FAMILIAR WITH ARPT TO KNOW WHAT ATC WANTED. I WAS CLRED TO TAXI TO AND HOLD SHORT OF RWY 32. THE ARPT IS LAID OUT SO RWY 32 AND RWY 35 INTERSECT EACH OTHER AT 30 DEGS AT THE THRESHOLDS. MY PERCEPTION OF THE ARPT LAYOUT WAS THAT THEY WERE 2 SEPARATE RWYS. I TAXIED ACROSS RWY 35 TO HOLD SHORT OF RWY 32, BUT UNKNOWINGLY TAXIED ACROSS RWY 32. I HAD SEEN THE RED SIGNS INDICATING THE RWYS 32 AND 35, BUT THEY DID NOT REGISTER TO ME. LUCKILY, NO ACFT WERE ON FINAL AND NO ONE WAS ENDANGERED. HOWEVER, I HAD FAILED TO STOP AND HOLD SHORT AT THE INTXN. THE CONTRIBUTING FACTORS THAT I BELIEVED THAT PLAYED A ROLE IN THIS SIT WERE FATIGUE, LACK OF PROPER PREFLT PLANNING (I HAD THE TAXI LAYOUT OF THE ARPT IN THE FLT BAG BUT DID NOT STUDY IT), AND FAILURE TO COMPREHEND THE RED RWY SIGNS POSTED. THIS EVENT HAS TAUGHT ME THERE IS NO SUBSTITUTE FOR PROPER PREFLT PLANNING AND BEING AT 1000/0 ATTENTIVE TO THE FLT.

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.