AD/GENERAL/82 Amdt 2 - Repair Assessment of Pressurised Fuselages

The AD is short and operates largely by reference. The principal concepts in the instrument are:

• Applicability by reference: The AD applies to "Transport Category aircraft listed in the Requirement document." The AD does not itself list individual aircraft types or serials; those details are held in the Requirement document that accompanies the AD. That document also contains the specific flight‑cycle implementation dates that determine compliance windows.

• Incorporation into a CASA‑approved System of Maintenance: The operative action is to "Incorporate repair assessment guidelines for the fuselage pressure boundary into the CASA approved System of Maintenance for the aircraft." This means the repair assessment guidance becomes part of each affected operator’s maintenance system that has CASA approval.

• Reference to an external regulatory standard: The Requirement explicitly ties the form or substance of the incorporation to "Federal Aviation Administration 14 CFR Part 121.1107 (a)." The AD also notes that "FAR Part 121.307(a) is now FAR Part 121.1107 (a)," recording a renumbering.

• CASA approval substitution: The AD contains an express interpretive instruction: "References made in the Requirement document text to 'FAA approval of repair assessment guidelines', shall be read as 'CASA approval of repair assessment guidelines'." That instruction changes the locus of approval from FAA to CASA where the Requirement document uses FAA phrasing.

• Guidance vs mandatory content: The AD identifies FAA Advisory Circular AC 120‑73 as "available to provide guidance for operators of affected aircraft." The AD does not make the AC mandatory, but it signals that AC 120‑73 is a recognised source of technical guidance.

• Damage‑tolerance based supplemental inspection programme: The Background states the objective of the repair assessment guidelines is to "establish a damage‑tolerance based supplemental inspection program for repairs" with the goal of detecting damage before a repaired area’s load‑carrying capability is compromised below airworthiness standards.

• Amendment history and cross‑reference corrections: The AD records that Amendment 1 changed terminology from "repair assessment programs" to "repair assessment guidelines," updated references to FAA regulations and AC 120‑73, and moved compliance date specification into the Requirement document. Amendment 2 updates the reference to the Requirement document.

These concepts show the AD’s mechanics: it is directive on content to be integrated into operator maintenance systems, it requires domestic (CASA) approval of the resulting guidelines even when the Requirement document references FAA approval, it points to an FAA AC for technical guidance, and it relies on the Requirement document for the list of affected aircraft and specific compliance timing.

The AD is directed at operators of transport‑category aircraft identified in the Requirement document. The Applicability field states: "Transport Category aircraft listed in the Requirement document." Because the AD does not itself enumerate aircraft, an operator must consult the associated Requirement document to determine whether its aircraft types or specific airframes are subject to the directive.

The party that must take the action is the operator who holds a CASA‑approved System of Maintenance for the aircraft. The Requirement instructs operators to "Incorporate repair assessment guidelines for the fuselage pressure boundary into the CASA approved System of Maintenance for the aircraft," which places the primary operational obligation on the operator responsible for maintenance of the affected aircraft. Note 1 clarifies that any language in the Requirement document referring to "FAA approval" should be interpreted as requiring "CASA approval of repair assessment guidelines." That means CASA is the approving authority for the incorporated guidelines.

CASA itself is implicated as the approving body; the AD’s Note 1 expressly requires CASA approval in place of FAA approval where the Requirement document refers to FAA approval. The AD also implicitly involves maintenance organisations and engineers who prepare or implement the System of Maintenance documentation and the repair assessment guidelines, because the AD requires incorporation into the System of Maintenance and CASA approval of those guidelines.

The Background references other authorities and stakeholders. It records that the AD is the result of "FAA concern" for aircraft that are approaching or exceeding their design service goal. It also notes that the French DGAC "has mandated similar requirements for applicable French aircraft." Thus foreign operators or registrants operating under or sharing maintenance practices with French or US oversight may find harmonised regulatory expectations.

Who pays: the AD requires operators to incorporate and obtain CASA approval of repair assessment guidelines. The most immediate and direct cost and operational burden therefore falls to affected operators and their maintenance organisations, because they are the parties responsible for updating and obtaining approval for their System of Maintenance.

