B737 taxiing for departure at bur is cleared via runway and then questioned by ATC.

Attributes
ACN	615937
Time
Date	200405
Day	Mon
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : bur.airport
State Reference	CA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi ground : holding
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	615937
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued advisory controller : issued new clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	ATC Human Performance

Narrative:

Pushed back in bur with winds 33 degrees at 5 KTS, runways 33/8/15 in use. Completed checklist and called for taxi. Waited for company jet in front of us to taxi to runway 33. Cleared to taxi to runway 15 and hold short of runway 8. We landed on runway 33, wind velocity was varying and we concurred to request runway 33. Ground cleared us to taxi to runway 33 and hold at second set of hold bars. Another carrier B737 was landing and ground instructed us to hold for them to exit runway 8, then hold at second set of hold bars. The other carrier pulled forward, turned to about 180 degrees on taxi line blocking taxiway to runway 33 and blocking the hold bar. The other carrier did not have a gate and was holding at this position. We were instructed to contact tower. Company jet landed on runway 8 and company was cleared to take off on runway 33. The other carrier had us blocked and was still waiting for a gate. An aircraft was visible lined up on runway 8 and appeared to be several mi from the airport. Tower cleared us to taxi behind the other carrier and taxi to runway 33 and back taxi into position and hold. The other carrier was not moving and we heard no instructions for them. We cleared for traffic on runway 8/26 and began a turn behind the other carrier to runway 33. As we started the turn, the tower controller told us to not taxi onto runway 8/26 and to clear the runway. We had slightly passed over the runway edge line. The other carrier began to move forward and we pulled back onto the yellow taxi line and held short of runway 33. The aircraft that was observed earlier landed on runway 8 and the traffic conflict occurred. When told to clear the runway, we did so and I stated to the tower controller we had been cleared to taxi to runway 33 behind the other carrier. We were cleared to back taxi into position and hold on runway 33. We were cleared for takeoff. On the change to departure call, the tower controller apologized for the confusion that had been caused and we also apologized.

Original NASA ASRS Text

Title: B737 TAXIING FOR DEP AT BUR IS CLRED VIA RWY AND THEN QUESTIONED BY ATC.

Narrative: PUSHED BACK IN BUR WITH WINDS 33 DEGS AT 5 KTS, RWYS 33/8/15 IN USE. COMPLETED CHKLIST AND CALLED FOR TAXI. WAITED FOR COMPANY JET IN FRONT OF US TO TAXI TO RWY 33. CLRED TO TAXI TO RWY 15 AND HOLD SHORT OF RWY 8. WE LANDED ON RWY 33, WIND VELOCITY WAS VARYING AND WE CONCURRED TO REQUEST RWY 33. GND CLRED US TO TAXI TO RWY 33 AND HOLD AT SECOND SET OF HOLD BARS. ANOTHER CARRIER B737 WAS LNDG AND GND INSTRUCTED US TO HOLD FOR THEM TO EXIT RWY 8, THEN HOLD AT SECOND SET OF HOLD BARS. THE OTHER CARRIER PULLED FORWARD, TURNED TO ABOUT 180 DEGS ON TAXI LINE BLOCKING TXWY TO RWY 33 AND BLOCKING THE HOLD BAR. THE OTHER CARRIER DID NOT HAVE A GATE AND WAS HOLDING AT THIS POS. WE WERE INSTRUCTED TO CONTACT TWR. COMPANY JET LANDED ON RWY 8 AND COMPANY WAS CLRED TO TAKE OFF ON RWY 33. THE OTHER CARRIER HAD US BLOCKED AND WAS STILL WAITING FOR A GATE. AN ACFT WAS VISIBLE LINED UP ON RWY 8 AND APPEARED TO BE SEVERAL MI FROM THE ARPT. TWR CLRED US TO TAXI BEHIND THE OTHER CARRIER AND TAXI TO RWY 33 AND BACK TAXI INTO POS AND HOLD. THE OTHER CARRIER WAS NOT MOVING AND WE HEARD NO INSTRUCTIONS FOR THEM. WE CLRED FOR TFC ON RWY 8/26 AND BEGAN A TURN BEHIND THE OTHER CARRIER TO RWY 33. AS WE STARTED THE TURN, THE TWR CTLR TOLD US TO NOT TAXI ONTO RWY 8/26 AND TO CLR THE RWY. WE HAD SLIGHTLY PASSED OVER THE RWY EDGE LINE. THE OTHER CARRIER BEGAN TO MOVE FORWARD AND WE PULLED BACK ONTO THE YELLOW TAXI LINE AND HELD SHORT OF RWY 33. THE ACFT THAT WAS OBSERVED EARLIER LANDED ON RWY 8 AND THE TFC CONFLICT OCCURRED. WHEN TOLD TO CLR THE RWY, WE DID SO AND I STATED TO THE TWR CTLR WE HAD BEEN CLRED TO TAXI TO RWY 33 BEHIND THE OTHER CARRIER. WE WERE CLRED TO BACK TAXI INTO POS AND HOLD ON RWY 33. WE WERE CLRED FOR TKOF. ON THE CHANGE TO DEP CALL, THE TWR CTLR APOLOGIZED FOR THE CONFUSION THAT HAD BEEN CAUSED AND WE ALSO APOLOGIZED.

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.