AD/S-PUMA/83 - Hinged Door Upper and Lower Catches

The AD rests on a small set of tightly defined technical and procedural concepts drawn from Eurocopter service guidance and EASA oversight. The principal concepts are:

• Applicability by configuration and delivery date. The AD applies only to specified AS 332 models "if equipped with hinge doors and delivered before 1 August 2007" (Applicability). Applicability therefore depends on a combination of airframe model, physical configuration (presence of hinged doors) and a completed manufacture/delivery date. The text does not define "delivered" further.

• Visual inspection standard anchored to an external service bulletin. The inspection is not free-form; it must be carried out "in accordance with the instructions of paragraph 2.B.2 of Eurocopter AS 332 ASB 52.00.38 original issue, or later EASA approved revision" (Requirement). The AD therefore imports the ASB's procedures and tolerances by reference rather than reproducing them.

• Conditional corrective work prescribed by reference. If any catch is improperly installed, the AD requires removal and reinstallation in accordance with paragraph 2.B.3 and 2.B.4 of the ASB, then adjustment of the door-open micro-switches and a functional check per paragraph 2.B.5 (Requirement). These paragraphs define the technical remedial steps; the AD makes them mandatory for affected helicopters.

• Baseline micro-switch adjustment and functional check. Even where no incorrect installation is found, the AD still requires adjustment of the micro-switches and a functional check per paragraph 2.B.5 before further flight (Requirement). Adjustment and functional testing are therefore universal within the applicable population; removal/reinstallation is conditional.

• Time-limited compliance window. The AD must be complied with within 220 flight hours or six months after 12 March 2009, whichever occurs first (Compliance). The AD also states it becomes effective on 12 March 2009, anchoring the start date for the compliance window (Compliance).

• Referential incorporation of EASA documents. The AD explicitly refers to Eurocopter ASB 52.00.38 (original issue) and allows "later EASA approved revision" to be used, and notes EASA AD 2009-0015 (Requirement; Note). The AD therefore operates in a regulatory ecology where the ASB and an EASA AD are procedural sources. The AD does not itself reproduce the ASB procedures.

• Safety rationale tied to possible in-flight door opening. The Background explains the trigger: a report that a rear hinged door opened in flight due to an incorrectly positioned door catch; the investigation found incorrect positioning leading to incorrect locking and uncontrolled opening, and the AD links this to potential in-flight loss of the door, possible damage to main or tail rotors and possible loss of control or risk to persons on the ground (Background).

These concepts show the AD functions by importing Eurocopter-prescribed maintenance procedures and imposing them on a defined subset of AS 332 helicopters within a short compliance timeframe. The AD does not specify penalties, recordkeeping protocols, or alternative methods of compliance within the text provided. It does not reproduce the ASB content; instead it makes compliance conditional on executing the ASB paragraphs named.

The AD directly addresses operators and maintainers responsible for the identified Eurocopter AS 332 helicopter models that meet the configuration and delivery-date criteria. Concretely, the affected parties include:

• Operators of AS 332 C, AS 332 C1, AS 332 L, AS 332 L1 and AS 332 L2 helicopters that were delivered before 1 August 2007 and are equipped with hinged doors (Applicability). The AD applies to "all serial numbers" of those models, subject to the configuration and delivery-date qualifiers. Therefore the pool is limited by delivery date and by whether the helicopter has hinge doors.

• Maintenance organisations and certificated personnel who will perform the inspection, any removal/reinstallation of catches, micro-switch adjustments and functional checks, because the AD mandates compliance "in accordance with" specific paragraphs of Eurocopter ASB 52.00.38 (Requirement). The AD therefore places procedural obligations on those who perform airworthiness work.

• Regulatory compliance units within operator organisations. Responsible managers will need to ensure scheduling of inspections within the 220 flight-hour or six-month window, ensure the proper ASB revision is used, and confirm that "before further flight" requirements are met (Compliance; Requirement).

Secondary but relevant parties include:

• Owners and financiers. While the AD addresses the operator/maintenance function, owners or financiers who control decisions about aircraft usage or maintenance budgets may be affected because the direction may impose a requirement that aircraft be taken out of service until the inspection and any necessary corrective work are completed.