Who decides: the operator drafts and incorporates the guidelines; CASA decides whether the incorporation meets approval requirements, per Note 1’s substitution of CASA approval for any FAA approval references in the Requirement document.

Key duties established by the AD, as expressed in the Requirement and Notes, are concrete and limited in scope:

• Duty to incorporate repair assessment guidelines: The principal duty is to "Incorporate repair assessment guidelines for the fuselage pressure boundary into the CASA approved System of Maintenance for the aircraft" (Requirement). That duty is a directive to change the content of an operator’s approved maintenance system so that repair assessment guidelines for the pressurised fuselage are included.

• Duty to comply in accordance with a specified regulatory standard: The Requirement links the incorporation to "Federal Aviation Administration 14 CFR Part 121.1107 (a)." The AD also records a historical renumbering: "FAR Part 121.307(a) is now FAR Part 121.1107 (a)." The presence of the 14 CFR reference indicates that the form or procedural expectations set out in that US regulation are the standard against which the incorporation is to be made, subject to CASA approval per Note 1.

• Duty to obtain CASA approval: Note 1 provides that references in the Requirement document to "FAA approval of repair assessment guidelines", shall be read as "CASA approval of repair assessment guidelines." The operative effect is that operators must secure CASA approval for the incorporated repair assessment guidelines.

• Duty to meet the compliance timing in the Requirement document: The Compliance field requires incorporation "Before the applicable flight cycle implementation time and date specified in the Requirement document." This places temporal obligations on operators tied to flight cycle thresholds set out in the Requirement document.

Rights and procedural aspects visible in the AD text:

• Use of guidance material: Note 2 states that "FAA Advisory Circular AC 120‑73 is available to provide guidance for operators of affected aircraft." The AD thus affords operators the right to rely on AC 120‑73 as a recognised source of technical guidance when producing repair assessment guidelines. The AD does not make the AC mandatory; it is referenced as "available to provide guidance."

• CASA approval process: While the AD requires CASA approval (Note 1), the AD does not specify the procedural mechanics of that approval process or any appeal / review rights. The absence of procedural detail means the operator’s opportunity to shape and negotiate the content of the guidelines rests on the existing CASA approval framework for a System of Maintenance, but the AD text does not describe specific rights of review, timelines or conditions.

• Flexibility in document drafting: The AD instructs incorporation "in accordance with" the cited regulation and points to an advisory circular for guidance, which together indicate a standard plus fallback guidance approach. Operators can draw on AC 120‑73 for content and methodology, subject to CASA approval.

The AD does not state sanctions, enforcement measures, or rights to seek exemption. It also does not describe record‑keeping details, inspection intervals, or the format of the repair assessment guidelines. Those specifics are left to the Requirement document, the referenced 14 CFR provision, and CASA’s approval process.

The supplied AD text does not specify penalties, enforcement mechanisms, or sanctions within the document itself. The Compliance entry sets a temporal obligation: "Before the applicable flight cycle implementation time and date specified in the Requirement document." The AD also records an effective date: "This Amendment becomes effective on 30 July 2009." Beyond these timing provisions, the AD contains no express section detailing penalties, infringement provisions, or enforcement procedures.

Because the AD requires incorporation into a "CASA approved System of Maintenance," the AD operates through the maintenance approval framework. Note 1 instructs that references to "FAA approval" in the Requirement document be read as "CASA approval of repair assessment guidelines." That substitution indicates that CASA is the approving authority and therefore the agency whose certification and oversight mechanisms will be implicated in assessing compliance. The AD does not, however, set out CASA’s enforcement powers or the consequences of failing to obtain CASA approval; those mechanisms, if any, are not included in the text supplied.

The Background refers to safety objectives and international counterparts (FAA and DGAC) but does not add enforcement detail. The AD’s administrative metadata includes a delegate signatory: "David Villiers, Delegate of the Civil Aviation Safety Authority, 17 June 2009." The presence of a delegate signature is the instrument’s formal authorisation, but the AD does not articulate any additional enforcement process deriving from that signature.

Practically, the absence of penalties or explicit enforcement language in the AD text means readers must look to broader CASA regulatory instruments and the Requirement document for details on compliance monitoring and consequences. The AD itself imposes duties and timing, but it leaves enforcement modalities and penalties , if any , unspecified in the supplied material.

The AD is expressly cross‑referential and interacts with several external regulatory instruments as described in the text:

• Federal Aviation Administration regulation 14 CFR Part 121.1107(a): The Requirement instructs incorporation "in accordance with Federal Aviation Administration 14 CFR Part 121.1107 (a)." This creates an interaction where the form or requirements of that US regulation are the technical standard the AD uses to shape the content of the repair assessment guidelines that must be adopted domestically. The AD also records renumbering: "FAR Part 121.307(a) is now FAR Part 121.1107 (a)." The effect is to import, by reference, aspects of the FAA standard into the domestic obligation for the content of repair assessment guidelines, while simultaneously directing that any reference to FAA approval in the Requirement document should be read as CASA approval (Note 1).

• FAA Advisory Circular AC 120‑73: Note 2 states AC 120‑73 "is available to provide guidance for operators of affected aircraft." The AD thus positions AC 120‑73 as a non‑mandatory but recognised technical guidance document that operators may use when drafting the required repair assessment guidelines.

• French DGAC mandates: In the Background the AD records that "The DGAC has mandated similar requirements for applicable French aircraft." This indicates policy harmonisation or alignment with French regulatory measures but does not create a legal obligation under Australian law; it documents that similar regulatory action exists elsewhere, which may be relevant to international operators or leasing arrangements.

• CASA regulatory framework: Note 1 makes clear that where the Requirement document used the term "FAA approval," this must be read as requiring "CASA approval of repair assessment guidelines." That substitution establishes direct interaction between the AD and CASA’s domestic approval processes for Systems of Maintenance and technical documentation.

• Requirement document as instrument of specification: The AD interacts with the Requirement document in two ways. First, the Requirement document lists the specific aircraft to which the AD applies (Applicability). Second, it sets "the applicable flight cycle implementation time and date" that determines compliance timing. Because those details are in the Requirement document rather than the AD text, the AD’s legal effect is mediated by a separate instrument. The AD therefore must be read in tandem with that Requirement document for full effect.

The AD does not reference other Australian statutes, administrative penalty provisions, or criminal provisions. It does not specify how CASA’s enforcement powers under other aviation statutes interact with the AD. Readers must consult CASA’s broader regulatory framework and the Requirement document to understand enforcement, approval procedures, and any interactions with other Australian aviation law instruments. The text supplied documents the AD’s cross‑references to FAA regulations and guidance and the procedural substitution of CASA approval where FAA approval language appears.

The AD includes an internal amendment history summarised in the Background. Key historical points appearing in the text are:

• Original issue effective date: The Background records that "The original issue of this Airworthiness Directive became effective on 10 August 2000." That identifies the AD’s initial entry into force.

• Amendment 1: The Background states that "Amendment 1 updated the requirement document and the notes to reference US Federal Aviation Regulation 121.370 and the associated Advisory Circular AC120‑73." It further states that reference to "repair assessment programs" was changed to "repair assessment guidelines" "to be consistent with the requirement document." Amendment 1 also "altered the compliance to remove the date, which is now specified in the requirement document." Those changes show that Amendment 1: (a) updated cross‑references to US CFR material and AC 120‑73, (b) replaced the term "programs" with "guidelines," and (c) moved exact compliance dates into the Requirement document.

• Amendment 2: The AD at hand is "AD/GENERAL/82 Amdt 2" and the Background notes that "Amendment 2 updates the reference to the requirement document." The header itself is dated "8/2009" and the Compliance field states "This Amendment becomes effective on 30 July 2009." Amendment 2 thus appears to be an updating instrument that refreshes the Requirement document reference and thereby refreshes the list of affected aircraft and/or compliance dates as contained in that document.

• Renumbering note: The AD contains an explicit note outside the Background: "FAR Part 121.307(a) is now FAR Part 121.1107 (a)." This records a regulatory renumbering in the external (FAA) instrument and the AD’s awareness of that change.

