MEL Dispatch & ETOPS

ECAM governs what to do in the air; the MEL governs whether to dispatch from the ground. The engine MEL chapter maps ECAM alert names to dispatch entries, one by one — you look up the dispatch terms holding the alert's name. Read all 53 mappings and the verdicts reduce to three kinds, plus one sorting switch. ETOPS then closes the whole chapter as its macro-scale footnote: a twin-engine aircraft's licence to fly far from land rests entirely on the credibility of the engine this chapter has been describing.

This is the closing article of the ATA-70 series.

1. The three verdicts

Each MEL entry reads ECAM alert name | aircraft status → dispatch conditions. Scanning the full chapter, three verdict types emerge:

1.1 The two most instructive contrasts

FADEC FAULT's air/ground reversal. Article 19 called it mute, not paralysed — in flight you proxy-confirm on three pages and carry on. Yet the ground verdict is no dispatch (synthesis): the in-flight logic is control is intact — finish this sector; the dispatch logic is an aircraft with no engine reporting chain does not begin a new flight. You may not take off behind an engine whose instruments you cannot see. This mirrors FADEC SYS FAULT's "NO DISPATCH yet no in-flight action" from the other direction: the airborne ledger and the dispatch ledger are separate books — one alert governs whether you may continue, the other whether you may begin.

The depth of "not related to the MEL". ENG FAIL and the OVERLIMITs appear in the table only to be declared outside it — the MEL drawing its own boundary (synthesis). The MEL's business is dispatching with degraded equipment; an engine failure or exceedance is an event, and an event's exit is maintenance inspection (the downstream of article 28's logbook-to-borescope line). Pass the inspection and the alert no longer exists — there is nothing to "dispatch with". Listing them at all is a fence: it stops anyone holding an alert name from mining the MEL for a fly-anyway clause.

1.2 The genuine/spurious sorting switch

For the ignition alerts the MEL forks explicitly: genuine warning → the ignition system's own item (system A or B — repair intervals and limitations); spurious warning → the warning function's item — dispatching with a false-alarming annunciation is a different set of terms entirely. The philosophy runs through the whole MEL: whether the broken thing is the function, or the lamp that reports the function, the dispatch terms differ. And the genuine/spurious call is precisely the ground value of the airborne verification procedures from articles 19/20 — the SLOW RESPONSE pass, the maintenance-coordinated second start. The spurious determination you make in the air decides which MEL line the ground walks.

REV INHIBITED → the reverser lock-out item closes article 32's loop: that alert is the display of an MEL dispatch already in effect — entry and alert are two faces of one state.

2. ETOPS: the chapter's macro-scale footnote

"Due to the poor reliability of piston engines in the early 1950s, the ICAO recommended that no aircraft be operated beyond 90 min with all engines operative, from a diversion airport … The FAA was even more restrictive … limited … twins, to areas where they were less than 60 min away …"

ETOPS in essence (synthesis, following the Airbus ETOPS guide's framing): a line of credit permitting the twin to fly beyond the 60-minute circle — and the collateral is everything this chapter has described. The triple-spool's containment design (article 01); the FADEC's dual channels and the four-layer overspeed protection (articles 04/05/28); the anti-flameout kit (article 05); the dual ignition (article 11); the complete single-engine ledger and circling capability (article 25).

Every single-engine diversion is an ETOPS design assumption being honoured: single-engine cruise thrust at the MCT detent, APU availability, diversion fuel reserves (the fuel chapter's domain) — together guaranteeing the other engine carries you to the airport. The operating rules themselves — areas, diversion times, dispatch requirements — belong to the ETOPS documentation and operators' regulations; what this chapter supplies is the engine credibility underneath them. Read the MEL's severity in that light and it gains a second meaning: zero tolerance for a missing FADEC reporting chain, a dedicated line for double ignition loss — an ocean-going flight's margins must be fully stocked before the wheels leave the ground.

3. The chapter in retrospect — the 36-article map, final edition

Five design languages run through the whole chapter (teaching synthesis):

1. Dual channel plus organ-borrowing — redundancy used at two depths.
2. Fail toward the safe side — stator vanes close, bleed valves open, cooling control shuts: directions differ, purpose identical.
3. Layered protection, itself monitored — red-line limiters → independent protections → mechanical backstop, with every layer's failure carrying its own alert.
4. Say only what the crew needs — inhibition windows, single-engine suppression, the awareness grade.
5. The airborne ledger and the ground ledger are separate books — NO DISPATCH with no in-flight action; FADEC FAULT flyable in the air, unreleasable on the ground.

4. Scenario walk-throughs

Turnaround with OIL CHIP standing. Look up the chip-detector item; dispatch is decided jointly with maintenance on that item's terms.

FADEC FAULT at landing. Tell the company early: this aircraft does not fly its next sector (no dispatch) — operations control needs the lead time.

IGN A FAULT overnight. Maintenance's first step is the genuine/spurious call — and your in-flight evidence (the second-start verification result) is the deciding input.

Post-diversion review on an ETOPS route. Walking article 25's ledger against the ETOPS diversion assumptions is the best recurrent-training material there is.

Self-test

[!note]- Q1. The three MEL verdicts? No dispatch (e.g. FADEC FAULT) / not related to the MEL (events: ENG FAIL, the OVERLIMITs) / refer to the equipment item (chip detector, reverser lock-out, and the rest).

[!note]- Q2. FADEC FAULT flies in the air — why won't it dispatch? Airborne ledger: control intact, proxy-confirm, finish the sector. Dispatch ledger: no engine reporting chain, no new flight. The mirror image of SYS FAULT's no-dispatch-but-no-action.

[!note]- Q3. Genuine versus spurious — which line does each walk? Genuine → the ignition system's own item; spurious → the warning function's item. Function broken versus lamp broken: different terms. Your airborne spurious verdict picks the line.

[!note]- Q4. What does "not related to the MEL" mean for an OVERLIMIT? An exceedance is an event, not an equipment state — its exit is inspection, not a dispatch clause. The listing exists to prevent misuse of the MEL.

[!note]- Q5. ETOPS and this chapter, in one sentence? ETOPS is a line of credit drawn on engine credibility — this chapter's designs (containment, protection, redundancy, single-engine capability) are the collateral, and every diversion honours the assumptions.

Key takeaways

References

• Operator MEL (engine chapter) — the 53 alert-to-item mappings, the three verdict types, the genuine/spurious forks, and the canonical entries discussed; repair intervals and specific limitations per the MEL text itself.
• Getting to Grips with ETOPS, Vol. II (the flight-operations view) — the historical origin quoted (90/60-minute rules); operating rules per the ETOPS documentation and operator regulations.
• Integrative synthesis (marked in text): the two contrasts; the sorting-switch philosophy and its link to airborne verification; the credit/collateral framing; the five design languages.

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.