How do you document a red X on the AFTO 781A?

The controlling publication in each branch

What the regulation actually says

Every discrepancy, on the 781A

The AFTO Form 781A documents each discrepancy discovered by aircrew or maintenance personnel, with one standing exception: on discovery of battle damage the finder makes an initial red X entry reading that the aircraft sustained battle damage, and the damage is then tracked on the AFTO Form 97 series instead.

“5.7 AFTO FORM 781A, MAINTENANCE DISCREPANCY AND WORK DOCUMENT. (Figure 5-3 and Figure 5-4) Use the AFTO Form 781A to document each discrepancy discovered by aircrew or maintenance personnel. NOTE EXCEPTION: Upon discovery of battle damage, the finder will make an initial Red X entry in the aircraft’s AFTO Form 781A which reads “Aircraft sustained battle damage, see AFTO Form 97.” From this point, all discrepancies resulting from battle damage will be documented on AFTO Form 97/97A/97B. See TO 1-1H-39, for specific instructions on documenting aerospace vehicle battle damage repairs.”

A red X goes in both places

Discrepancies found during scheduled inspections may be recorded in the maintenance information system, on locally approved lists, or on work control documents — but every red X entry must appear in both the AFTO Form 781A and the MIS.

“5.7.1.3.11.8 Record discrepancies discovered during scheduled inspections directly in the MIS, locally developed/approved lists or WCDs. All Red X entries must be entered in both the AFTO Form 781A and MIS (MIS only for paperless inspections). All other discrepancies tracked on locally developed lists and/or WCDs that cannot be corrected by the allotted scheduled inspection time, must be transcribed to the MIS with the documents routed with the 781 series forms package and filed with the inspection historical documents.”

Removed parts get their own entry

Any component removed to facilitate other maintenance is documented as a separate discrepancy with its own red symbol, and this applies even when the item goes straight back on, cross-referenced by job control number or by page and item.

“5.7.1.3.11.9 Any component removed to FOM, will be documented as a separate discrepancy with the appropriate Red symbol entry. This applies even if the item is immediately reinstalled. Reference the original discrepancy using “See JCN __________” and/or “See Page __________, Item __________.” NOTE • EXCEPTION: Procedures that require removal of a component as a step of the task and contain all of the steps for component removal/installation within the same procedure do not need to be documented separately. If applicable, ensure steps include any operational checks and functional check flights documentation procedures IAW Paragraph 5.4. • EXCEPTION: If the removal to FOM WCEs/WESs are part of the original discrepancy and are listed in the MIS generated AFTO Form 781A, a reference to the original discrepancy is not required.”

Warning tags are tracked separately

Warning tags, circuit breaker safety locks and engine control box straps are documented on their own red X, as an associated job control number or work control entry, and must match a corresponding AFTO Form 781A and MIS entry.

“5.7.1.3.11.5.7 Documentation. Warning tag(s)/circuit breaker safety lock/(s)ECB strap(s) will be documented on a separate Red X as either an associated JCN or WCE/WES. Warning tag(s)/circuit breaker safety lock(s)/ECB strap(s) must match a corresponding AFTO Form 781A and MIS entry. (MIS only for paperless inspections). Warning tags/circuit breaker safety lock(s)/ECB straps may be grouped providing all tags/straps pertain to the same discrepancy. NOTE • EXCEPTION: Non-discrepancy driven warning tag(s)/circuit breaker safety lock(s)/ECB strap(s) (i.e., system locked out to perform pre-flight, etc.) will still be documented on a Red X but are not required to match a corresponding AFTO Form 781A and MIS entry. • EXCEPTION: An individual warning tag JCN discrepancy may reference multiple corresponding AFTO Form 781A and MIS entries providing all entries require the same exact warning tags.”… (paragraph continues in the PDF)

One red X for a modification

A modification is documented by a single red X entered or transferred into the 781A, and no concurrent maintenance is performed during it without maintenance group commander approval and agreement from the depot team.

“3.14.1.1.1 A single Red X symbol will be entered or transferred into the AFTO Forms 781A to document the modification to be performed. No concurrent maintenance will be accomplished during this modification unless previously agreed with MXG/CC approval and the Depot team.”

Panel removal can be consolidated

Group commanders may develop local panel sheets to record panels removed for an inspection, provided a red X entry in the 781A reflects their use — which avoids a separate red X for every panel and in-process inspection.

“5.7.1.3.11.3.1 For scheduled inspections, GP/CCs have the option of developing local panel sheets to record the removal of panels required by an inspection as long as a Red X entry is made in the AFTO Form 781A which reflects its use. This will preclude a separate Red X entry for each panel/IPI. Local panel sheets contain as a minimum: panel number or nomenclature, name and employee number of individual who removed panel, minimum signature and employee number of individual who installed the panel and minimum signature and employee number of individual who performed applicable IPIs. Local panel sheets will be treated the same as aerospace vehicle documents and filed with the inspection historical documents.”

The inspector signs the original

The inspector who completes an in-process inspection records it in the corrective action block of the original discrepancy, naming the task or step complied with, and enters their minimum signature there rather than opening a new entry.

“5.7.1.3.11.6.1 The IPI inspector who completes the IPI will indicate completion of the IPI(s) in the CORRECTIVE ACTION block of the original discrepancy by stating, “Required IPI (insert IPI task title or IPI description or IPI step number) complied with” and enter minimum signature in the CORRECTIVE ACTION block. If more than one IPI is required to complete the task, IPI inspector must identify number of IPIs in corrective action block such as, “Three required IPIs (insert IPI task title or IPI description or IPI step number of three IPIs) complied with.” If there is no room in the CORRECTIVE ACTION block, the IPI inspector will document IPIs as a separate entry in the AFTO Form 781A or appropriate work package. Place the IPI(s) on a Red X and reference the page and item number of the original discrepancy(s).”

Ask a follow-up

Need this narrowed to your branch or a specific paragraph? Ask it here — free, and the answer quotes the regulation text where we have it indexed.

Related answers

• What Should QA Look For During a Corrosion Control Inspection?
• What should QA check on an AGE ready line in-use inspection?
• What should QA look for when reviewing aircraft maintenance forms documentation?
• What should QA check for CTK and tool accountability?
• What should QA look for when evaluating technical data compliance?
• What should QA check when observing aircraft refueling?