Airbus Flight Instructor
Airbus · Knowledge Base

MEL Dispatch — How to Use Engine MEL, Typical Items, the Boundary

This article covers the framework for using engine-related MEL: how the MEL is used, the typical dispatchable engine-system item types, and the dispatch-condition structure — with the boundary that the full items live in the MEL manual. Note on method: each MEL item's dispatch conditions + (o) operational / (m) maintenance procedures are in the MEL manual, which is frequently updated and operator-customised → a system course does not copy the MEL table, only how to use it + typical item types + a pointer to the MEL manual (the current MEL governs).


1. MEL structure

The MEL (Minimum Equipment List) is organised by ATA chapter (engine items in the ME-70–80 series + related ME-22 autothrust etc.). Each item:

Field Content
Aircraft status the fault / INOP description, ECAM alert
Dispatch conditions number required, limitations, whether dispatchable
(o) operational procedure crew action required after dispatch
(m) maintenance procedure maintenance action required for dispatch

(MEL abbreviation examples verbatim: FADEC = Full Authority Digital Engine Control, EEC = Electronic Engine Control, A/THR = autothrust [MEL HOW].)


2. How to use the MEL (engine view)

Fault / INOP → find the MEL item for the ECAM/system → read the dispatch conditions (dispatchable, number/limits) → carry out the (o) operational + (m) maintenance procedures → make the dispatch decision.


3. Typical dispatchable item types

(Pointing to the relevant article, not listing specific conditions.)

System Typical MEL item type Article
Reverser reverser INOP dispatch (landing-performance correction) 29
Ignition igniter / continuous-ignition related 06
Bleed / surge bleed valve / bleed related 08
Indicating parameter display / vibration indication related 10
Thrust A/THR (ME-22), N1-mode dispatch (flex unavailable in N1 mode, 03) 03

[!warning]- Why this article does not list specific dispatch conditions (boundary) Each MEL item's specific dispatch number / limits / (o)(m) procedures are in the MEL manual, and the MEL is frequently revised + operator-customised → a system course copying it would quickly go stale and would carry operator-specific data. By "full items → MEL manual (the current one governs)," this article gives only the framework + typical types + how to use. Actual dispatch must consult the current MEL manual.

[!note]- Echoes with the fault articles Some dispatch consequences are already verbatim in earlier articles: e.g. N1-mode dispatch → flex take-off unavailable (03 DSC-70-35-20). MEL dispatch often carries such operational limitations, established earlier.


4. Counterintuitive point

[!warning]- The course does not replace the MEL manual — dispatch must check the current MEL The MEL is frequently revised + operator-customised → this article teaches only the framework / how to use / typical types; actual dispatch must consult the current MEL manual. The course gives "how to read the MEL," not "the dispatch conditions themselves."


Self-test

[!note]- Q1. What does each MEL item contain? Aircraft status + dispatch conditions (number/limits) + (o) operational procedure + (m) maintenance procedure.

[!note]- Q2. What types of engine items might be dispatchable? Reverser INOP (29), ignition (06), bleed (08), indicating (10), A/THR / N1 mode (03); specific conditions in the MEL manual.

[!note]- Q3. Why doesn't the course list specific dispatch conditions? The MEL is frequently revised + operator-customised → copying it would go stale / carry operator data; dispatch must consult the current MEL manual (the current one governs).


Key takeaways

Point Detail
MEL structure by ATA (engine ME-70–80 + ME-22); each item = aircraft status + dispatch conditions + (o)(m) procedures
Typical engine items reverser / ignition / bleed / indicating / A/THR
Boundary the course teaches framework / how to use; dispatch must consult the current MEL manual

References

Independent study material, not an Airbus publication and not endorsed by the manufacturer. Always defer to the current operator FCOM, FCTM, and QRH for operational use.