B737. Flight crew misinterpreted ground controller taxi routing clearance. Controller cleared them to runway 35 via taxiway east and H6 to cross runway 34R. Thinking they were cleared via the most direct route after H6, they taxied down runway 14-32 to runway 35. Reporter says that is standard at this airport.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	346962
Time
Date	199609
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : slc
State Reference	UT
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	ground other : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : atp pilot : instrument
Experience	flight time last 90 days : 135 flight time total : 14500 flight time type : 9400
ASRS Report	346962
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : instrument
Experience	flight time last 90 days : 200 flight time total : 5000 flight time type : 2000
ASRS Report	346580
Events
Anomaly	non adherence : published procedure non adherence : clearance non adherence : far other anomaly other other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Upon calling for taxi instructions from ramp in slc, ground control cleared us 'to runway 35 via taxiway east, H6, cross runway 34R.' after crossing runway 34R at H6 we continued toward runway 35 via back taxi on runway 32 (a normal taxi route at slc). At that time we switched to tower 118.3 and tower said we were not cleared onto runway 32. We replied that we had been cleared to runway 35 with no 'hold short' instructions. Both the first officer and I heard the clearance as above. There must have been a communication breakdown between the ground controller and the tower. We asked if we had caused a conflict and the tower said no.

Original NASA ASRS Text

Title: B737. FLC MISINTERPRETED GND CTLR TAXI ROUTING CLRNC. CTLR CLRED THEM TO RWY 35 VIA TXWY E AND H6 TO CROSS RWY 34R. THINKING THEY WERE CLRED VIA THE MOST DIRECT RTE AFTER H6, THEY TAXIED DOWN RWY 14-32 TO RWY 35. RPTR SAYS THAT IS STANDARD AT THIS ARPT.

Narrative: UPON CALLING FOR TAXI INSTRUCTIONS FROM RAMP IN SLC, GND CTL CLRED US 'TO RWY 35 VIA TXWY E, H6, CROSS RWY 34R.' AFTER XING RWY 34R AT H6 WE CONTINUED TOWARD RWY 35 VIA BACK TAXI ON RWY 32 (A NORMAL TAXI RTE AT SLC). AT THAT TIME WE SWITCHED TO TWR 118.3 AND TWR SAID WE WERE NOT CLRED ONTO RWY 32. WE REPLIED THAT WE HAD BEEN CLRED TO RWY 35 WITH NO 'HOLD SHORT' INSTRUCTIONS. BOTH THE FO AND I HEARD THE CLRNC AS ABOVE. THERE MUST HAVE BEEN A COM BREAKDOWN BTWN THE GND CTLR AND THE TWR. WE ASKED IF WE HAD CAUSED A CONFLICT AND THE TWR SAID NO.

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.