Runway incursion creates a potential conflict between a departure B737-800 and a taxiing air carrier crossing the active runway at the direction of local controller at MMMX, first officer.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	613473
Time
Date	200404
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : mmmx.airport
State Reference	FO
Altitude	agl single value : 0
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-800
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi ground : takeoff roll
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : mmmx.tower
Operator	common carrier : air carrier
Make Model Name	Airbus Industrie Undifferentiated or Other Model
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
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
ASRS Report	613473
Events
Anomaly	conflict : ground critical incursion : runway non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	controller : issued alert controller : issued new clearance controller : separated traffic flight crew : rejected takeoff
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance Airport Environmental Factor
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

We were cleared to back taxi from taxiway B9 into position and hold for runway 23R at MMMX. During the back taxi, tower cleared us for takeoff. On the takeoff roll at approximately 80 KTS, tower directed us to abort. After clearing the runway, we inquired into the reason for the abort call and was told tower had inadvertently cleared a flight to cross runway 23R. We did not see another aircraft on the runway. My biggest concern is that from the time we pushed back until cleared for takeoff, the only tower xmissions in english were to us. All others were in spanish. Being unable to catch potential conflicts by monitoring other radio xmissions is a big disadvantage in a foreign country. Fortunately, tower caught this one. Another problem was the time from 'cleared for takeoff' clearance and the start of the takeoff roll, which was 1 1/2 mins due to the back taxi. Aircraft landing on the outside runway 23L and waiting to cross runway 23R may have contributed to this situation.

Original NASA ASRS Text

Title: RWY INCURSION CREATES A POTENTIAL CONFLICT BTWN A DEP B737-800 AND A TAXIING ACR XING THE ACTIVE RWY AT THE DIRECTION OF LCL CTLR AT MMMX, FO.

Narrative: WE WERE CLRED TO BACK TAXI FROM TXWY B9 INTO POS AND HOLD FOR RWY 23R AT MMMX. DURING THE BACK TAXI, TWR CLRED US FOR TKOF. ON THE TKOF ROLL AT APPROX 80 KTS, TWR DIRECTED US TO ABORT. AFTER CLRING THE RWY, WE INQUIRED INTO THE REASON FOR THE ABORT CALL AND WAS TOLD TWR HAD INADVERTENTLY CLRED A FLT TO CROSS RWY 23R. WE DID NOT SEE ANOTHER ACFT ON THE RWY. MY BIGGEST CONCERN IS THAT FROM THE TIME WE PUSHED BACK UNTIL CLRED FOR TKOF, THE ONLY TWR XMISSIONS IN ENGLISH WERE TO US. ALL OTHERS WERE IN SPANISH. BEING UNABLE TO CATCH POTENTIAL CONFLICTS BY MONITORING OTHER RADIO XMISSIONS IS A BIG DISADVANTAGE IN A FOREIGN COUNTRY. FORTUNATELY, TWR CAUGHT THIS ONE. ANOTHER PROB WAS THE TIME FROM 'CLRED FOR TKOF' CLRNC AND THE START OF THE TKOF ROLL, WHICH WAS 1 1/2 MINS DUE TO THE BACK TAXI. ACFT LNDG ON THE OUTSIDE RWY 23L AND WAITING TO CROSS RWY 23R MAY HAVE CONTRIBUTED TO THIS SIT.

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.