A B767-300 crew, taxiing for takeoff at slc, taxied past the hold short line.

Attributes
ACN	533501
Time
Date	200112
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : slc.airport
State Reference	UT
Altitude	agl single value : 0
Environment
Flight Conditions	IMC
Weather Elements	Fog
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : commercial pilot : flight engineer pilot : instrument pilot : multi engine pilot : private
Experience	flight time last 90 days : 80 flight time total : 4000 flight time type : 500
ASRS Report	533501
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	incursion : runway non adherence : published procedure non adherence : clearance non adherence : far other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Weather Airport Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

1000 ft RVR. Ground control cleared us to back-taxi down runway 32 and hold short of runway 35. Runway hold short line for runway 35 appeared to be actually on runway 32. We noticed this as we passed the line and came to a stop about 20 ft past. No part of the aircraft was actually on runway 35. Visibility was poor, tower immediately cleared us for takeoff and there were no conflicts. In hindsight, I'm not even sure a runway incursion occurred. The hold short markings at that location on the airport are very confusing, and we didn't have a chance to get a good look at them. I would recommend a 'blow-up' diagram on the airport 10-9 page for this intersection with emphasis on the hold short lines. Callback conversation with reporter revealed the following information: an slc tower specialist revealed that runway 32 does indeed display hold short lines for runway 35 located just north of the numbers for runway 32. This is due to the fact that runway 14/32 is often used as taxiway access to runway 35.

Original NASA ASRS Text

Title: A B767-300 CREW, TAXIING FOR TKOF AT SLC, TAXIED PAST THE HOLD SHORT LINE.

Narrative: 1000 FT RVR. GND CTL CLRED US TO BACK-TAXI DOWN RWY 32 AND HOLD SHORT OF RWY 35. RWY HOLD SHORT LINE FOR RWY 35 APPEARED TO BE ACTUALLY ON RWY 32. WE NOTICED THIS AS WE PASSED THE LINE AND CAME TO A STOP ABOUT 20 FT PAST. NO PART OF THE ACFT WAS ACTUALLY ON RWY 35. VISIBILITY WAS POOR, TWR IMMEDIATELY CLRED US FOR TKOF AND THERE WERE NO CONFLICTS. IN HINDSIGHT, I'M NOT EVEN SURE A RWY INCURSION OCCURRED. THE HOLD SHORT MARKINGS AT THAT LOCATION ON THE ARPT ARE VERY CONFUSING, AND WE DIDN'T HAVE A CHANCE TO GET A GOOD LOOK AT THEM. I WOULD RECOMMEND A 'BLOW-UP' DIAGRAM ON THE ARPT 10-9 PAGE FOR THIS INTXN WITH EMPHASIS ON THE HOLD SHORT LINES. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: AN SLC TWR SPECIALIST REVEALED THAT RWY 32 DOES INDEED DISPLAY HOLD SHORT LINES FOR RWY 35 LOCATED JUST N OF THE NUMBERS FOR RWY 32. THIS IS DUE TO THE FACT THAT RWY 14/32 IS OFTEN USED AS TXWY ACCESS TO RWY 35.

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.