• Supply chain and parts providers. If an inspection reveals catches that must be removed and reinstalled, parts availability, tooling and access to Eurocopter technical support may matter. The AD requires removal/reinstallation "in accordance with" ASB paragraphs, which may reference specific parts or tooling; the AD itself does not list parts (Requirement).

• National aviation authority staff. The AD was issued by the Civil Aviation Safety Authority (CASA) via its delegate (David Punshon) and refers to EASA AD 2009-0015, so regulatory staff coordinate the technical instruction and may manage oversight and enforcement (signed & dated lines; Note).

The AD does not identify any exemptions or alternate compliance pathways within the text provided. It does not state explicit recordkeeping obligations, nor does it allocate costs or specify who bears penalties for non-compliance. Those responsibilities follow from the AD's mandatory instruction to perform the work within the stated window and to complete required tasks "before further flight" after inspection or remediation (Requirement; Compliance).

Key duties imposed by the AD are concrete and process-driven. The directive sets out required actions, preconditions for flight, and timing constraints. The rights of addressees are not enumerated in the text; the AD focuses on mandatory obligations. The principal duties and any implied rights evident from the text are as follows:

Duties

• Determine applicability. Operators must first determine whether a helicopter is within the AD's scope: the model must be AS 332 C, C1, L, L1 or L2, be equipped with hinge doors, and have been delivered before 1 August 2007 (Applicability). This initial determination is a duty of the operator or maintainer.

• Perform the mandated visual inspection. The AD requires "Perform a visual inspection of the positioning of the rear and front lower door catches as well as the rear and front upper door catches" and expressly ties the method to paragraph 2.B.2 of Eurocopter ASB 52.00.38 original issue or a later EASA-approved revision (Requirement). The duty is both to inspect and to follow the ASB procedure cited.

• Execute conditional remedial work. If any catch is found improperly installed, the AD requires removal and reinstallation in accordance with paragraphs 2.B.3 and 2.B.4 of the ASB, then adjustment of the door-open micro-switches and performance of the functional check per paragraph 2.B.5. These remedial steps must be completed before further flight (Requirement).

• Perform micro-switch adjustment and functional check even when no defect is found. The AD requires micro-switch adjustment and functional check per paragraph 2.B.5 before further flight regardless of whether catches are improperly installed (Requirement). This makes at least part of the remedial sequence universal across applicable aircraft.

• Meet the compliance window. All the above must be completed within 220 flight hours or six months after 12 March 2009, whichever comes first (Compliance). The AD also states it becomes effective on 12 March 2009 (Compliance).

• Use approved ASB revision. The inspection and any corrective actions must be carried out "in accordance with" the named paragraphs of Eurocopter ASB 52.00.38 original issue, or a later EASA-approved revision. Using a non-approved or unreferenced revision would not meet the AD's textual requirement (Requirement).

Rights (as implied by the text)

• Right to rely on later EASA-approved ASB revisions. The AD explicitly allows the operator to use the "original issue, or later EASA approved revision" of the named paragraphs. This grants operators the right to implement any subsequent EASA-approved clarification or change to the ASB text in place of the original issue (Requirement).

• Right to consult the referenced EASA AD. The AD includes a note that "EASA AD 2009-0015 refers" (Note). This implies operators may consult the referenced EASA AD for further context or matching requirements. The AD does not, however, make the EASA AD itself a compliance substitute; it is listed as a reference.

• Procedural clarity but no listed variances. The AD provides a clear, process-based route to compliance through the ASB procedures. It does not, in the text provided, disclose an alternative method of compliance or a formal process for seeking a deviation or extension. Any such rights are not set out in this document.

The AD does not specify recordkeeping, reporting, or certification procedures within the text supplied. It also does not set out penalty clauses or explicit enforcement mechanisms. The clear operational duties are inspection, conditional reinstallation, micro-switch adjustment and a functional check, all completed within the stated time limits and, where applicable, before further flight.

The AD text supplied identifies the Civil Aviation Safety Authority as the issuing body through the signature block and indicates the date of signature. It specifies that "This Airworthiness Directive becomes effective on 12 March 2009" and sets mandatory compliance actions and timelines (Compliance; signed by CASA delegate). The document, however, does not specify monetary penalties, criminal sanctions, administrative fines, or the enforcement procedures that CASA may deploy for non-compliance.

What the instrument does provide relevant to enforcement is:

• A mandatory operational requirement. The AD sets mandatory maintenance and inspection tasks that must be completed within a defined compliance window ("within 220 flight hours or 6 months after 12 March 2009, whichever occurs first") and requires certain steps to be taken "before further flight" following inspection or remedial work (Requirement; Compliance). The use of "before further flight" establishes a flight-safety precondition that makes the work operationally binding.

• An issuing authority. The AD bears the signature of David Punshon as Delegate of the Civil Aviation Safety Authority and is dated 28 January 2009, which identifies an authoritative CASA delegate as the decision-maker for issuance (signature block).

• Referential enforcement levers. The AD refers to Eurocopter ASB 52.00.38 and to EASA AD 2009-0015. While the AD does not itself spell out enforcement steps, the incorporation by reference of a manufacturer ASB and EASA AD suggests compliance will be judged against those texts and the AD's time limits.

What the AD does not state

• No explicit penalties described. The AD text does not include any clause specifying fines, suspension, revocation of certificates, or other sanctions for non-compliance.

• No explicit enforcement process described. The AD does not set out how CASA will monitor compliance, whether operators must report completion, or what documentary proof is required. The AD likewise does not state whether and how rectification after discovery of non-compliance will be handled.

Practical inference based on the instrument

• The AD creates an obligation that must be met; the instrument itself provides the technical route to compliance but leaves the enforcement apparatus and sanctions out of the document text supplied. Entities responsible for compliance should therefore treat the AD as mandatory and should presume that CASA has administrative enforcement tools available even though the AD does not recite them. For avoidance of doubt, the AD text itself provides no express penalty or enforcement procedure to cite.

Users of this AD will need to consult CASA policy and regulatory frameworks outside this text to identify the administrative or legal remedies CASA may use for non-compliance and any formal reporting or documentation requirements that CASA expects post-completion.

The AD explicitly imports or references two external regulatory/technical instruments and therefore functions within a multi-source regulatory environment. The interactions stated in the AD are as follows:

• Incorporation by reference of a Eurocopter ASB. The AD mandates that the visual inspection and remedial work be carried out "in accordance with the instructions of paragraph 2.B.2 of Eurocopter AS 332 ASB 52.00.38 original issue, or later EASA approved revision" and further requires execution of paragraphs 2.B.3, 2.B.4 and 2.B.5 for removal/reinstallation, micro-switch adjustment and functional checks (Requirement). This creates a direct dependency: compliance with the AD requires following the named paragraphs of a manufacturer-issued service bulletin. The AD therefore interacts materially with the content and approvals of that ASB.

• Reference to an EASA Airworthiness Directive. The AD includes a note that "EASA AD 2009-0015 refers" (Note). This signals regulatory coordination with EASA: the CASA AD nods to an EASA AD addressing the same or related unsafe condition. The AD does not reproduce EASA AD 2009-0015 within its text but acknowledges it as relevant.

• Cross-jurisdictional conformity. By referencing an EASA AD and by permitting "later EASA approved revision" of the Eurocopter ASB, the AD creates a pathway for technical standards approved by EASA to be used to satisfy an Australian AD. The AD therefore interacts procedurally with EASA's approval process for revisions to the ASB.

What the AD does not state about interactions

• The AD text does not cite or amend any Australian Acts, regulations or specific CASA enforcement regulations. It does not quote or incorporate by reference Australian Civil Aviation Regulations or other domestic legal frameworks in the text provided.

• The AD does not define how conflicts between the ASB, the EASA AD, and CASA requirements would be reconciled. It simply requires compliance with the named ASB paragraphs and allows later EASA-approved revisions to be used.

Operational implications of the stated interactions

• Operators must ensure they have access to the correct ASB revision. Because the AD ties compliance to paragraphs in ASB 52.00.38 "original issue, or later EASA approved revision", the operator must source the appropriate ASB document and confirm whether any later EASA-approved revision is in force and whether that revision alters the procedures or tolerances.

• The AD’s reference to EASA AD 2009-0015 suggests that the same unsafe condition has been addressed at the EASA level. Operators operating across jurisdictions or under multiple authorities should compare the CASA AD requirements with the EASA AD to ensure consistent compliance, noting that the CASA AD prescribes compliance in the Australian context and imports the ASB provisions by reference.

• No express conflict resolution process is set out, so where an ASB revision approved by EASA post-dates the AD issuance, the operator may rely on the later EASA-approved revision as permitted by the AD text. Any other interactions with domestic aviation law or CASA enforcement practice are outside the text provided and must be checked against CASA’s procedural guidance.

In sum, the AD operates by directly incorporating manufacturer procedures and recognizing EASA approvals; it does not, within the text provided, directly amend or restate domestic regulatory statutes, nor does it provide a standalone technical method beyond reference to the ASB.

The AD text provided contains limited information about amendments and revision history. The material explicitly present in the document is:

• Effective date. The AD states it "becomes effective on 12 March 2009" (Compliance). That locates the AD’s operational commencement date.

• Signature and issue date. The AD is signed by David Punshon, Delegate of the Civil Aviation Safety Authority, and dated 28 January 2009. The signature date precedes the effective date; this indicates the AD was issued or signed prior to the effective date stated in the document.

• Reference to later EASA-approved revisions of the ASB. The AD allows the operator to perform required actions "in accordance with the instructions of paragraph 2.B.2 of Eurocopter AS 332 ASB 52.00.38 original issue, or later EASA approved revision" and similarly allows later EASA-approved revisions for the corrective paragraphs 2.B.3, 2.B.4 and 2.B.5 (Requirement). This clause creates a mechanism by which later EASA-approved revisions to the ASB are accepted for compliance purposes without needing an amendment to the AD text itself.

• Reference to EASA AD 2009-0015. The AD includes a note that "EASA AD 2009-0015 refers" (Note). The presence of that reference indicates coordination and that there is at least one corresponding EASA directive addressing the same unsafe condition. The AD does not, however, summarise any changes resulting from that EASA AD or indicate that the CASA AD was amended to track particular EASA AD content.

What is not in the text

• The AD as provided does not include any recorded amendments to the AD text itself, such as later variations, superseding AD numbers or revocations. There is no explicit amendment log printed in the supplied document.

• There is no textual record in this instrument of previous versions, revocations, extensions, or alternative method approvals. The AD does not provide a historical list of amendments or consolidations.

How to interpret the allowance for later EASA-approved revisions

• The AD’s express permission to use a later EASA-approved revision of the Eurocopter ASB functions de facto as an amendment mechanism limited to that external document. That means if EASA later approves revisions to paragraph(s) 2.B.2-2.B.5 of ASB 52.00.38, those revisions are expressly permitted for satisfying the AD’s procedural requirements without the AD itself needing to be reissued. The AD text therefore contains a narrowly scoped change-management mechanism but no recorded amendments to the AD itself.

If a reader needs a formal history of AD amendments, revocations or supersessions beyond what is printed in this document, they must consult CASA's official AD record or repository. The instrument as provided gives the initial effective date, the signature date and allows use of later EASA-approved ASB revisions, but it does not document any subsequent amendments to the AD text itself.

The text provided is an administrative Airworthiness Directive and does not include any judicial or quasi-judicial litigation history. Specifically:

• No cases cited. The AD includes no references to any judicial decisions, rulings, or challenges. The document contains no summary of litigation nor any mention of disputes or appeals.

• No administrative appeals or variations recorded. There is no indication within the AD text that the directive has been the subject of an administrative appeal, stayed, varied or otherwise legally contested.

• No enforcement proceedings recorded. The AD does not record any enforcement actions taken under its authority, nor does it reference outcomes of enforcement proceedings.

What the absence of litigation history in the text means practically

• The AD, as supplied, represents a technical and operational safety measure issued by a CASA delegate. The lack of litigation history in the document simply means the instrument itself does not record legal disputes. It does not prove that no litigation, challenge or dispute has occurred; it only means the document contains no such information.

