A taxiing B737-300 PIC misses his intended taxiway and has to use another one at bos, ma.

Attributes
ACN	449920
Time
Date	199909
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bos.airport
State Reference	MA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi landing : roll
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : cfi pilot : commercial pilot : atp pilot : multi engine pilot : instrument
Experience	flight time last 90 days : 190 flight time total : 20412 flight time type : 3011
ASRS Report	449920
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : multi engine
Events
Anomaly	incursion : taxiway non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	flight crew : returned to intended or assigned course flight crew : became reoriented
Supplementary
Problem Areas	Flight Crew Human Performance Environmental Factor ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were asked to expedite clearing the active runway after landing. In the same or next mouthful, the controller then cleared us to taxi across an intersecting runway. We were still clearing the runway, so I asked for a repeat of the instructions. We confirmed cleared to cross, then the ground controller gave us cleared to the gate via txwys K, C, and a. I inadvertently missed taxiway C and transitioned to taxiway a at taxiway east. Controller didn't mention the deviation. Factors leading to the deviation: 1) we were getting over a busy landing and initial taxi clearance after landing. 2) taxi instructions were slightly out of the ordinary. 3) if the instructions had included the words 'transition to the inner' or 'transition to taxiway a at taxiway C,' it would have made a deviation less likely. 4) bottom line: it was still our fault. To avoid taxi deviations: go slow, use the taxi diagram, think about the route and the intention of the clearance, and use the first officer to help insure compliance.

Original NASA ASRS Text

Title: A TAXIING B737-300 PIC MISSES HIS INTENDED TXWY AND HAS TO USE ANOTHER ONE AT BOS, MA.

Narrative: WE WERE ASKED TO EXPEDITE CLRING THE ACTIVE RWY AFTER LNDG. IN THE SAME OR NEXT MOUTHFUL, THE CTLR THEN CLRED US TO TAXI ACROSS AN INTERSECTING RWY. WE WERE STILL CLRING THE RWY, SO I ASKED FOR A REPEAT OF THE INSTRUCTIONS. WE CONFIRMED CLRED TO CROSS, THEN THE GND CTLR GAVE US CLRED TO THE GATE VIA TXWYS K, C, AND A. I INADVERTENTLY MISSED TXWY C AND TRANSITIONED TO TXWY A AT TXWY E. CTLR DIDN'T MENTION THE DEV. FACTORS LEADING TO THE DEV: 1) WE WERE GETTING OVER A BUSY LNDG AND INITIAL TAXI CLRNC AFTER LNDG. 2) TAXI INSTRUCTIONS WERE SLIGHTLY OUT OF THE ORDINARY. 3) IF THE INSTRUCTIONS HAD INCLUDED THE WORDS 'TRANSITION TO THE INNER' OR 'TRANSITION TO TXWY A AT TXWY C,' IT WOULD HAVE MADE A DEV LESS LIKELY. 4) BOTTOM LINE: IT WAS STILL OUR FAULT. TO AVOID TAXI DEVS: GO SLOW, USE THE TAXI DIAGRAM, THINK ABOUT THE RTE AND THE INTENTION OF THE CLRNC, AND USE THE FO TO HELP INSURE COMPLIANCE.

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.