The Pilot's Maintenance View

The final ATA 21 article: the pilot's maintenance interface — the 30-second pre-flight scan, post-flight handling, and the five classes of information for talking to maintenance. The skill of a pilot who does not repair the aircraft but must identify, describe, and coordinate.

1. The pilot's role in the maintenance chain

   defect → pilot identifies (the abnormals + ECAM) → pilot handles (FCOM/QRH)
   → pilot describes (the Tech Log) → maintenance receives → troubleshoots → repairs
   → pilot re-checks (the next cockpit preparation)

[!important]- The pilot's five "do nots"

(1) Do not repair the aircraft — the pilot is an operator, not a mechanic. (2) Do not ignore a small defect — a small symptom may build into a large one. (3) Do not simplify the description — maintenance is not there to see the ECAM. (4) Do not omit the timing and configuration — the same defect means different things at different phases. (5) Do not say "I think" — describe from the SD values + the ECAM text, not subjective feeling.

The four maintenance-interface scenarios: the pre-flight scan (cockpit prep), an in-flight finding (monitor + ECAM procedure + draft the Tech Log), post-flight handling (cabin feedback + ECAM STATUS + write the Tech Log), and the maintenance conversation (the five classes + on-site coordination).

2. The 30-second pre-flight scan

[!tip]- A 30-second ATA 21 health check

[0–5 s]  ECAM PRESS pb → SD CAB PRESS → CAB ALT (≈0) / CAB V/S (≈0) / ΔP (≈0) / OFV (full open)
[5–10 s] ECAM COND pb → SD COND → zone temps / trim-air valves / HOT AIR ON
[10–15 s] ECAM BLEED pb → SD BLEED → PFCV 1+2 / pack-outlet temp / EMER RAM AIR (crossline green)
[15–20 s] AIR COND panel → lights: PACK 1+2 / HOT AIR / CAB FAN / PAX SYS (no FAULT)
[20–25 s] CABIN PRESS panel → LDG ELEV AUTO / MODE SEL AUTO (no FAULT) / DITCHING OFF (guarded)
[25–30 s] ECAM STS pb → INOP SYS (matches the MEL?) + MAINTENANCE STATUS?

[!warning]- ECAM STS "MAINTENANCE STATUS"

Below INOP SYS the STS page sometimes shows a MAINTENANCE STATUS block — an internal state for maintenance, not affecting the flight: a BITE-found internal fault, not triggering an ECAM warning, but maintenance watches it (refer to the MMEL ECAM-and-MAINTENANCE-STATUS item). Pilot meaning: a MAINTENANCE STATUS → do not ignore it (maintenance checks it before the walk-around) → note it in the Tech Log.

3. Post-flight diagnosis

[!tip]- "Forward warm, aft cool" — the unbalanced-cabin diagnosis

The commonest ATA 21 cabin complaint is uneven temperature. Diagnose: read the SD COND page — the zone temperatures (FWD 24 °C? AFT 18 °C?), the trim-air valve positions (FWD at C closed / AFT at H open?), the HOT AIR valve. Judge: all trim valves at H but the cabin still cool → insufficient bleed temperature → check the pack-outlet temperature; one zone's trim valve stuck at C → that zone cannot balance; the HOT AIR valve closed → all trim air lost → the pack outlet sets the temperature. Then write the Tech Log with the specific zone temperatures + the valve position + the duration — not a vague "cabin temperature uneven".

[!note]- The ATA 21 walk-around physical checks

Check point	Anomaly	Possible ATA 21 fault
Belly pack exhausts (L/R)	black / oil staining	ACM oil leak / heat-exchanger fault
Belly overboard outlet	abnormal water marks	AEVC failure / steam carry-over
Wing root	abnormal airflow noise / steam	bleed leak (→ ATA 36)
Cargo door	an abnormal gap when closed	door seal affecting ΔP
Fuselage skin	abnormal bulge / dent	pressurisation structural fatigue (rare but serious)

The pilot does not repair these but must log them + notify maintenance.

4. The five classes of information & the Tech Log