• Users who need to know whether the AD has been the subject of legal challenge, or whether any judicial or administrative determinations have interpreted the AD, must consult case law databases, CASA records, or other legal repositories outside this text. The AD does not instruct how to access any appeal mechanism or record of litigation.

For current legal status, challenge history, or interpretation of legal obligations arising from the AD, affected parties should verify whether CASA later amended, superseded or withdrew the AD and whether any courts or tribunals have considered its validity or application. None of that material is included in the AD as provided.

This AD contains several practical pitfalls and implementation risks that operators, maintenance organisations and compliance managers should note. Each of these items is derived from the AD text and the way it frames compliance.

1. Applicability depends on configuration and delivery date. The AD applies only to helicopters "if equipped with hinge doors and delivered before 1 August 2007" (Applicability). A helicopter of the listed models but delivered on or after 1 August 2007, or one whose doors were modified post-delivery, may fall outside the AD. Operators must confirm delivery date records and current door configuration; delivery date ambiguity or incomplete records can create compliance uncertainty.

2. "All serial numbers" wording but with qualifiers. The AD says "all serial numbers" for the listed models, but the hook is the hinge-door configuration and delivery date (Applicability). The phrase may give an impression of blanket applicability, but the conditional qualifiers narrow the scope. Careful cross-checking of fleet delivery dates and modifications is required.

3. Reliance on external ASB paragraphs. The AD does not reproduce the inspection or corrective procedures; it requires compliance "in accordance with" paragraph 2.B.2 and paragraphs 2.B.3-2.B.5 of Eurocopter ASB 52.00.38 original issue, or later EASA-approved revision (Requirement). Operators must obtain the correct ASB and confirm the exact procedural steps and any parts, torque settings, tolerances or special tooling listed there. Failure to follow the specified paragraphs exactly could mean non-compliance with the AD.

4. "Before further flight" is an absolute operational precondition. The AD requires that, after inspection, either the remedial steps (if required) or the micro-switch adjustment and functional check (in all cases) be completed "before further flight" (Requirement). This can ground an aircraft until qualified maintenance completes the tasks and documents completion to the operator’s own safety management system.

5. Compliance window is short and measured in flight hours or months. The AD requires completion within "220 flight hours or 6 months after 12 March 2009, whichever occurs first" (Compliance). Operators must track both calendar time and flight hours from the effective date. Failure to schedule inspections promptly could force an immediate grounding to meet the "before further flight" requirement as the window closes.

6. ASB revisions approved by EASA permitted; uncertified revisions not permitted. The AD allows the use of "later EASA approved revision" of the ASB; it does not authorise using other manufacturer revisions not EASA-approved or other informal guidance. Operators must verify EASA approval status of any later ASB revision they intend to use.

7. Interplay with EASA AD 2009-0015. The AD notes that "EASA AD 2009-0015 refers" (Note). That EASA AD may contain parallel or supplementary requirements. Operators servicing aircraft across jurisdictions should reconcile any differences. The CASA AD does not elaborate on the EASA AD content.

8. No explicit recordkeeping or reporting requirement in the AD text. The AD does not state how to record completion or whether to notify CASA. Operators should not infer that no documentation is required; operational good practice and other regulatory obligations typically require records, but the AD does not specify them.

9. Signature date earlier than effective date. The AD is signed 28 January 2009, with an effective date of 12 March 2009. This interval may create confusion about when counting of the six-month window or 220-flight-hour window begins. The AD makes the effective date the anchor (Compliance), but users must be careful to use the stated effective date rather than the signature date.

10. Scope of "removal and reinstallation" may imply parts or downtime. The AD requires removal and reinstallation "in accordance with" ASB paragraphs if improper installation is found. That could require parts, tooling, or specialist labour; the AD does not state whether temporary measures or minor adjustments are acceptable. Operators must consult the ASB to determine exact tasks and parts involved.

11. Possible groundings if inspections identify defects late. Because required remedial work must be completed before further flight, identifying an improperly installed catch close to scheduled flights may cause unplanned ground time. Operators should plan inspections early within the compliance window to reduce operational disruption.

These "gotchas" are direct inferences from the AD's wording and its reliance on external ASB instructions. They highlight practical points where ambiguity, recordkeeping gaps, or operational timing can produce compliance risk.

