MasAir Flight MMA6853
Boeing 767-338 767-300ER · Incident: fire/smoke (non-impact) during initial climb
From Los Angeles International Airport (LAX) to Mexico City Benito Juárez International Airport (MMMX)
Event
- NTSB case
- ENG21LA013
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Unknown
Boeing 767-338 767-300ER
- Aircraft type
- Boeing 767
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N363CM
- Operator
- MasAir
- Onboard fatalities
- Unknown
- Route
- From Los Angeles International Airport (LAX), Los Angeles, CATo Mexico City Benito Juárez International Airport (MMMX), Mexico City
- Aircraft age
- About 31 years (built 1990)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 129: Foreign
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Initial climb
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Fire/smoke (non-impact)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Aircraft › Aircraft power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The low pressure turbine stage 5 nozzle segment No. 3 was the only item identified that had any indication of primary fatigue, and no damage or distress was found upstream (forward) of the low pressure turbine that would have accounted for the damage observed throughout the low pressure turbine, the most likely initiating event was the fatigue fracture and liberating of the two missing stage 5 nozzle airfoils. The low pressure turbine stage 5 blades are located directly downstream (aft) of the stage 5 nozzle; thus, the loss of the two stage 5 nozzle airfoils would have traveled downstream in the airflow direction contacting and damaging the stage 5 blades resulting in stage 5 blade airfoil fractures. The damage inflicted on the stage 5 blades by the ingestion of the stage 5 nozzle airfoils would have created an imbalance in the low pressure turbine rotor. This low pressure turbine imbalance was confirmed by the flight data recorder data. Shortly after takeoff during climb the low pressure turbine vibration started to climb and within a few seconds reached the value of 5 cockpit units which is the maximum value that can be recorded; a cockpit unit is a dimensionless scaler unit, a magnitude with no unit of measure attached.
GE performed a rotor imbalance and deflection analysis to determine the amount of radial deflection each stage of the low pressure turbine would be anticipated to experience based on the condition of the hardware as documented during the engine exam. Since the exact condition of the low pressure turbine hardware for any point in time during the event was not known the analysis does not provide the exact vibration levels or deflections at the time of the event or during the engine deceleration but instead a general assessment. The results of the analysis showed that the amount of low pressure turbine rotor expected radial deflection was several times greater than the nominal running blade radial clearances at takeoff for each of the low pressure turbine rotor stages. This is consistent with all the observed gouging and heavy wear down to the backing strip of the honeycomb on the blade outer shroud segments and the accompanying loss of blade tips for each stage of the low pressure turbine. The analysis also predicted that the low pressure turbine stage 5 would be the stage that experienced the most deflection and that the deflection would be the greater not at takeoff/climb low pressure turbine rotor speed but as it decelerates from the accumulation of damage and the pilot’s action to shut down the engine.
This would indicate that the overall damage observed throughout the low pressure turbine was initially caused by the loss of the low pressure turbine stage 5 nozzle airfoils due to fatigue and impacting the stage 5 blades fracturing them creating imbalance and deflection in the low pressure turbine rotor. The low pressure turbine rotor imbalance and deflection progressively increased due to the accumulation of additional stage 5 blade damage and the accompanying loss of rotor speed that eventually led the entire low pressure turbine rotor to lose radial blade clearance. This loss of radial blade clearance throughout the low pressure turbine resulted in blades contacting static structure, fracturing, and causing additional downstream damage.
Since the flight data recorder does not record vibration levels or amplitudes above 5 cockpit units, any vibration values higher than 5 cockpit units is capped to 5 cockpit units, the exact vibration the right engine experienced was unknown; however, the results of the GE imbalance and deflection analysis indicated that the loads experience by the right engine would have been sufficient to fracture the oil supply tube and the turbine exhaust sleeve. Since neither of these items showed signs of a pre-existing anomalies, their failures were as a resulted of the high vibrational loads from the right engine during the failure sequence. The low-grade thermal/fire damage observed on the inside of the right engine core cowls and thrust reverser halves and on the outside of the right engine was due to the oil from the fractured oil supply line contacting hot engine cases and smoldering and igniting. The fuel system, forward of the left and right fuel manifold where the thermal/fire damage was most pronounced, was leak checked and no leaks were found; thus, the only source of a flammable fluid would have been the fractured oil supply line.
Probable cause
The fatigue fracture and liberation of two airfoils from a low pressure turbine stage 5 nozzle segment that impacted and damaged the downstream low pressure stage 5 blades creating an initial imbalance load in the engine’s low pressure turbine rotor sufficient to allow all the low pressure turbine blades to lose radial blade clearance, contact static structure, and to fracture transversely across the airfoil. The progressive failure of the low pressure rotor caused an increasingly imbalanced load that eventually resulted in the fracture of the oil supply tube that allowed oil to contact hot engine parts and smolder and ignite resulting in the undercowl fire.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ENG21LA013
- Event ID
- 20210130102575
- Case number
- ENG21LA013
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: c03ed6c327af48e06c525bfc379c01fc12b4e175bbea51a9134ccab4105b2d70; retrieved 2026-09-16T13:35:11.297Z.