What Documentation Should Accompany Every Airbus Auxiliary Power Unit Transaction

When an Airbus auxiliary power unit changes hands through a lease, exchange, or outright sale, the documentation package that accompanies the unit is as operationally significant as the unit itself. An APU that arrives without complete, compliant paperwork cannot be installed until the records are resolved. For operators managing tight maintenance schedules, that delay can be as costly as the removal that triggered the transaction in the first place.

Why Documentation Drives Installation Readiness

An Airbus APU is not installation-ready based on its physical condition alone. Before a unit can be inducted into service, the receiving operator's engineering and quality teams must confirm that the documentation meets their internal acceptance standards and the requirements of the applicable airworthiness authority. A unit that looks serviceable on the shop floor is not legally or technically cleared for installation without a complete paper trail confirming its history, condition, and compliance status.

This distinction matters because documentation gaps are not always visible at the point of delivery. A missing airworthiness directive compliance record or an incomplete ownership trace may not surface until the unit is already at the aircraft, at which point the operator faces a choice between delaying the installation or accepting a compliance risk. Neither outcome is acceptable in a regulated maintenance environment.

The Core Documentation Package

Every Airbus APU transaction should include the following as a minimum:

1. FAA/EASA Form 8130-3 is the primary airworthiness release document. It confirms the unit has been inspected or overhauled by an authorized repair station and is in a condition for safe operation. For units intended for use on aircraft registered outside the United States, dual release under both FAA and EASA authority is preferred and, in many cases, required.
2. ATA 106 trace documentation provides the full ownership history of the unit from its original manufacture through every subsequent operator, repair station, and transaction. Unbroken trace to the original equipment manufacturer or the last airline operator is the accepted standard. Any gap in the ownership chain creates an airworthiness question that must be resolved before installation.
3. A non-incident statement confirms that the unit has not been involved in an aircraft accident, incident, or exposure to abnormal operating conditions including fire, flood, extreme stress, or corrosive storage. This declaration protects the receiving operator from unknowingly installing a unit with undisclosed damage history.
4. Airworthiness directive compliance records must document every applicable AD against the unit, including the AD number, amendment number, date of compliance, and method of compliance. Partial AD records or records that reference compliance without supporting evidence are not sufficient.
5. LLP status documentation must confirm the current cycles since new for each life-limited part, the applicable limiter value, and the remaining life before the next replacement is required. Operators should verify that the disclosed limiter value meets their fleet's minimum acceptance criteria before committing to a transaction.
6. Utilization data covering time since new, cycles since new, time since overhaul, and cycles since overhaul gives the receiving operator a complete picture of where the unit sits in its service life and what maintenance events are approaching.

Platform-Specific Considerations

Airbus APU models vary across the family. The A320 family uses different models than the A330, A350, and A380. Each platform has its own applicable ADs, LLP part numbers, and limiter thresholds defined by the OEM. Documentation that is complete for one model may be structured differently for another. Operators and procurement teams should confirm that the documentation package references the correct part number and serial number for the specific unit being transacted and that AD compliance records reflect the applicable directives for that model, not a generic package carried over from a different variant.

What To Require Before Committing

The time to request and review documentation is before a transaction is agreed, not after delivery. Operators who require a complete documentation package as a condition of commitment have the ability to identify gaps, request corrections, and delay delivery if records cannot be produced. Operators who accept a unit first and attempt to resolve documentation afterward lose that leverage and often spend more time reconstructing records than the original transaction took to execute.

A supplier who cannot produce a complete documentation package on request may not be trusted with an installation-critical asset. Requiring full documentation upfront is not an administrative formality. It is the most direct protection an operator has against airworthiness exposure, AOG extension, and lease return disputes.