<< >> NASA ASRS Report 292903, December 1994

Runway incursion.

Attributes
ACN	292903
Time
Date	199412
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : 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	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	ground other : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : atp pilot : commercial
Experience	flight time last 90 days : 190 flight time total : 20000 flight time type : 12000
ASRS Report	292903
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

After touchdown and during rollout on runway 28 at gdl airport, mexico, tower issued instructions for clearing the runway/taxiway. It sounded to me and the rest of the crew that they wanted us to use runway 20. The copilot acknowledged the call with a 'roger.' I exited runway 28 onto runway 2/20 heading 020 degrees. Tower called us shortly after telling us to exit runway 20. We exited at taxiway a. As we were exiting the runway we saw a small aircraft on what appeared to be a missed approach. Throughout approach and landing, tower issued instructions in spanish except when communicating with us. The english that was spoken to us was very rapid and very broken with a heavy spanish accent, making communications and situational awareness very difficult. Contributing factors to the incursion were: 1) language barriers. 2) we had flown into gdl airport for the last 3 weeks and each time had been instructed to use runway 20 to exit runway 28. To prevent future problems: 1) I will not use a runway as a turnoff point where language barriers exist. 2) read back all clrncs, even during rollout.

Related reports:

• Runway incursion small aircraft X crossed hold line with atx...
• Runway incursion at gon, ct, causing a go around.
• PA32 pilot was accused of a runway incursion when he taxied ...
• Beech 1900 runway incursion. First officer distracted doing ...
• Runway incursion. Unauthorized runway entry.
• Runway incursion by a military C40 (B737-700) during a night...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: RWY INCURSION.

Narrative: AFTER TOUCHDOWN AND DURING ROLLOUT ON RWY 28 AT GDL ARPT, MEXICO, TWR ISSUED INSTRUCTIONS FOR CLRING THE RWY/TXWY. IT SOUNDED TO ME AND THE REST OF THE CREW THAT THEY WANTED US TO USE RWY 20. THE COPLT ACKNOWLEDGED THE CALL WITH A 'ROGER.' I EXITED RWY 28 ONTO RWY 2/20 HDG 020 DEGS. TWR CALLED US SHORTLY AFTER TELLING US TO EXIT RWY 20. WE EXITED AT TXWY A. AS WE WERE EXITING THE RWY WE SAW A SMALL ACFT ON WHAT APPEARED TO BE A MISSED APCH. THROUGHOUT APCH AND LNDG, TWR ISSUED INSTRUCTIONS IN SPANISH EXCEPT WHEN COMMUNICATING WITH US. THE ENGLISH THAT WAS SPOKEN TO US WAS VERY RAPID AND VERY BROKEN WITH A HVY SPANISH ACCENT, MAKING COMS AND SITUATIONAL AWARENESS VERY DIFFICULT. CONTRIBUTING FACTORS TO THE INCURSION WERE: 1) LANGUAGE BARRIERS. 2) WE HAD FLOWN INTO GDL ARPT FOR THE LAST 3 WKS AND EACH TIME HAD BEEN INSTRUCTED TO USE RWY 20 TO EXIT RWY 28. TO PREVENT FUTURE PROBS: 1) I WILL NOT USE A RWY AS A TURNOFF POINT WHERE LANGUAGE BARRIERS EXIST. 2) READ BACK ALL CLRNCS, EVEN DURING ROLLOUT.

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.