Date: 201601
Local time of day: 1801-2400
Location: BUR.Airport, CA
Flight conditions: VMC
Light: Night
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower BUR
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued New Clearance
Contributing factors: Chart Or Publication; Human Factors
Primary problem: Chart Or Publication

Narrative: We received a wheels up time from Ground which created a time compression threat. During pushback from [our] gate; Ground informed us that they were switching the runway configuration from Runway 15 to Runway 33. After pushback and engine start; we ran the after start checklist. We did not rush. With the parking brake set; we checked performance calculations; programmed the FMC; and briefed the departure waypoints; single engine procedure; 10-9 page; taxi procedures. During my briefing I mentioned that there used to be a taxi restriction to Runway 33; but it looked like that had been fixed as there was nothing on the 10-9 page (no hotspots). 'There are Yellow parallel strips between our ramp area and the runway. These boundary markings separate the movement (runway) and non-movement (ramp) areas. Use extreme caution while taxiing so as to remain clear of any obstructions as well as in the non-movement until cleared by ATC to enter the movement area.'The First Officer stated that he had never taxied to Runway 33. I noted his statement and after review of the departure procedures we requested taxi. Ground Control cleared us to 'Taxi to Runway 33 via the ramp.' The clearance was read back. I repeated the taxi route. We started our taxi west on C. We noted the 8/26 hold short line and crossed it. (Now that I look back; I believe we should have received a clearance to cross 8/26 hold short line and maybe the reason we did not give way to the 15/33 hold short line.) We then continued west on C. We both were heads up looking for the obstacles. We were both verbalizing our position to each other. [Passing a] gate I was looking out for the baggage carts parked there. We noted the hold short line for 15/33 for what we believed was to hold short to continue straight on Taxiway C. We continued on the ramp taxi line making sure we did not cross the yellow parallel strips between the ramp area and the runway. We both believed we were still on the ramp.As we switched to Tower frequency; Tower was calling us. The Controller very politely stated that we did not have clearance past the non-standard 15/33 hold short line and it was a 'runway violation'. He also made a statement that it was a hotspot and they were trying to get it fixed. We apologize and stated that we thought we were still on the ramp. (In my head I believed that the ramp taxi line did not cross the 15/33 hold short line and turned before. It was until I looked at Google Maps that I was incorrect.) There was no other aircraft involved in this incident. The Controller cleared us to 'line up and wait'. We were cleared for takeoff. We continued without further incident.It may seem normal to ATC for a Runway 33 departures; but Runway 33 departures are a very rare operation. (This is the second time I have departed Runway 33 in 15 years.) I feel that the Ground Controller's taxi instructions could have been more concise on holding short of the non-standard hold line and not use the vague clearance of 'Taxi via the ramp.' There are no yellow wig-wag lights at the 15/33 hold short line. There is no Hot Spot or depiction of a non-standard hold short line on the 10-9 pages. (There is a depiction of nonstandard ILS hold short on D Taxiway.) Next time I will question any hold short line.


Second narrative: During pushback we were advised that our takeoff runway changed to Runway 33. I immediately stated that this would be the first time for me taking off on Runway 33 in Burbank. Pushback; engine start; flows; and checklists were all accomplished uneventfully. We double checked takeoff performance calculations and accomplished the departure checklist before initiating our taxi call and moving the aircraft. The only change to the original plan was a now two engine taxi because of the shorter taxi length. We also had a flow time to meet.I believe there was no other traffic involved in our entire event. Nevertheless; the taxi instructions from Ground Control were to taxi to Runway 33 via the ramp. We did remember that there used to be special procedures in reference to the hold short lines. However; we could not find anything on the 10-9 pages or the local publications. Therefore; we communicated; to each other; to stay on the ramp and not leave the non-movement area. However; after turning south around Terminal B and switching to Tower frequency; the Controller kindly reminded us to not taxi across the 33 hold short line in the future.The Controller was very friendly about it and we apologized genuinely. However; at this point we still did not understand what we did wrong as we stayed within the non-movement area. We truly believed the unlit hold short line was only there if you wanted to cross Runway 33 onto Taxiway C. To us the taxi instructions were very vague and almost not sufficient for the non-standard operation at Burbank; especially for Runway 33. After the Tower said something; we discussed taxiing across the 8/26 hold short line as well without clearance. We truly did not think that they would apply to us while staying in the non-movement area.Initially; I thought the taxi instructions should be more detailed or more specific for this non-standard situation. However; after finally finding the safety alert page; hidden as a link; I have to say that this could be the root cause. Especially at night; when the red circle with the exclamation mark turns light blue; my attention was not there were it should have been. Nevertheless; if in doubt; we should have asked; but we were so vigilant to stay ramp-side and not taxi into anything. We were not aware of doing anything wrong. The only question mark we had; was the fact that we knew there used to be something but we couldn't find it on the local procedures nor on the 10-9 pages (e.g. hot spots); so we simply thought; they must have gotten away with it.


Synopsis: During night-time taxi to Runway 33 at BUR; crew crossed the hold short line. The Airport Diagram (BUR 10-9) was changed just four days after this incident to add a Hot Spot and related note for this spot on the airport.