Runway incursion. - NASA ASRS

Attributes
ACN	293707
Time
Date	199412
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : gdl
State Reference	FO
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	B727 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	landing other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : second officer
Qualification	pilot : instrument pilot : atp pilot : commercial pilot : flight engineer
Experience	flight time last 90 days : 150 flight time total : 4500 flight time type : 1200
ASRS Report	293707
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : ground critical incursion : runway non adherence : clearance 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:

After landing on runway 28 at gdl, tower issued instructions for clearing the runway and taxi which sounded to our crew like 'use runway 20.' the copilot acknowledged with 'roger.' the captain exited runway 28 at runway 20 (right turn to 020 degrees) and shortly thereafter, tower told us to immediately exit the runway 20. It was then the copilot noticed a light aircraft executing what appeared to be a go around from an approach to runway 20. Apparently, we had been instructed 'not' to use runway 20 for our turnoff. Throughout our approach and landing, tower spoke exclusively in spanish except when speaking to us. This prevented any situational awareness on our part. When english was spoken to us, it was very difficult to understand and with a heavy accent. Contributing to the confusion was the fact that on our 2 previous trips to gdl, we had been directed to taxi via runway 20/02. Lessons learned: 1) don't use a runway as a turnoff if communications are difficult or ambiguous. 2) never simply 'roger' a call involving entering or exiting a runway, but rather, read back the entire clearance.

Original NASA ASRS Text

Title: RWY INCURSION.

Narrative: AFTER LNDG ON RWY 28 AT GDL, TWR ISSUED INSTRUCTIONS FOR CLRING THE RWY AND TAXI WHICH SOUNDED TO OUR CREW LIKE 'USE RWY 20.' THE COPLT ACKNOWLEDGED WITH 'ROGER.' THE CAPT EXITED RWY 28 AT RWY 20 (R TURN TO 020 DEGS) AND SHORTLY THEREAFTER, TWR TOLD US TO IMMEDIATELY EXIT THE RWY 20. IT WAS THEN THE COPLT NOTICED A LIGHT ACFT EXECUTING WHAT APPEARED TO BE A GAR FROM AN APCH TO RWY 20. APPARENTLY, WE HAD BEEN INSTRUCTED 'NOT' TO USE RWY 20 FOR OUR TURNOFF. THROUGHOUT OUR APCH AND LNDG, TWR SPOKE EXCLUSIVELY IN SPANISH EXCEPT WHEN SPEAKING TO US. THIS PREVENTED ANY SITUATIONAL AWARENESS ON OUR PART. WHEN ENGLISH WAS SPOKEN TO US, IT WAS VERY DIFFICULT TO UNDERSTAND AND WITH A HVY ACCENT. CONTRIBUTING TO THE CONFUSION WAS THE FACT THAT ON OUR 2 PREVIOUS TRIPS TO GDL, WE HAD BEEN DIRECTED TO TAXI VIA RWY 20/02. LESSONS LEARNED: 1) DON'T USE A RWY AS A TURNOFF IF COMS ARE DIFFICULT OR AMBIGUOUS. 2) NEVER SIMPLY 'ROGER' A CALL INVOLVING ENTERING OR EXITING A RWY, BUT RATHER, READ BACK THE ENTIRE CLRNC.

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.