ATR 72 Airworthiness Directive status records review

When this review is needed

• ATR 72 assets are being purchased, returned, inducted, or prepared for sale.
• AD status list entries need to be checked against source records before the next handoff.
• propeller and regional-operation evidence can be decisive at transfer, making unsupported AD status entries more expensive to resolve late.

The problem

ATR 72 records cannot be treated as generic aircraft paperwork. ATR 72 records place more emphasis on propeller, landing-gear, corrosion, and regional-operation maintenance evidence than a typical narrowbody review. A summary status line can miss those family-specific pressure points, especially where an AD is marked closed without the accomplishment record behind it.

What gets reviewed

• AD compliance status for the reviewed ATR 72 asset
• AD status list entries tied to the relevant serial numbers and configuration
• applicability notes, accomplishment records, and method-of-compliance evidence behind the family-specific records position
• Configuration, utilization, or program records that affect turboprop aircraft acceptance
• Open gaps where the accomplishment entry and method of compliance for the affected serial number is missing or inconsistent

What gets validated

• AD applicability and closure is supported by source records for the asset configuration
• ATR 72 family considerations are reflected in the records reviewed
• AD status list entries reconcile with serial numbers, dates, and revisions
• Documents that affect propeller and regional-operation evidence can be decisive at transfer are isolated for closer review
• Every exception includes the record needed to close it

Evidence normally required

• ATR 72 current status reports
• AD status list
• applicability notes, accomplishment records, and method-of-compliance evidence
• Configuration list, modification status, and maintenance-program context

Common discrepancies

• an AD is marked closed without the accomplishment record behind it
• Family-specific configuration or utilization assumptions are missing from the records package
• Source evidence is present but not linked to the serial number or asset configuration
• A prior operator or shop holds documents needed to support the current family-specific status

What is at stake

unsupported AD closure can turn into a return finding, audit finding, or authority question. On ATR 72 assets, that issue can also affect the family-specific records areas tied to propeller and regional-operation evidence can be decisive at transfer.

How the work runs

What the buyer receives

• A ATR 72 AD status exception list
• A source-record map tied to the reviewed asset
• A closure plan for unsupported family-specific records items

Who uses the output

• Asset managers evaluating value and transfer risk
• Fleet teams inducting or returning the aircraft
• Records teams closing source-evidence gaps

How the work fits into the transaction or program

The review supports a transaction, return, induction, or program transition where the asset family changes which records deserve the closest read.

Aircraft-specific considerations

ATR 72 records place more emphasis on propeller, landing-gear, corrosion, and regional-operation maintenance evidence than a typical narrowbody review.

Jurisdiction-specific considerations

FAA and EASA contexts both require a supported records position, but the receiving party may ask different questions about releases, prior maintenance, and configuration evidence.

Regulatory limits

The review checks the records supplied for the asset. It does not determine airworthiness, inspect the aircraft, or guarantee authority acceptance.

What this review does not cover

• Physical aircraft survey or conformity inspection
• Manufacturer support, endorsement, or service bulletin interpretation on behalf of the manufacturer
• Valuation or negotiation of transaction terms

Specific to this review

