SF340 flight crew failed to follow the taxi route instructed by tower controller to parking resultin...

Attributes
ACN	516737
Time
Date	200106
Day	Wed
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : buf.airport
State Reference	NY
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	SF 340B
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : atp
Experience	flight time last 90 days : 270 flight time total : 5500 flight time type : 1800
ASRS Report	516737
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	incursion : runway non adherence : clearance
Independent Detector	other controllera
Resolutory Action	controller : issued alert controller : issued new clearance
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

After landing on runway 32, there was a miscom regarding our taxi instructions. I believe tower's intent was for us to back taxi on runway 32, cross runway 5, continue on runway 32, then make a right turn onto taxiway K and proceed to the ramp. However, what we believe was said was something similar to back taxi on runway 32, cross runway 5, right to taxiway K and proceed to ramp. Which we understood to mean, back taxi on runway 32, right on runway 5 to taxiway K. First officer read back 'back taxi runway 32, right on runway 5 to taxiway K.' tower did not make any corrections. We proceeded to back taxi on runway 32. While trying to check our airport diagrams, we got to runway 5 and made the right turn on runway 5. I stopped the aircraft, short of taxiway east. I wanted to query the tower because, looking at our diagrams, this was not the correct way to taxiway K. At the same time, tower contacted us to exit runway 5 on taxiway east and take taxiway a to taxiway K -- that runway 5 does not lead to taxiway K. Runway 5 was closed to aircraft less than 40000 pounds (per the ATIS) and we did have permission to cross runway 5.

Original NASA ASRS Text

Title: SF340 FLC FAILED TO FOLLOW THE TAXI RTE INSTRUCTED BY TWR CTLR TO PARKING RESULTING IN TAXIING ON AN ACTIVE RWY WITHOUT CLRNC.

Narrative: AFTER LNDG ON RWY 32, THERE WAS A MISCOM REGARDING OUR TAXI INSTRUCTIONS. I BELIEVE TWR'S INTENT WAS FOR US TO BACK TAXI ON RWY 32, CROSS RWY 5, CONTINUE ON RWY 32, THEN MAKE A R TURN ONTO TXWY K AND PROCEED TO THE RAMP. HOWEVER, WHAT WE BELIEVE WAS SAID WAS SOMETHING SIMILAR TO BACK TAXI ON RWY 32, CROSS RWY 5, R TO TXWY K AND PROCEED TO RAMP. WHICH WE UNDERSTOOD TO MEAN, BACK TAXI ON RWY 32, R ON RWY 5 TO TXWY K. FO READ BACK 'BACK TAXI RWY 32, R ON RWY 5 TO TXWY K.' TWR DID NOT MAKE ANY CORRECTIONS. WE PROCEEDED TO BACK TAXI ON RWY 32. WHILE TRYING TO CHK OUR ARPT DIAGRAMS, WE GOT TO RWY 5 AND MADE THE R TURN ON RWY 5. I STOPPED THE ACFT, SHORT OF TXWY E. I WANTED TO QUERY THE TWR BECAUSE, LOOKING AT OUR DIAGRAMS, THIS WAS NOT THE CORRECT WAY TO TXWY K. AT THE SAME TIME, TWR CONTACTED US TO EXIT RWY 5 ON TXWY E AND TAKE TXWY A TO TXWY K -- THAT RWY 5 DOES NOT LEAD TO TXWY K. RWY 5 WAS CLOSED TO ACFT LESS THAN 40000 LBS (PER THE ATIS) AND WE DID HAVE PERMISSION TO CROSS RWY 5.

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.

SF340 flight crew failed to follow the taxi route instructed by tower controller to parking resulting in taxiing on an active runway without clearance.