[!important]- A Tech Log ATA 21 entry must contain five classes

#	Class	Example
1	Fault description	"PACK 1 OVHT triggered" / "Cabin temperature unbalanced"
2	Timing	"30 min into cruise FL 370 / climb out"
3	Configuration at the time	"PACK 1+2 ON / PACK FLOW NORM / Zone 22 °C / HOT AIR ON"
4	Recurrence	"Recurred 3 times" / "Did not recur after cooldown"
5	Action taken	"PACK 1 OFF → wait 5 min → ON → temp recovered to 200 °C"

All five are essential — without being there, maintenance reproduces + troubleshoots from these.

[!example]- A standard Tech Log entry (the log is normally written in English)

ATA: 21-51 (Pack 1 OVHT)

Description:
ECAM "AIR PACK 1 OVHT" triggered 30 min into cruise at FL 370.
SD BLEED showed Pack 1 compressor outlet at 275°C (above the 260°C threshold);
pack outlet at 88°C.

Configuration:
PACK 1+2 ON / PACK FLOW NORM / HOT AIR ON / CAB FAN ON.
Zone selectors cockpit 22°C, FWD 23°C, AFT 23°C. OAT -54°C, IAS 280 kt, weight 195 t.

Action (per FCOM PRO-ABN-AIR-AD):
PACK 1 OFF, PACK 2 high flow auto-selected. Waited 8 min until the compressor
outlet dropped to 178°C. PACK 1 ON, stabilized at 195°C. No recurrence in the
remaining 2 hours.

Cabin impact: no PAX complaints. CAB ALT remained on the normal 7000 ft schedule.
Recurrence: first this flight; not on the previous 2 sectors today.
Recommendation: inspect Pack 1 compressor + ACM; check the RAM air door; possible
heat-exchanger fouling.

[!warning]- INOP SYS vs MAINTENANCE STATUS

WARNING (L3 red) / CAUTION (L2 amber) / ADVISORY (L1 green) / STATUS / INOP SYS are for the pilot (immediate / per-procedure / known-limit / MEL cross-check). MAINTENANCE STATUS the pilot only needs to know is present — it is BITE information for maintenance. The pilot may not know its coded meaning, but must note in the Tech Log that a maintenance status was displayed — an index for maintenance.

5. Noise & smell diagnosis; avoiding "no fault found"

[!note]- Noise diagnosis

A high-frequency whine → a stuck RAM air door / the pack outlet (ata-21-07); a low-frequency rumble → cabin-fan vibration (ata-21-15); a periodic hiss → outflow-valve modulation (ata-21-12); a sudden bang → a bleed valve closing / a prepressurisation transient. Describe the character + timing + location for maintenance to localise.

[!note]- Smell diagnosis

Smell	Possible cause	Action
A specific fluid smell	a rain-repellent fluid leak (ata-21-26)	the SMOKE/FUMES procedure
Burning	an electrical fault / a fan burning	the SMOKE/FUMES procedure + emphasise it
Oil	ACM oil leak / engine bleed oil contamination	Tech Log + maintenance
Musty	a failed recirculation filter / blocked drain	ata-21-10
Unidentified chemical	unknown → the SMOKE/FUMES procedure	no delay

The pilot's rule: any unidentified smell → the SMOKE/FUMES procedure at once, not "wait for it to go away".

[!warning]- Avoiding "no fault found" (NFF)

Maintenance's worst case is reproducing nothing — the pilot saw a fault, maintenance finds none. Three ways the pilot helps: (1) photograph the SD / ECAM (time, fields, the warning text); (2) record the timestamp (to the minute); (3) record the configuration values (OAT, IAS, weight, PAX, the zone-selector settings). This metadata lets maintenance reproduce the conditions precisely, greatly raising the reproduction rate.

6. The 32-article retrospective

[!example]- The complete ATA 21 material

