Dispatch Limitations: Master Minimum Equipment List (MMEL) vs. Operator MEL

You are at the gate. The captain is tapping his watch, operations is calling on the radio asking for a departure time, and the aircraft has a hard fault on a primary system. Your job isn’t always to fix the aircraft before pushback—sometimes, your job is to determine if the aircraft can legally and safely fly broken.

The Minimum Equipment List (MEL) is the most powerful tool in your dispatch arsenal. However, misinterpreting an MEL deferral doesn’t just delay flights; it creates aerodynamic penalties, compromises system redundancy, and can lead to catastrophic accidents.

For AME students and line mechanics, understanding the legal hierarchy between the OEM’s MMEL and the airline’s Operator MEL is critical. Here is the hangar-floor reality of dispatching with inoperative equipment.

Prerequisite Knowledge

Before you open the manual, you must understand the regulatory foundation of dispatch limits.

• The Baseline Rule: Under aviation law (like 14 CFR 91.213), an aircraft with broken equipment is legally unairworthy unless that specific equipment is listed in an approved MEL. If a component is broken and it is NOT in the MEL, the aircraft does not fly. Period.
• Regulatory Links:
  • FAA Dynamic Regulatory System (DRS) – MMELs
  • EASA Operational Suitability Data (OSD) – MMEL

The Regulatory Hierarchy: Who Writes the Rules?

There is a strict chain of command when it comes to what can be deferred on the flightline.

The MMEL (Master Minimum Equipment List)

The MMEL is authored by the aircraft manufacturer (OEM) like Boeing or Airbus, and it is approved by the regulatory authority (FAA or EASA) during the aircraft’s initial type certification. It is the absolute baseline. It lists every piece of equipment that can safely be inoperative under specific conditions.

The Operator MEL

An airline cannot dispatch using the MMEL. The airline must write its own Operator MEL, which is customized to its specific routes, operating environment, and cabin configuration. This document is then approved by their local National Aviation Authority (NAA).

The Golden Rule of the MEL: The Operator MEL can be more restrictive than the MMEL, but it can never be less restrictive. Example: If the Airbus MMEL allows a 10-day deferral for a specific pack valve, but the airline operates strictly in the Middle East during summer, their Operator MEL might restrict that deferral to 3 days.

Navigating the MEL Structure

When you open the MEL on your tough-pad, you are looking at a standardized four-column format. You must read every single word.

The Repair Intervals (Categories)

Every defect operates on a ticking clock. The moment you sign the deferral in the Aircraft Technical Logbook (ATL), the countdown begins.

(M) and (O) Procedures

The remarks column will dictate exactly what must happen before the aircraft can fly.

• (M) Maintenance Procedure: A specific mechanical action you must perform. (e.g., physically capping a hydraulic line, locking a valve, pulling and collaring a circuit breaker).
• (O) Operational Procedure: An action the flight crew must take. (e.g., operating at a lower altitude, adjusting takeoff weight, or running a specific checklist).

WARNING: LEGAL LIABILITY. If an MEL specifies an (M) procedure, it is maintenance data. You must physically complete the procedure and sign for it in the ATL. You cannot verbally ask the flight crew to pull a circuit breaker and consider the (M) procedure complete.

Fleet Granularity: Mechanical vs. Automated Redundancy

The logic of a deferral shifts dramatically depending on the generation of the aircraft you are dispatching.

Legacy Mechanical (Boeing 737NG)

On a traditional mechanical aircraft, an MEL deferral often requires heavy (M) procedures. For example, deferring a 737 Thrust Reverser requires you to physically access the engine, install a lockout pin, and safety-wire the directional control valve. You are manually securing the mechanical system.

Modern Fly-By-Wire (Airbus A320neo)

On highly automated aircraft, the MEL heavily leverages software redundancy. Deferring a system often involves navigating the Electronic Centralized Aircraft Monitor (ECAM) and resetting computer channels. However, this automation creates complex interdependencies. A single failed sensor deferred in the MEL might automatically downgrade the aircraft’s autoland capabilities from CAT III to CAT I.

CAUTION: Always check the operational penalties. Deferring an anti-skid system or a thrust reverser will impose severe takeoff weight penalties. If you defer a system without informing operations, the captain may have to kick off 30 passengers at the gate to meet the new performance limits.

Tarmac Scenario: The APU Inop Dispatch

The Snag: You are dispatching an A320. During turnaround, the APU auto-shutdowns due to a low oil pressure fault.

Diagnostic & Regulatory Logic:

1. Troubleshooting: The turnaround is tight (45 minutes). You check the TSM (Troubleshooting Manual), but an APU oil pump replacement will take 4 hours. You must defer it.
2. The MEL: You open the Operator MEL chapter 49 (Airborne Auxiliary Power). The APU is listed as Category C (10 days).
3. The (M) Procedure: The MEL dictates an (M) procedure: You must deactivate the APU bleed valve to prevent unconditioned air from entering the cabin system, and secure the APU generator.
4. The (O) Procedure: Because the APU is dead, the aircraft has no pneumatic air for engine start. The (O) procedure dictates that the crew requires a Ground Air Start Unit (ASU) and external AC power.
5. Action: You perform the (M) procedure, coordinate with ramp staff to position the ASU, verify the weight penalties using the AviationHunt MEL/Dispatch Calculator, and sign the deferral in the ATL.

Case Study: The Fatal Cost of Misreading the MEL

If you treat the MEL as a simple checklist without understanding the systems you are isolating, the results are fatal. Look at the official investigation of Spanair Flight 5022 (MD-82) in Madrid.

During taxi, the flight crew noted the Ram Air Temperature (RAT) probe was overheating on the ground. The mechanics consulted the MEL, which permitted dispatch with an inoperative RAT probe heater.

To satisfy the (M) procedure, the mechanics pulled the circuit breaker for the RAT probe heater, signed the tech log, and dispatched the aircraft.

The Breakdown:

• The Hidden Dependency: What the mechanics failed to realize (and what standard line troubleshooting should have caught) was that the RAT probe was overheating because a ground sensing relay (Relay R2-5) had failed.
• The System Link: That exact same R2-5 relay also powered the aircraft’s Take-off Warning System (TOWS). By pulling the breaker and signing the MEL, they left a critical failure unaddressed.
• The Consequence: The crew attempted takeoff with the flaps fully retracted. Because the R2-5 relay was failed, the TOWS did not sound the alarm to warn them. The aircraft stalled on takeoff, resulting in 154 fatalities.

The MEL is not a license to blindly bypass broken components. You must understand why the component failed before you legally defer it. Diagnose the root cause, follow the (M) procedures to the letter, and protect your dispatch.