The AD therefore shows a sequence: original AD effective 10 August 2000; Amendment 1 updated terminology and reference to FAA instruments and moved compliance dates into the Requirement document; Amendment 2 updated the Requirement document reference and was effective 30 July 2009. The text does not supply earlier drafts, the full Requirement document contents, or any later amendments beyond Amdt 2.

The supplied document contains no record of litigation, judicial review, administrative appeals, or legal challenges. The AD’s Background and metadata mention only regulatory sources (FAA, DGAC) and the delegate signature "David Villiers, Delegate of the Civil Aviation Safety Authority, 17 June 2009." There is no mention of legal proceedings, court decisions, or tribunal findings in the text provided.

Where litigation history is absent from an AD text, interested parties should not infer litigation status from silence; to determine whether any legal challenges exist against this AD or its Requirement document, practitioners must consult court databases, administrative records, or CASA records outside the supplied document. The AD itself does not contain or reference any case law or dispute resolution outcomes.

The AD contains several details and drafting features that create practical risk points and potential sources of confusion for operators. These are concrete points drawn from the text:

• Applicability is externalised: The AD’s Applicability is "Transport Category aircraft listed in the Requirement document." The AD does not include an embedded list of affected types or serial ranges. Practitioners must obtain and read the separate Requirement document to identify whether a particular aircraft falls within the AD’s scope and to learn the specific flight‑cycle thresholds that trigger compliance.

• Compliance timing is set in the Requirement document: The Compliance section instructs operators to comply "Before the applicable flight cycle implementation time and date specified in the Requirement document." Failure to consult the Requirement document could result in missed compliance deadlines because the AD itself does not state a uniform date or flight‑cycle threshold.

• CASA approval substitution: Note 1 mandates that references to "FAA approval" in the Requirement document be read as "CASA approval." Operators that read the Requirement document literally could be misled unless they apply Note 1. Practically, this means operators must submit repair assessment guidelines to CASA, not FAA, for approval even when the Requirement document language refers to FAA approval.

• Guidance vs requirement distinction: Note 2 states that "FAA Advisory Circular AC 120‑73 is available to provide guidance." The AC is guidance, not a mandatory prescription in the AD. Operators must distinguish between the AD’s mandatory incorporation obligation and the advisory role of the AC.

• Terminology change from "programs" to "guidelines": Amendment 1 expressly changed "repair assessment programs" to "repair assessment guidelines." That change suggests the AD contemplates documentation and guidance to be integrated into the System of Maintenance rather than a standalone mandated programme. However, the Background still states the purpose is to "establish a damage‑tolerance based supplemental inspection program for repairs" which could cause interpretive friction between the notion of a "guideline" and the operational reality of an inspection programme. Practitioners should be explicit in their documentation about how the "guideline" produces enforceable inspection tasks and intervals, consistent with CASA approval expectations.

• Cross‑jurisdictional references and renumbering: The AD links to FAA 14 CFR Part 121.1107(a) and records renumbering ("FAR Part 121.307(a) is now FAR Part 121.1107 (a)"). Users must ensure they are looking at the correct and current regulatory paragraph in the FAA material when using it as a standard or reference, and then map its approval language to CASA per Note 1.

• Document quality and typographical repeats: The supplied AD contains repeated headings and some typographical concatenations (for example repeated "Repair Assessment ofPressurised Fuselages" with a missing space). Those features can complicate document management and reference. Practitioners should rely on the authoritative Requirement document and CASA communications rather than copying header text verbatim.

• No penalties or enforcement mechanisms in the AD text: The AD does not specify penalties or enforcement procedures. Parties should not assume the AD is unenforceable; rather, they should seek the relevant enforcement authorities and statutory frameworks (not contained in the supplied text) to understand consequences of non‑compliance.

• International operator implications: The Background notes the DGAC mandate for French aircraft. Operators with cross‑registry operations, leasing arrangements or maintenance shared across national boundaries should confirm which jurisdiction’s requirements apply and whether multiple approvals (CASA, DGAC or lessee state) are required.