Stage A — foundations (6): overview, main airflow, pack principles, pressurisation principles, ventilation principles, cargo environmental control. Stage B — component deep-dives (11): PFCV, ACM, pack controller, zone controller, mixing/recirculation, CPC, outflow valve, safety/negative-relief valves, avionics ventilation, cabin/pack-bay/battery/lav-galley, cargo ventilation. Stage C — interfaces (2): cross-system interfaces, physical layout. Stage D — indication (2): ECAM COND/BLEED, ECAM CAB PRESS & warnings. Stage E — abnormals (8): single-pack, dual-pack/RAM AIR, automatic-pressurisation failure, excess cabin altitude, ΔP faults, smoke/fumes, ventilation/cargo-fire, ditching. Stage F — dispatch & operations (3): MEL & dispatch, typical day, the maintenance view (this).

After the 32 articles, a pilot can: understand the A330 ATA 21 to component level; recognise the warnings + handle the procedures; apply the MEL; write a professional Tech Log; and decide correctly in the abnormal scenarios (emergency descent / ditching). Next (beyond this material): the simulator, the operator SOP + operations specification, the regulations, and accumulated line experience.

Self-test

[!note]- Q1. On the pre-flight scan, the normal SD CAB PRESS four-field values?

Cold aircraft: CAB ALT ≈ 0 ft, CAB V/S ≈ 0, ΔP ≈ 0 PSI, OFV fully open (the ground-mode default). Any anomaly → investigate further.

[!note]- Q2. Post-flight, the cabin reports "uneven temperature" — how do you diagnose?

Read the SD COND page: the zone temperatures + the trim-air valve positions. Judge: one zone's trim valve stuck at C → that zone cannot heat; all valves at H but still cool → insufficient pack-outlet temperature; the HOT AIR valve closed → all trim air lost. Then write the Tech Log with the specific zone temperatures + the valve position + the pack-outlet temperature + the duration — not a vague "uneven".

[!note]- Q3. The STS page shows MAINTENANCE STATUS — should the pilot care?

Yes — not "immediate action" but a Tech Log note. It is a BITE-found internal fault, not affecting the flight or triggering a warning, but maintenance cares (an early sign of a hidden problem). Refer to the MMEL item; note "MAINTENANCE STATUS displayed" in the Tech Log as an index for maintenance.

[!note]- Q4. After a successful PACK 1 OVHT handling, how do you write the Tech Log?

All five classes: description ("AIR PACK 1 OVHT, compressor outlet 275 °C above 260 °C"); timing ("30 min into FL 370 cruise"); configuration ("PACK 1+2 ON / PACK FLOW NORM / Zone 22 °C / OAT −54 °C / weight 195 t"); recurrence ("first this flight, not on the previous 2 sectors"); action ("PRO-ABN-AIR-AD: PACK 1 OFF, 8 min, 178 °C, PACK 1 ON, stabilized 195 °C, no recurrence").

[!note]- Q5. You smell burning in the cockpit — besides the Tech Log, what immediately?

The SMOKE/FUMES procedure at once (ata-21-26): CREW OXY MASKS USE/100%/EMERG; verify crew comms; LAND ASAP (red) + notify ATC + a diversion; the suspected-source branch; alert the cabin crew. Do not wait for it to "go away" — burning means an electrical fault / a fan burning, possibly escalating to a fire. The Tech Log is written after landing — the procedure comes first.

Key takeaways

Common misconceptions

Scope — what this article covers and defers

References

A330 specifics per FCOM PRO-NOR-SOP-06 (the cockpit-preparation ECAM checks and the STS-page INOP SYS / MAINTENANCE STATUS), the MMEL ECAM-and-MAINTENANCE-STATUS item, FCOM PRO-ABN-SMOKE (the smell-handling basis), and FCOM DSC-21-10-50 (the SD-page field meanings). The 30-second-scan structure, the Tech Log five-class framework and example, the noise/smell diagnosis tables, and the no-fault-found avoidance are integrative syntheses (consistent with the SD-value precision required throughout this material). The Tech Log example is a generic recommended format without an operator name, flight number, or fleet tail number. All engineering detail is from the A330 knowledge base; no cross-type comparison is made.

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.