BE99 flight crew crossed active runway during taxi out without clearance.

Attributes
ACN	542053
Time
Date	200203
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : bil.airport
State Reference	MT
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air taxi
Make Model Name	Airliner 99
Operating Under FAR Part	Part 135
Flight Phase	ground : taxi
Flight Plan	VFR
Person 1
Affiliation	company : air taxi
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : commercial pilot : instrument
Experience	flight time last 90 days : 32 flight time total : 1394 flight time type : 87
ASRS Report	542053
Person 2
Affiliation	company : air taxi
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial pilot : multi engine
Experience	flight time last 90 days : 225 flight time total : 1020 flight time type : 800
ASRS Report	542855
Events
Anomaly	incursion : runway non adherence : far non adherence : clearance non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On mar/tue/02 I was taxiing from the north tanker base at bil. As I approached the end of the ramp apron, my first officer asked for taxi clearance. The ground controller acknowledged 'aircraft X cleared to taxi runway 28R.' there was no hold short instruction so we thought that we were cleared to taxi via taxiway B and across runway 28 and continue to the hold short line of runway 28R on taxiway a. The controller advised us that we were not cleared to cross runway 28R. Supplemental information from acn 542855: after doing a runup by hangar, I called bil ground and identified myself and where we were and told them we were ready for takeoff. I told him we were sorry for the miscom and when I told him when I said ready for takeoff and he responded with taxi to runway 28R I assumed he wanted to get us to the approach end to take off. I should have confirmed with ground control that we were cleared all the way to the approach end before proceeding across the runway. We were engaged in a conversation and that may have contributed to the situation.

Original NASA ASRS Text

Title: BE99 FLC CROSSED ACTIVE RWY DURING TAXI OUT WITHOUT CLRNC.

Narrative: ON MAR/TUE/02 I WAS TAXIING FROM THE N TANKER BASE AT BIL. AS I APCHED THE END OF THE RAMP APRON, MY FO ASKED FOR TAXI CLRNC. THE GND CTLR ACKNOWLEDGED 'ACFT X CLRED TO TAXI RWY 28R.' THERE WAS NO HOLD SHORT INSTRUCTION SO WE THOUGHT THAT WE WERE CLRED TO TAXI VIA TXWY B AND ACROSS RWY 28 AND CONTINUE TO THE HOLD SHORT LINE OF RWY 28R ON TXWY A. THE CTLR ADVISED US THAT WE WERE NOT CLRED TO CROSS RWY 28R. SUPPLEMENTAL INFO FROM ACN 542855: AFTER DOING A RUNUP BY HANGAR, I CALLED BIL GND AND IDENTIFIED MYSELF AND WHERE WE WERE AND TOLD THEM WE WERE READY FOR TKOF. I TOLD HIM WE WERE SORRY FOR THE MISCOM AND WHEN I TOLD HIM WHEN I SAID READY FOR TKOF AND HE RESPONDED WITH TAXI TO RWY 28R I ASSUMED HE WANTED TO GET US TO THE APCH END TO TAKE OFF. I SHOULD HAVE CONFIRMED WITH GND CTL THAT WE WERE CLRED ALL THE WAY TO THE APCH END BEFORE PROCEEDING ACROSS THE RWY. WE WERE ENGAGED IN A CONVERSATION AND THAT MAY HAVE CONTRIBUTED TO THE SIT.

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.