The AD sets out a clear, reference-based compliance path. Below is a stepwise compliance checklist derived from the AD text for operators and maintainers. Each step cites the relevant part of the AD to show the textual basis.

1. Determine applicability (Applicability)

   • Check the helicopter model: confirm the aircraft is an AS 332 C, C1, L, L1, or L2.
   • Confirm door configuration: verify that the helicopter is equipped with hinged doors.
   • Confirm delivery date: verify the aircraft was delivered before 1 August 2007.
   • If any of the three conditions is not met, the AD as written does not apply.

2. Establish the compliance timeline anchor (Compliance)

   • Note the AD "becomes effective on 12 March 2009" and the required compliance action is "within 220 flight hours or 6 months after 12 March 2009, whichever occurs first."
   • Calculate the six-month calendar deadline from 12 March 2009 and compute flight hours remaining against 220 flight hours from that date to determine the controlling deadline.

3. Obtain the referenced documentation (Requirement)

   • Obtain Eurocopter AS 332 ASB 52.00.38 original issue, and confirm whether a later EASA-approved revision exists.
   • Confirm which ASB revision is EASA-approved for use; per the AD you may use the original issue or a later EASA-approved revision. Ensure the ASB contains paragraphs 2.B.2, 2.B.3, 2.B.4 and 2.B.5 and identify the content of each.

4. Perform the visual inspection per ASB paragraph 2.B.2 (Requirement)

   • Conduct the visual inspection of the rear and front lower door catches and rear and front upper door catches in accordance with paragraph 2.B.2 of the ASB.
   • Document findings precisely, noting any catches found "improperly installed" per the ASB's criteria.

5. If any catch is improperly installed, perform removal and reinstallation per ASB paragraphs 2.B.3 and 2.B.4 and then adjust micro-switches and functional check per paragraph 2.B.5 (Requirement)

   • Execute removal and reinstallation instructions exactly as described in 2.B.3 and 2.B.4.
   • After reinstallation, carry out adjustment of the “door open” indicating system micro-switches and perform a functional check in accordance with paragraph 2.B.5.
   • Completion of these remedial steps is required "before further flight."

6. If all catches are properly installed, adjust the micro-switches and carry out the functional check per ASB paragraph 2.B.5 before further flight (Requirement)

   • Even absent an improper installation, the AD still requires micro-switch adjustment and a functional check per paragraph 2.B.5 before further flight.

7. Complete actions within the compliance window and prior to any further flights where required (Compliance; Requirement)

   • Ensure all inspections and post-inspection remedial steps are completed within 220 flight hours or six months after 12 March 2009, whichever occurs first.
   • If remedial work is required as a result of the inspection, complete that remedial work and requisite functional checks before returning the helicopter to flight status.

8. Coordinate with accountable maintenance personnel and confirm qualifications (Requirement)

   • Ensure that maintenance actions are performed by appropriately qualified and certificated personnel capable of following the ASB procedures.

9. Maintain documentary evidence (implied)

   • While the AD text does not mandate specific recordkeeping, best practice and other regulatory obligations require documenting inspection results, any corrective actions taken (including the specific ASB paragraphs followed), dates, personnel performing the work, and evidence the functional check was completed. Keep these records available for audit and regulatory inquiry.

10. Reconcile with EASA AD 2009-0015 if operating across jurisdictions (Note)

• Review EASA AD 2009-0015 as referenced in the AD for any supplementary or clarifying requirements and ensure consistent compliance across jurisdictions.

11. Address parts, tooling and scheduling to avoid operational disruption (practical step)

• Anticipate that any detected improper installation may require parts, specific tools or additional labour. Schedule inspections early enough within the compliance window so that corrective work can be completed without causing avoidable flight cancellations or groundings.

12. Verify acceptable ASB revisions prior to implementation (Requirement)

• If using a later ASB revision, confirm it is EASA-approved, as the AD accepts only the original issue "or later EASA approved revision."

Following these steps, grounded in the AD's Requirement and Compliance text, fulfils the directive's obligations as stated in the supplied document. Operators should also consult CASA guidance and their own safety and compliance processes for any additional documentation, reporting or oversight obligations that may apply in practice.