BE99 PIC taxied into position on wrong runway.

Attributes
ACN	574044
Time
Date	200302
Day	Sat
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : pih.airport
State Reference	ID
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Operator	common carrier : air taxi
Make Model Name	King Air 100 A/B
Operating Under FAR Part	Part 135
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air taxi
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : cfi pilot : atp
Experience	flight time last 90 days : 140 flight time total : 2940 flight time type : 130
ASRS Report	574044
Person 2
Affiliation	government : faa
Function	controller : ground
Events
Anomaly	incursion : runway non adherence : clearance non adherence : far
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Instructed into position and hold on runway 3. Taxied on to non-active runway 34 instead. Tower pointed out my mistake, then cleared me to take off on runway 34, which I did. There was no other traffic in the vicinity, and no conflict. Major factor was unfamiliarity with airport. I had never taken off from runway 3 before. I was rushed, and neglected to consult airport diagram prior to taxiing. Runway layout is somewhat unique, with access to runway 3 only from a small, nondescript crossing taxiway. I mistakenly followed the main parallel taxiway all the way to the end, and then found myself with access to only one runway, which turned out to be runway 34.

Original NASA ASRS Text

Title: BE99 PIC TAXIED INTO POS ON WRONG RWY.

Narrative: INSTRUCTED INTO POS AND HOLD ON RWY 3. TAXIED ON TO NON-ACTIVE RWY 34 INSTEAD. TWR POINTED OUT MY MISTAKE, THEN CLRED ME TO TAKE OFF ON RWY 34, WHICH I DID. THERE WAS NO OTHER TFC IN THE VICINITY, AND NO CONFLICT. MAJOR FACTOR WAS UNFAMILIARITY WITH ARPT. I HAD NEVER TAKEN OFF FROM RWY 3 BEFORE. I WAS RUSHED, AND NEGLECTED TO CONSULT ARPT DIAGRAM PRIOR TO TAXIING. RWY LAYOUT IS SOMEWHAT UNIQUE, WITH ACCESS TO RWY 3 ONLY FROM A SMALL, NONDESCRIPT XING TXWY. I MISTAKENLY FOLLOWED THE MAIN PARALLEL TXWY ALL THE WAY TO THE END, AND THEN FOUND MYSELF WITH ACCESS TO ONLY ONE RWY, WHICH TURNED OUT TO BE RWY 34.

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.