• ATR 72 records are shaped by ATR 72 records place more emphasis on propeller, landing-gear, corrosion, and regional-operation maintenance evidence than a typical narrowbody review.
• propeller and regional-operation evidence can be decisive at transfer, so source evidence is more useful than a summary status line.
• AD status review for this family should connect the asset configuration to the exact source documents being relied on.
• ATR 72 AD status findings should be read against the family pattern: ATR 72 records place more emphasis on propeller, landing-gear, corrosion, and regional-operation maintenance evidence than a typical narrowbody review. That context changes which missing source record deserves the first recovery attempt.
• For turboprop aircraft, AD status list entries are most useful when they name the affected serial number, configuration point, or maintenance-program assumption rather than only the document title.
• ATR 72 reviews should distinguish fleet-wide assumptions from asset-specific evidence, especially where an AD is marked closed without the accomplishment record behind it.
• The closure plan should explain how the accomplishment entry and method of compliance for the affected serial number supports propeller and regional-operation evidence can be decisive at transfer for the exact aircraft, engine, or component under review.
• ATR 72 records packages often pass through several holders; a serious review states whether applicability notes, accomplishment records, and method-of-compliance evidence came from the operator, shop, lessor, owner representative, or scanned archive.
• The family-specific question is whether ad applicability and closure can be defended on this turboprop aircraft after configuration, utilization, and program history are considered together.
• A atr 72 airworthiness directive status records review should preserve how operator archive and shop-visit file were compared, because task-level sign-off and part-number identity usually decide whether the status can travel to the next reviewer. The file should show when the team chose to reconcile dates and cycles, when it chose to correct the binder index, and where which party can still supply the missing record. That level of detail turns the work into a configuration support note rather than another unexplained exception list.
• The strongest version of this review names the document path from component history folder to maintenance-control export, then marks method-of-compliance support, utilization carry-forward, and approval-basis trace as separate checks. If the answer is incomplete, the closeout should attach the approval reference and split commercial exposure from records recovery before anyone relies on the status. The practical test is whether the gap changes the next technical acceptance decision and how the finding affects the receiving maintenance program.
• For this specific records page, the useful handoff is a serial-number evidence chain that states whether the record can be explained without new maintenance work. It should avoid mixing document recovery with acceptance judgment: document the receiving-context note belongs in the recovery lane, while which status entry would change if the evidence fails belongs in the risk note. That separation helps the next asset, fleet, or transaction team read the evidence without reconstructing the review history.
• The page is intentionally scoped around atr 72 airworthiness directive status records review, so the record package should be checked for task-level sign-off before it is treated as ready. A good closeout leaves a transfer package addendum and a corrected index reference, with enough context to show why the team used component history folder instead of a derived status line. That is the difference between a recoverable document gap and an unresolved records position.
• atr 72 airworthiness directive status records review starts with airframe logbook set and release-certificate archive because the useful question is how the finding should be separated from valuation judgment. For ATR 72, the reviewer should test installed-configuration alignment before accepting ad status list; otherwise asset management receives a status line that cannot explain which record created it.
• On ATR 72, ad compliance status should be treated as a configuration-controlled trail. The review compares task-level sign-off with method-of-compliance support, asks what status can safely be used while evidence is pending, and uses a reviewer-readable trail to show why reconcile dates and cycles is the next practical step.
• turboprop aircraft work changes the evidence boundary for atr 72 airworthiness directive status records review. A useful package does not merge seller data-room index with operator archive; it marks approval-basis trace, names the source holder, and leaves a receiving-party evidence map when which party can still supply the missing record.
• For aircraft-family records review, the weak point is often the handoff between shop-visit file and component history folder. atr 72 airworthiness directive status records review should therefore check work-package closeout, return-condition mapping, and ad status list together before the team decides to split commercial exposure from records recovery.
• FAA and EASA records review for atr 72 airworthiness directive status records review should not hide document custody inside a general discrepancy note. It should state whether the record can be explained without new maintenance work, document defect-disposition history, and return a source-to-status table that can travel with the next data room or handback package.
• When asset management relies on ad compliance status, the package needs a reader to see index-to-source trace without re-opening the entire archive. The practical closeout is update the discrepancy register, followed by a redelivery condition attachment for the affected serial number, asset, or work package.
• atr 72 airworthiness directive status records review is credible only if the exception language names the actual evidence gap. The reviewer should separate operator archive from shop-visit file, test return-condition mapping, and answer which party can still supply the missing record before the finding becomes a commercial condition.
• The final package for ATR 72 should make ad compliance status usable by someone outside the original review team. That means defect-disposition history is recorded beside maintenance-control export, how the finding affects the receiving maintenance program is answered directly, and split commercial exposure from records recovery is not confused with acceptance of residual risk.
• A serious atr 72 airworthiness directive status records review review distinguishes recovery work from acceptance work. lease-return register may solve index-to-source trace, but a source-to-status table still has to say whether which status entry would change if the evidence fails before the record set is used for transfer, audit, or valuation.
• For turboprop aircraft, ad status list can be misleading when the source package is spread across operators, shops, and scanned folders. The review checks revision control, asks what the next reviewer would ask first, and keeps update the discrepancy register tied to the document that supports it.
• atr 72 airworthiness directive status records review should leave a narrow finding, not a broad concern. The narrow version identifies technical acceptance log, checks installed-configuration alignment, explains how much of the chain is source-supported today, and converts the issue into an induction baseline entry that a later reviewer can audit.
• The most useful output for asset management is not another status extract. For atr 72 airworthiness directive status records review, it is a document-owner matrix showing where engine records pack supports ad compliance status, where undefined remains open, and when the team should route the question to engineering.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits