Airbus Flight Instructor
Airbus · Knowledge Base

Volcanic Ash / FOD — Avoidance, Engine Effects, Symptom Links

This article covers the threat of volcanic ash and foreign-object damage (FOD) to the engine: the avoidance principle (verbatim), the observable engine symptoms (linking to 22/23/24/31), and FOD/bird strike vs vibration. Note on method: the avoidance principle is verbatim in the master library; the detailed damage mechanism of volcanic ash (melting / erosion) is not described in the master library for the A330/Trent, so it is not inferred — only the observable symptoms are pointed to.


1. External-ingestion threats

Threat Source Main risk
Volcanic ash eruption cloud both engines affected at once (common cause) → surge / EGT rise / flameout
Bird strike take-off / approach fan/compressor blade damage → vibration (24)
FOD runway debris etc. blade damage → vibration

Volcanic ash is most dangerous because it affects both engines at once (common cause), able to cause all-engines failure (31).


2. Volcanic-ash avoidance

Avoid flight into areas of known volcanic activity. If a volcanic eruption is reported while the aircraft is in flight, reroute the flight to remain well clear of the affected area (volcanic dust may be spread over several hundred miles). If possible, stay on the upwind side of the volcano (at least 20 NM upwind of it if it is erupting).

Per FCTM PR-AEP-MISC: avoid known volcanic activity; reroute well clear if an eruption is reported (dust spreads hundreds of miles); stay upwind (at least 20 NM upwind if erupting).

[!warning]- The core threat of volcanic ash: a common-cause both-engine event Volcanic ash is an external medium entering both engines at once → both can surge / EGT-rise / flame out together (common-cause failure → 31). Avoidance is primary (the master library stresses avoid + 20 NM upwind) — prevention over handling.


3. Engine symptoms (boundary — pointing to fault articles)

The observable engine symptoms of volcanic ash / FOD (pointing to the fault articles; the damage mechanism is not detailed here):

Symptom → article
surge (noise / flame / EGT spike) 22
EGT overlimit 23
vibration overlimit (blade damage / imbalance) 24
multi-engine flameout 31

[!note]- Why the volcanic-ash damage mechanism is not detailed (boundary) Mechanisms like "ash melting onto the turbine / eroding blades" are general aviation knowledge, but the master library does not give a verbatim A330/Trent description here → by "not in the master library → do not infer," this article covers only the evidenced avoidance principle (PR-AEP-MISC) and the observable-symptom links (existing fault articles), not the physical mechanism.


4. Handling framework and counterintuitive point

 prevention (primary): avoidance — avoid known volcanic areas / reroute clear / 20 NM upwind (PR-AEP-MISC)
 if encountered (symptoms):
   ├─ surge → 22
   ├─ EGT rise → 23
   ├─ vibration → 24
   └─ multi-engine flameout → 31 (all-engines failure + relight 21)
 full encounter handling → QRH / PR-AEP-MISC

[!warning]- Volcanic ash is a common cause — it can take out both engines at once Unlike a single-engine mechanical fault — ash enters both engines simultaneously → both damaged together (31). Hence the master library's emphasis on avoidance (20 NM upwind), prevention first.


Self-test

[!note]- Q1. The volcanic-ash avoidance principle? Avoid known volcanic activity; reroute clear if an eruption is reported (dust spreads hundreds of miles); stay upwind, at least 20 NM upwind if erupting.

[!note]- Q2. Where do volcanic-ash / FOD engine symptoms go? Surge → 22, EGT overlimit → 23, vibration → 24, multi-engine flameout → 31.

[!note]- Q3. The most dangerous aspect of volcanic ash? Common cause — entering both engines at once → both damaged / flame out (31). Hence avoidance is primary.


Key takeaways

Point Detail
Avoidance avoid known areas / reroute / 20 NM upwind (prevention primary)
Volcanic ash a common-cause threat (both engines → all-engines failure 31)
Symptoms surge 22 / EGT 23 / vibration 24 / multi-engine flameout 31
Boundary damage mechanism not in the master library → not inferred

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.