Reporting, handing over, and looking it up

Three procedures. Two are performances — a report and a briefing — that you can practice in the in-person shop course; the third is a lookup.

These are the shortest procedures in the curriculum and the hardest to do well, because their difficulty is not technical.

Procedure 1 — File a Malfunction or Defect Report (S1)

Given — a defect you have found that warrants reporting. Sought — a filed FAA Form 8010-4 that is useful to whoever reads it.

Method

1. Decide whether it warrants a report. The form exists to surface defects that may affect others — a pattern, a part failing before its time, something that is not a one-off. Not every worn part is a report; a worn part that should not be worn is.
2. Identify the article precisely. Part number, serial number, manufacturer, and the aircraft or engine it came from with times and cycles. A report that does not identify the part is not actionable.
3. Describe what you found, not what you concluded. "Cracked at the weld, approximately 12 mm, found during 100-hour inspection" is a finding. "Poor manufacturing quality" is an opinion, and it displaces the observation the reader needs.
4. Give the context: total time, time since overhaul, operating environment, anything unusual about how the aircraft is used.
5. Say what you did about it — replaced, repaired, quarantined.
6. File it, and keep a copy with the maintenance record.

Check — could someone who has never seen this aircraft find the same defect on another one? If the report does not let them, it is a note to yourself rather than a report.

Failure — the report that says a part failed and does not say which part, how long it had been in service, or what the surrounding conditions were. It is filed, it is counted, and it tells nobody anything.

R1 lives here. The hard cases are the ones where filing is inconvenient: the defect you caused, the defect that delays a release, the defect on a colleague's work. The form is identical. The decision is not (GEN-L Concepts §5).

Procedure 2 — Brief a shift turnover (S2)

Given — work in progress that you are handing to someone else. Sought — that they can continue it safely without rediscovering what you already know.

Method

1. State the aircraft and the task, and what the task is for.
2. State exactly where you stopped. Not "about half done" — the last step completed, and the next step due. This is the whole of the procedure and everything else supports it.
3. State what is disturbed: panels off, systems depressurized, circuit breakers pulled, fasteners fitted but not torqued, safety wire not yet installed.
4. State what is not obvious by looking. A fitted-but-untorqued fastener looks finished. Say so explicitly, every time.
5. Hand over the paperwork — the manual open at the right page, the worksheet, the parts.
6. Ask them to tell you back what they are picking up. Then correct what they got wrong.

Check — step 6 is the check. A turnover you delivered is not a turnover they received. If they cannot state the next step and the disturbed condition of the aircraft, the handover has not happened yet.

Failure — the untorqued fastener that looks torqued. It is the classic turnover failure, it appears in accident reports, and step 4 exists solely to prevent it.

Never leave a task in a state that looks finished. If you must stop mid-task, leave visible evidence that it is incomplete — a warning tag, a panel deliberately left off, a fastener deliberately left out. Make the aircraft tell the next person what the briefing said.

Procedure 3 — Locate information regarding human factors errors (S3)

Given — an event you want to understand, or a factor you want to check. Sought — the applicable source.

Method

1. Start with the FAA's own maintenance human factors material, which is public and is the source this element points at.
2. For a specific event type, look for accident and incident reporting data rather than commentary.
3. For a specific error, use the classification vocabulary from GEN-L Concepts §3 as your search terms — slip, lapse, mistake, violation, latent condition — because the literature is organized that way.

Check — you should be able to name the source and its date. An unattributed claim about human error is not usable in an investigation.

The checks, collected

All three checks are the same check in different clothes: does this work for the next person? That is what human factors is, and it is why this unit's procedures are short and its subject is not.

License

CC BY-SA 4.0 (Licensing).