B737 captain reports being cleared to taxi via runway 26 to runway 33 at bur but is unsure of which ...

Narrative:

Just prior to push; new ATIS came out which favored runway 33 vs 15 for departure. Completed new takeoff data and called for taxi and was cleared by ground to taxi to runway 33 via runway 26; with no hold short instructions. I taxied down 26 and I knew that I was not cleared to enter 33 but was unsure where to hold exactly as there is no hold short line painted on runway 26 for runway 33. Began to make a short left turn toward the departure end of 33 and as I was stopping at what looked like a hold short line; was told to stop there as well by ground. We never crossed that line and there was no runway incursion; but after reviewing the airport diagram and company briefing pages; it appeares that was the hold short for 26 coming the other direction. Was cleared to switch to tower and departed without incident. Not sure why we were cleared to taxi on 26 to 33 as there is no published taxiway to get to 33 other than back taxi on 33 which we were not cleared to do. There was no further query from ATC on this event. I think to avoid this problem in the future with runway 33 departures; all taxiing aircraft should be on the taxiway around the terminal which is properly marked with hold short lines.

Original NASA ASRS Text

Title: B737 Captain reports being cleared to taxi via Runway 26 to Runway 33 at BUR but is unsure of which hold line is the correct one for Runway 33. After takeoff it is determined that a runway incursion may have occurred.

Narrative: Just prior to push; new ATIS came out which favored Runway 33 vs 15 for departure. Completed new takeoff data and called for taxi and was cleared by Ground to taxi to Runway 33 via Runway 26; with no hold short instructions. I taxied down 26 and I knew that I was not cleared to enter 33 but was unsure where to hold exactly as there is no hold short line painted on Runway 26 for Runway 33. Began to make a short left turn toward the departure end of 33 and as I was stopping at what looked like a hold short line; was told to stop there as well by Ground. We never crossed that line and there was no runway incursion; but after reviewing the airport diagram and company briefing pages; it appeares that was the hold short for 26 coming the other direction. Was cleared to switch to Tower and departed without incident. Not sure why we were cleared to taxi on 26 to 33 as there is no published taxiway to get to 33 other than back taxi on 33 which we were not cleared to do. There was no further query from ATC on this event. I think to avoid this problem in the future with Runway 33 departures; all taxiing aircraft should be on the taxiway around the terminal which is properly marked with hold short lines.

Data retrieved from NASA's ASRS site 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.

Attributes
ACN	1147320
Time
Date	201401
Local Time Of Day	0601-1200
Place
Locale Reference	BUR.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	Taxi
Person 1
Function	Captain
Experience	Flight Crew Last 90 Days 268
Events
Anomaly	Deviation - Procedural Clearance Ground Incursion Runway

B737 captain reports being cleared to taxi via runway 26 to runway 33 at bur but is unsure of which hold line is the correct one for runway 33. After takeoff it is determined that a runway incursion may have occurred.