You can turn the wrench perfectly, torque the bolts to the exact inch-pound, and lock-wire the assembly like a work of art. But if you do not document it correctly in the Aircraft Technical Logbook (ATL), the aircraft is legally unairworthy.
The ATL is not a diary—it is a legally binding contract between the maintenance department, the flight crew, and the regulatory authority. When a pilot writes up a snag, the aircraft is grounded until a certifying mechanic signs the action taken.
For AME students and line mechanics, mastering the ATL is just as critical as mastering your tools. Here is the hangar-floor reality of sector records, defect deferrals, and the legal weight of your pen.
Prerequisite Knowledge: The Legal Status of the ATL
Before you make a single entry, you must understand the regulatory foundation of the logbook.
- The Baseline Rule: Every commercial aircraft must carry an ATL. It tracks the aircraft’s maintenance status, fuel uplift, flight cycles, and deferred defects.
- Regulatory Links:
The Anatomy of a Sector Record Page
Whether it is a physical paper binder or a glass screen, every sector record page operates on a strict call-and-response format between the pilot and the mechanic.
| Section | Who Owns It | Legal Purpose |
| Flight Details | Flight Crew | Logs cycles, block times, and sectors flown (critical for life-limited parts tracking). |
| Defect / Snag | Flight Crew | The exact report of a malfunction. Once written, the aircraft is legally grounded until cleared. |
| Action Taken | Line Mechanic | The exact maintenance performed, referencing approved data (AMM/TSM/MEL). |
| CRS / Release | Line Mechanic | The signature, date, and license number returning the aircraft to service. |
WARNING: NEVER ALTER A PILOT’S ENTRY. If a pilot writes a snag that is technically inaccurate (e.g., calling an IDG a “generator thingy”), do not cross it out or use correction fluid. You must respond to exactly what is written, diagnosing the actual fault in your “Action Taken” block.
Fleet Granularity: Paper vs. Glass (eTLB)
The transition from analog to digital has fundamentally changed how line mechanics clear defects.
Legacy Fleets (Boeing 737NG / A320ceo)
Older fleets rely on a traditional NCR (No Carbon Required) carbon-copy paper logbook. The logbook stays physically on the flight deck. If you make a mistake, you must draw a single line through the error, sign, and date it. The physical pink or yellow pages must be torn out and dropped in the station box before the aircraft can legally push back.
Modern Fleets (Boeing 787 / A350 / A320neo)
Modern aircraft utilize an Electronic Technical Logbook (eTLB) integrated into the flight deck tough-pads.
- The Advantage: Real-time synchronization. Maintenance Control Center (MCC) sees the pilot’s snag before the aircraft even lands, allowing you to have the exact LEAP-1A sensor and tools waiting at the gate.
- The Trap: Digital timestamps are unforgiving. You cannot backdate a signature or sign a dispatch clearance simultaneously with a pilot. The system locks out steps to force regulatory compliance.
The Defect Deferral Process: Legal Rules of the ADD
When you cannot fix a snag on the turnaround, you must transfer it to the Acceptable Deferred Defect (ADD) log. This is where the MEL/CDL comes into play.
- Troubleshoot and Isolate: Identify the exact component failure using the TSM/FIM.
- Verify the MEL: Ensure the component is allowed to be inoperative.
- Perform (M) Procedures: Execute any mechanical isolation procedures required by the MEL.
- Transfer the Defect: Write the defect into the ADD section of the ATL, assigning it the specific MEL reference number and the expiration date (Category A, B, C, or D).
- Placard: You must physically install an “INOP” placard on the flight deck control associated with the deferred system.
CAUTION: THE NFF LOOP. Writing “Tested OK, No Fault Found (NFF)” for a recurrent snag without performing deep troubleshooting is a massive red flag for regulators. If a system fails three times in a week and is cleared NFF three times, it is a sign of pencil-whipping. You must escalate chronic snags to MCC for deep diagnostics.
Tarmac Scenario: The A320 Bleed Fault at 02:00 AM
The Snag: You are meeting a transit A320. The pilot writes in the ATL: “ENG 1 Bleed trip during descent. ECAM AIR ENG 1 BLEED FAULT.”
Diagnostic & Regulatory Logic:
- TSM Action: You run the CFDS (Centralized Fault Display System) BITE test on the Bleed Monitoring Computer (BMC). The fault points to a failed PRV (Pressure Regulating Valve).
- Logistics: Stores does not have a PRV in stock. It is a 4-hour replacement job anyway. You must defer it.
- MEL Check: You check MEL Chapter 36 (Pneumatic). The Engine 1 Bleed system can be deferred under Category C (10 days).
- The (M) Procedure: The MEL requires you to physically lock the PRV in the closed position using the manual override mechanism.
- Documentation: In the ATL “Action Taken” block, you write: “Troubleshot per TSM 36-11-00-810-801. PRV identified as failed. PRV mechanically locked closed per MEL 36-11-01 (M) procedure. Defect transferred to ADD #1234. System placarded INOP.” You verify the MEL conditions using the MEL/Dispatch Calculator and sign your CRS.
Case Study: The Danger of the “Action Taken” Block
The ATL is a communication tool. If what you write does not perfectly align with the physical state of the aircraft, people die. Look at the official Hellenic AAIASB report for Helios Airways Flight 522 (Boeing 737-300).
The aircraft arrived with a pilot snag reporting an aft service door seal issue and a freezing cabin during the previous flight. The line mechanic suspected a pressurization leak.
To perform a cabin pressure test on the ground, the mechanic switched the pressurization system from AUTO to MANUAL. The test passed, no leak was found. The mechanic cleared the snag in the ATL, writing: “Cabin pressure test carried out OK. NFF.”
The Breakdown:
- The Critical Omission: The mechanic forgot to switch the pressurization controller back from MANUAL to AUTO after the test.
- The Communication Failure: The “Action Taken” in the tech log did not state that the system configuration was altered. The flight crew read the “OK” in the tech log and assumed the aircraft was in its standard dispatch configuration.
- The Catastrophe: The aircraft took off with the pressurization system in MANUAL. The cabin failed to pressurize. The pilots, misinterpreting the warning horns, suffered hypoxia and passed out. The aircraft flew on autopilot until it ran out of fuel and crashed, killing all 121 on board.
Your entry in the logbook is the last line of defense. Say exactly what you did, ensure the aircraft matches your words, and never rush a signature.