These "gotchas" flow directly from the AD’s structure: heavy reliance on an external Requirement document for scope and timing, explicit substitution of CASA for FAA approval, and the presence of guidance rather than prescriptive technical content within the AD itself. Practitioners must obtain the Requirement document, align submissions to CASA approval processes and explicitly document how the incorporated guidelines create an effective damage‑tolerance inspection programme.

The AD sets a specific, limited compliance path. Based strictly on the text supplied, the practical steps to compliance are:

1. Obtain the Requirement document referenced by this AD. The Applicability and Compliance provisions make clear two critical items live in that document: (a) the list of "Transport Category aircraft" to which this AD applies, and (b) the "applicable flight cycle implementation time and date specified in the Requirement document" that determines the operator’s compliance deadline. The AD does not include those details, so the first compliance step is to obtain and review the Requirement document.

2. Determine applicability for each aircraft in your fleet. The AD’s Applicability clause instructs that it applies only to "Transport Category aircraft listed in the Requirement document." Do not assume universal applicability; confirm whether your aircraft type and serial numbers are listed.

3. Draft repair assessment guidelines for the fuselage pressure boundary. The Requirement requires operators to "Incorporate repair assessment guidelines for the fuselage pressure boundary into the CASA approved System of Maintenance for the aircraft in accordance with Federal Aviation Administration 14 CFR Part 121.1107 (a)." Draft the guidelines to address damage‑tolerance based supplemental inspection needs for repaired fuselage pressure boundary areas, consistent with the stated Background objective of establishing an inspection programme to detect damage before load‑carrying capability is degraded below applicable airworthiness standards.

4. Use AC 120‑73 as technical guidance where appropriate. Note 2 states "FAA Advisory Circular AC 120‑73 is available to provide guidance for operators of affected aircraft." Use AC 120‑73 for technical methodology and example practices, but remember AC 120‑73 is guidance , the AD requires incorporation into a CASA‑approved System of Maintenance.

5. Seek CASA approval. Note 1 requires that any reference to "FAA approval of repair assessment guidelines" in the Requirement document be read as "CASA approval of repair assessment guidelines." Therefore, submit the drafted repair assessment guidelines to CASA as an amendment or addition to your CASA‑approved System of Maintenance, and obtain written CASA approval in accordance with CASA’s existing processes. Maintain records of the submission and the approval.

6. Implement the approved guidelines before the specified flight‑cycle implementation time and date. The Compliance clause requires incorporation "Before the applicable flight cycle implementation time and date specified in the Requirement document." Once CASA approval is obtained, implement the inspection tasks and associated record keeping in operational practice by the required flight‑cycle deadline.

7. Document the integration and inspection programme in the System of Maintenance. Because the AD requires incorporation into the CASA‑approved System of Maintenance, ensure the System of Maintenance documentation is updated to include the repair assessment guidelines, inspection intervals, criteria for continued service, and any required training or maintenance procedures. Retain evidence of CASA approval and the date of incorporation.

8. Coordinate with stakeholders involved in maintenance and continued airworthiness. Operators should ensure that their maintenance organisations, base maintenance providers, and continuing airworthiness engineers understand the new guidelines and how they map to inspection tasks and defect reporting. The AD’s Background emphasises damage‑tolerance supplemental inspections for repaired areas; translate the guidelines into operational maintenance tasks.

9. Monitor for amended Requirement documents or further AD amendments. Amendment history shows the Requirement document and cross‑references have been updated in the past (Amendment 1 and Amendment 2). Confirm that you are working from the latest Requirement document and AD amendment so that the list of affected aircraft and compliance dates are current.

10. Archive and audit compliance evidence. The AD does not specify enforcement in the supplied text. As a procedural matter, retain approvals, revised System of Maintenance documents, training records, inspection results and correspondence with CASA to demonstrate compliance should CASA request evidence.

These steps are drawn directly from the AD’s Requirement, Notes and Compliance text. The AD does not prescribe inspection intervals, allowed repair sizes, analysis methods or record forms; those technical details should be developed consistent with 14 CFR Part 121.1107(a) as cited, and AC 120‑73 where useful for guidance, and must be acceptable to CASA under the System of Maintenance approval process (per Note 1).