AD/S-PUMA/72 - Fuselage - TGB Attachment Fittings

The AD revolves around a small number of technical and regulatory concepts, each of which determines how the obligation operates in practice.

Applicability. The AD is confined to particular aircraft types and serial numbers, and to aircraft equipped with the relevant fittings. The text is explicit: the affected models are AS 332 C, C1, L, L1 and L2, and affected serial numbers are those "below S/N 2680" together with S/N 9000 through S/N 9009 inclusive, provided the helicopter is "equipped with tail gear box (TGB) attachment fittings, all part numbers" (Applicability). The inclusion of "all part numbers" makes the directive independent of individual part-number variants of the fitting, so long as the fitting type is present on the helicopter.

Incorporation by reference. Rather than set out prescriptive maintenance steps, the AD prescribes compliance with the "technical requirements of French DGAC Airworthiness Directive (AD) UF-2007-027" (Requirement). This creates a cross‑jurisdictional compliance mechanism: CASA, via this Australian AD, makes adherence to a foreign regulator's technical directive mandatory for the identified Australian‑registered aircraft.

Technical failure mode. The background explains the mechanical mechanism of failure. A missing blind hole in the structure fitting leads to interference with the end of the threaded section of the TGB aft attachment bolt during scheduled maintenance, specifically observed at a "750-hour inspection." That interference can prevent the proper axial coupling of the TGB casing even when the torque applied to the bolt appears correct. The result is an insufficient axial tightening, which can damage the attachment and initiate cracks under the bolt head, potentially leading to loss of the TGB before its time between overhauls (TBO) and creating a severe flight‑safety hazard during take-off and landing (Background).

Inspection schedule reference. The AD refers to a maintenance check frequency at which the anomaly was found: the 750-hour inspection. While the AD does not change maintenance intervals, the background ties the discovery to that scheduled check, indicating the defect can manifest or be detected at that inspection stage.

Effective date and revised compliance. The AD sets an effective date and refers to a revised effective date in the requirements document. The instrument states it "becomes effective on 12 December 2007" and that the required actions are to be performed "as specified in the requirements document with a revised effective date of the 12 December 2007" (Compliance). This implies that the referenced DGAC AD had an effective date, and that CASA is aligning its own compliance schedule with that date.

Regulatory authorship. The AD is issued by an Australian regulator's delegate, identified in the text: "David Villiers, Delegate of the Civil Aviation Safety Authority" (signature block). That attribution indicates the issuing authority within Australia's aviation regulatory structure, though the instrument text itself does not set out enforcement mechanisms or any rights of objection or appeal.

Taken together, these concepts show that the instrument operates by identifying a narrow cohort of aircraft, mandating adherence to an external technical specification, and establishing a deadline by which the external-specification tasks must be completed, all anchored to a specific hazard: interference caused by a manufacturing anomaly that can prevent correct axial tightening of a TGB attachment bolt.

The AD’s plain applicability clause identifies the directly affected parties. Owners, operators and maintainers of Eurocopter AS 332 helicopters of variants C, C1, L, L1 and L2 are within scope if, and only if, two conditions are met: the helicopter’s serial number is either below S/N 2680 or within the range S/N 9000 to S/N 9009 inclusive, and the helicopter is equipped with the tail gearbox attachment fittings described in the AD (Applicability). The AD includes the caveat "all part numbers", meaning the obligation is not limited to specific part-number variants of the fitting; any TGB attachment fitting present on the identified helicopters falls within the AD.

Operators and maintenance organisations that service those helicopters are also directly affected. The background references discovery of the issue during a "schedule maintenance check (750-hour inspection)" which indicates that maintenance activities and inspectors who perform scheduled inspections are potential actors required to carry out the relevant detection and corrective work. Although the AD does not explicitly list maintenance providers, its technical requirement to act "in accordance with ... AD UF-2007-027" (Requirement) will necessarily involve those who carry out structural inspections and bolt torque/clearance checks.

Aircraft lessors, charter operators and end users who rely on affected airframes are indirectly affected because aircraft operability and regulatory compliance depend on the required work being completed. If the AD’s corrective steps render an aircraft unairworthy until completion, commercial operations will be disrupted.

Manufacturers and parts suppliers are implicated in a narrower way. The AD’s background attributes the root cause to a "manufacturing anomaly" , a missing blind hole in the structure fitting that provides clearance for the bolt (Background). The AD does not instruct manufacturers directly to take remedial steps beyond the technical instructions in the DGAC AD UF-2007-027, but the identification of a manufacturing anomaly is a data point that manufacturers and quality control functions must absorb and may prompt internal corrective action. The AD itself, however, does not require a manufacturer recall or specify any warranty or indemnity obligations.

Regulatory and administrative personnel are affected insofar as they must adopt and administer the AD. The AD bears the signature of "David Villiers, Delegate of the Civil Aviation Safety Authority" and has an effective date of 12 December 2007. That designation signals CASA's internal allocation of decision-making and responsibility for issuing the directive.

Finally, the AD also affects records and compliance systems within operator organisations. Although the AD text does not itself mandate specific record-keeping steps, operators who are subject to the requirement must be able to identify which of their fleet falls within the serial-number bands and whether the relevant fittings are installed, and then to demonstrate that the referenced DGAC actions have been completed by the effective date. The AD does not supply a compliance checklist; it requires identification and actions to be taken in accordance with an external technical document (Requirement, Compliance).

In summary, the primary parties who "pay" in practical terms are the owners and operators of the applicable AS 332 helicopters and the maintenance organisations they engage, because they must carry out inspections and corrective work dictated by the DGAC AD by the effective date stated in this CASA directive.

The AD establishes a single core duty, and it leaves other matters unspecified in the text provided.

Primary duty to comply with DGAC AD UF-2007-027. The declarative instruction is that affected operators must take "Action in accordance with the technical requirements of French DGAC Airworthiness Directive (AD) UF-2007-027" (Requirement). That duty is the operative legal obligation set out by the AD , CASA, by issuing this instrument, requires adherence to the technical steps detailed in the DGAC document.

Timing duty. The AD requires compliance "As specified in the requirements document with a revised effective date of the 12 December 2007" and states "This Airworthiness Directive becomes effective on 12 December 2007" (Compliance). The duty, therefore, is not open-ended; it is tied to the effective date, which sets the enforceable timeframe for completing the referenced actions or following the timing rules that the referenced document supplies.

Duty of applicability determination. Operators have a pre‑condition duty to determine whether the AD applies to their aircraft. The applicability provision is specific, and the operator must assess whether its airframe model and serial number fall within the specified ranges and whether the helicopter is "equipped with tail gear box (TGB) attachment fittings" (Applicability). This is a fact-finding obligation incumbent on owners/operators before deciding compliance steps.

Unspecified duties. The AD does not set out several commonly expected procedural duties. It does not, in the text provided, define record-keeping requirements, notification obligations to CASA upon completion, or mandatory grounding procedures. It also does not itself set out the specific inspection steps, torque checks, part replacements or modifications , these are delegated to the referenced DGAC AD. Consequently, an operator’s duty to undertake specific mechanical steps flows via the incorporated DGAC AD rather than from the Australian instrument itself.

Rights and procedural protections. The AD as published does not state any express rights of appeal, exemption, or application for an alternative means of compliance within the document’s text. It likewise does not provide express rights to delay or staging of compliance. Any rights an operator may have to seek an alternative means of compliance or an exemption would therefore have to be asserted under other statutory or regulatory mechanisms outside this instrument, not within the AD text. The AD does, however, implicitly grant the right to rely on the DGAC AD as the governing technical prescription; operators are not free to substitute other procedures unless those alternatives are accepted under other regulator-granted processes not described in the AD.

Delegation and authority. The AD is issued under the authority vested in the Civil Aviation Safety Authority, evidenced by the signature block indicating a delegate, "David Villiers" (signature block). This identifies who issued the AD and signals the administrative provenance of the requirement. The AD does not further describe the legal basis or the statutory provision under which the delegate acted; that basis is not included in the text provided.

Interim operational rights. The AD does not specify whether aircraft may continue to operate pending completion of the DGAC-prescribed actions. There is no explicit permission to continue operations, nor an explicit grounding order. Operators must therefore interpret the instrument in conjunction with their wider airworthiness obligations and the detailed instructions in the DGAC AD to determine whether operational restrictions apply, bearing in mind that the background identifies a safety risk sufficient to cause loss of the TGB (Background).

In short, the AD sets a single operative duty: follow DGAC AD UF-2007-027 for the specified aircraft, by the stated effective date. It does not itself set out ancillary procedural rights or remedies; those are outside the AD text and, if needed, must be sought via other regulatory or statutory channels.

The airworthiness directive text provided does not specify penalties, sanctions or the mechanics of enforcement. The instrument contains the operative requirements and the effective date, but it does not set out a penalty regime or enforcement steps within its text.

What the document does show. The AD is an instrument issued under the authority of the Civil Aviation Safety Authority, indicated by the delegate’s signature block, "David Villiers, Delegate of the Civil Aviation Safety Authority" dated 10 December 2007. The presence of a CASA delegate’s signature and an effective date "12 December 2007" (Compliance) indicates the directive is intended as an enforceable regulatory requirement. However, this AD does not include explicit references to statutory provisions imposing penalties for non-compliance, nor does it outline administrative processes for notices, rectification timelines, or infringement notices.

What is not in the AD. The following enforcement elements are absent from the text provided: (a) a statement of criminal or civil penalties for failure to comply; (b) instructions as to whether non-compliant aircraft must be grounded; (c) a process for notices of non-compliance or for CASA inspections; (d) a procedure for applications for alternative means of compliance or exemptions; and (e) a requirement to notify CASA when the work is completed. Those omissions mean that the AD itself does not supply the complete enforcement framework within this document.

Consequences for operators. The absence of penalty language in the text does not mean that non-compliance will be without consequence, but that any enforcement powers, penalties and processes must be derived from CASA’s statutory powers or other applicable aviation regulations not contained in this AD. The AD imposes a mandatory technical obligation , "Action in accordance with the technical requirements of French DGAC Airworthiness Directive (AD) UF-2007-027" , and the failure to comply with a CASA-issued AD would ordinarily be a matter for CASA enforcement under its broader statutory remit; however, the specific penalties and enforcement steps are not specified in the instrument text supplied.

Practical enforcement risks. From a compliance-risk perspective, operators should treat the AD as mandatory, and should be aware that the AD sets a clear effective date for compliance. The AD’s omission of an enforcement schedule or explicit penalties increases uncertainty concerning the precise enforcement procedure CASA might follow in any particular case, but it does not alter the operator’s duty to perform the required actions in accordance with the referenced DGAC AD by the effective date.

To determine concrete penalty exposure or enforcement avenues, interested parties would need to consult CASA’s enabling legislation, enforcement policy and any supplementary CASA guidance or communications that are not contained within this AD document. The AD text itself does not supply those enforcement mechanics.

This AD interacts with at least two distinct regulatory layers: the Australian regulatory instrument that CASA issues and the French DGAC technical directive that the AD incorporates by reference.

Incorporation of foreign regulator's instructions. The AD explicitly requires action "in accordance with the technical requirements of French DGAC Airworthiness Directive (AD) UF-2007-027" (Requirement). Functionally, the Australian AD imports the DGAC technical prescription into the Australian compliance framework for the identified aircraft. That creates a direct interface between Australian regulatory obligations and a foreign authority’s technical solution: Australian operators must perform the tasks the DGAC set out, as mandated by CASA. The AD thereby makes compliance with an external regulator’s AD a domestic requirement for the aircraft within the applicability bands.

Interaction with maintenance obligations. The background links the problem to a scheduled maintenance check, the "750-hour inspection," indicating that the defect can show up during routine maintenance (Background). Operators’ existing maintenance programmes and manuals will therefore intersect with the AD because the required actions must be integrated into the maintenance schedule. Whether that integration requires changes to manualised procedures, logbook entries, or maintenance planning will depend on operators’ internal compliance systems and on the content of the DGAC AD.

Relation to CASA’s broader regulatory powers. The AD is issued by a CASA delegate and becomes effective on a stated date (Compliance). The AD itself does not state the statutory provision it rests upon. Accordingly, the broader interaction between this AD and CASA’s enabling legislation, such as enforcement powers or approval processes for alternative means of compliance, is not set out in the text provided. Those statutory mechanisms will exist elsewhere in Australian aviation law and regulation, and this AD operates in concert with them, but the instrument does not itself explicate those links.

Non-duplication and precedence. The AD does not state whether it supersedes any prior Australian directives. It also does not say whether compliance with the DGAC AD will be taken as a complete discharge of Australian regulatory obligations for the issue in question, or whether CASA may require additional steps. The AD’s text is silent on these matters; in practice, operators would treat the CASA AD as the governing domestic requirement and follow the referenced DGAC instruction unless and until CASA provided further direction.

Implications for international operators and maintenance. Because the specified corrective action is in a French DGAC AD, maintenance organisations that operate across jurisdictions, or that obtain technical guidance from French documentation, will need to ensure that the DGAC document referenced is the exact document required by CASA, and that any translations, metric/imperial conversions or local approvals are properly addressed. The AD itself does not provide the DGAC document text, nor does it offer an Australian adaptation or translation.

No interaction with civil remedies or tort law stated. The AD’s text does not refer to civil liability, warranties, or tort-based claims that might arise from the defect. The identification of a manufacturing anomaly in the background may be relevant to potential civil claims, but those legal interactions are outside the document and not discussed in it.

In short, the AD operates by importing a foreign technical prescription into the Australian regulatory framework for specified aircraft and links to operators’ existing maintenance schedules, but it does not itself describe its legal relationship to CASA’s statutory enforcement powers, nor does it prescribe how compliance with the DGAC AD affects other domestic legal obligations.

The instrument carries limited amendment metadata within the text provided; the available entries are the AD reference lines, a compliance note referring to a "revised effective date," and the signature and dates.

Document identifiers. The AD is labelled in several places with the identifier "AD/S-PUMA/72" and the title "Fuselage - TGB Attachment Fittings" with a notation "2/2008 DM" (top table and repeated lines). The presence of "2/2008 DM" appears in the header block associated with the AD. The instrument repeats the AD identifier and the title across a series of header-like lines. These labels indicate the AD’s reference number, title and a version or issue identifier, but the AD text does not provide a running amendment log or an explicit explanation of what "2/2008 DM" signifies beyond its presence as part of the AD label.

Effective date and revised effective date. The AD states that actions must be carried out "As specified in the requirements document with a revised effective date of the 12 December 2007" and declares "This Airworthiness Directive becomes effective on 12 December 2007" (Compliance). The phrasing "revised effective date" implies that the referenced DGAC AD contained an original effective date which was subsequently revised to 12 December 2007, and that CASA’s instrument aligns with that revised effective date. The AD itself does not record any prior effective date or the nature of the revision.

Issuance and signature date. The AD is signed "David Villiers, Delegate of the Civil Aviation Safety Authority" and is dated 10 December 2007. That date precedes the effective date of 12 December 2007, which is typical for regulatory instruments that take effect shortly after issue. The AD does not include later amendment dates or superseding notices within the text provided.

Absence of subsequent amendments in the text. The document excerpt supplied does not show any later amendments, revocations or supersessions. There is no amendment history table, no version-control notes, and no explicit statement that this AD supersedes any prior ADs. The repeated headers and identifier lines appear to be formatting or publication artefacts rather than an amendment trace.

What to infer. From the language present, one can record these concrete points: (a) the AD carries the identifier AD/S-PUMA/72 and the title "Fuselage - TGB Attachment Fittings"; (b) it is associated with the notation "2/2008 DM"; (c) it was signed by the CASA delegate on 10 December 2007 and became effective on 12 December 2007; and (d) the compliance obligations are tied to a "revised effective date" of 12 December 2007 for the referenced DGAC AD. Beyond those explicit items, the AD text supplied contains no formal amendment history or record of subsequent changes.

Operators and maintainers seeking a complete amendment history or any post‑issue updates would therefore need to consult CASA’s AD register or other official sources outside the document provided to determine whether this AD was later amended, withdrawn or otherwise varied.

The AD document supplied contains no litigation history, judicial references or citations to cases. It does not mention any legal proceedings arising from the manufacturing anomaly, any enforcement actions, nor any judicial interpretation of the directive. The text is limited to the regulatory instruction, its applicability, the requirement to follow the DGAC technical directive, compliance timing, and a factual background on the defect.

Concrete absence of litigation references. The instrument does not name any cases, nor does it narrate any contested enforcement action. It makes no reference to judicial review, appeals, or litigation outcomes. Therefore, within the confines of this document, there is no litigation history to summarise or analyse.

Implications of the absence. The absence of litigation material in the AD itself means one cannot use this document to identify any court decisions on interpretation, challenges to the AD’s validity, or any precedential authority addressing the directive. It also means the AD does not provide guidance on how courts have treated the duty it imposes, or on any damages claimed in relation to TGB failures connected to the manufacturing anomaly described.

What parties should do if litigation context matters. If a stakeholder requires information about whether this AD has been the subject of litigation, or whether any adjudicated disputes have arisen connected to the manufacturing anomaly, those inquiries must be pursued outside this AD. Sources to consult would include court records, CASA enforcement records and industry notices, none of which are included in the text supplied.

Concluding note. The AD itself is a regulatory instrument and, as presented, contains no litigation narrative. Any analysis of legal exposure, precedent, or litigation risk therefore needs to be based on sources beyond this AD, because the AD does not record any such history.

The AD contains several features and omissions that create compliance traps, ambiguity and practical implementation risks. These are the concrete "gotchas" that appear directly from the text.

1. Narrow and potentially non-intuitive applicability bands. The AD applies only to specific AS 332 variants and to two serial-number bands: "serial numbers below S/N 2680" and "serial numbers from S/N 9000 (inclusive) to S/N 9009 (inclusive)" (Applicability). Operators must correctly determine serial-number categorisation. Confusion can arise in borderline cases where production numbering systems or registration data are ambiguous. The AD requires both a model match and a serial-number match, plus the presence of the specific TGB attachment fittings, so fleet managers must check all three conditions to determine applicability.

2. Applicability depends on installed fittings, irrespective of part number. The AD states "equipped with tail gear box (TGB) attachment fittings, all part numbers" (Applicability). That means even if a fitting has been replaced with a different part number, if it is a TGB attachment fitting it falls within scope. Operators that assume only particular part numbers are covered will be at risk; the AD is deliberately broad on part‑number coverage.

3. Required actions are external to the AD. The AD mandates action "in accordance with the technical requirements of French DGAC Airworthiness Directive (AD) UF-2007-027" (Requirement). The Australian AD itself does not include the technical steps. Consequently, compliance requires obtaining and applying the DGAC document. Failure to obtain the correct DGAC AD, or relying on an incorrect version, risks non-compliance.

4. Temporal precision and "revised effective date". The AD ties compliance to "a revised effective date of the 12 December 2007" and itself "becomes effective on 12 December 2007" (Compliance). That leaves little lead time for operators who only receive the AD close to its issuance date. The short interval between the delegate’s signature date (10 December 2007) and the effective date (12 December 2007) could create logistical strain in arranging inspections, parts and maintenance slots.

5. The detection mechanism may be masked by correct torque readings. The AD’s background warns that although the torque applied to the attachment screw may be correct, interference "does not enable correct axial tightening of the TGB casing, even if the torque load applied to the attachment screw is correct" (Background). That is a technical gotcha: standard torque checks alone may not reveal the deficiency, and operators relying only on torque values could miss the underlying interference condition.

6. The problem was discovered at a scheduled 750-hour inspection. The background connects discovery to a "schedule maintenance check (750-hour inspection)" (Background). Operators who do not use the same inspection schedule may not discover the problem at the same time, and must therefore proactively determine whether and when to inspect if their maintenance regime differs.

7. No enforcement mechanics, no record-keeping guidance in the AD. The AD does not set out penalties, notification obligations, or record-retention rules. The absence of procedural directions is a practical gotcha: operators must decide how to document compliance to evidence conformity in the event of subsequent regulatory inquiry. The AD does not prescribe what form proof of compliance should take.

8. Manufacturing anomaly identified, but no manufacturer-directed remedial obligation in the AD. The AD identifies a "manufacturing anomaly" as the cause but does not set out any direction for the manufacturer beyond the DGAC technical prescription. Parties might have expectations of manufacturer-assisted rectification or parts replacement; the AD does not obligate that. Any such assistance would need to be handled outside the AD.

9. Potential ambiguity over continuing operations. The AD does not expressly state whether aircraft must be grounded until the DGAC‑specified actions are completed. Given the background note that loss of the TGB could risk loss of the helicopter in take-off and landing, an operator must make an operational decision without explicit direction in the AD, creating legal and safety risk-management ambiguity.

10. The AD references a foreign document that must be relied upon. Practical issues follow: obtaining the exact DGAC AD UF-2007-027, ensuring correct interpretation of its technical instructions, and verifying any required parts or tools may involve foreign-sourced documentation or parts that are not immediately available domestically. The AD does not mitigate those logistical constraints.

Each of these points flows directly from the AD text. They identify places where operators and maintainers may be tripped by the AD’s structure, timing, or informational omissions, and where additional diligence is necessary to convert the obligation into compliant action.

The AD sets a narrow compliance pathway: identify applicability, obtain the referenced DGAC AD, and carry out the technical requirements by the effective date. Below is a stepwise, source‑grounded compliance checklist that follows from the AD text.

1. Determine applicability precisely. Start by checking the helicopter’s type and serial number against the AD’s Applicability clause: "AS 332 C, C1, L, L1 and L2 helicopters with serial numbers below S/N 2680 and helicopters with serial numbers from S/N 9000 (inclusive) to S/N 9009 (inclusive), and equipped with tail gear box (TGB) attachment fittings, all part numbers" (Applicability). Confirm whether the TGB attachment fittings are installed. This factual determination is the threshold for any further action.

2. Obtain the referenced technical requirements. The AD’s operative instruction is to act "in accordance with the technical requirements of French DGAC Airworthiness Directive (AD) UF-2007-027" (Requirement). Acquiring the correct version of DGAC AD UF-2007-027 is therefore mandatory. Operators should ensure they have the version of UF-2007-027 that corresponds to the "revised effective date" referred to in the AD, because the AD ties compliance to that date (Compliance).

3. Review the DGAC AD and map required tasks. Once the DGAC document is obtained, map the technical steps required (inspection procedures, borescope checks, part replacements, rework of blind holes, bolt replacement, or any other corrective tasks specified by DGAC). The CASA AD does not itself enumerate these steps; compliance depends on implementing the DGAC-prescribed actions.

4. Integrate with maintenance scheduling. The AD background notes discovery at a "750-hour inspection" (Background). If your maintenance programme uses an equivalent interval, plan to carry out the DGAC-required inspections at or before the next scheduled 750-hour check. If your inspection schedule differs, schedule a special inspection at the earliest practicable date consistent with the DGAC AD and the CASA effective date, which is 12 December 2007 (Compliance).

5. Consider inspection technique beyond torque checks. The AD warns that interference can prevent correct axial tightening "even if the torque load applied to the attachment screw is correct" (Background). Therefore, ensure that inspection and verification techniques address axial clearance and interference, not only torque readings. Follow the DGAC AD’s specifically prescribed detection methods.

6. Document actions and findings. Although the AD does not specify record-keeping in the text provided, operators should retain clear documentation showing the applicability determination, dates when DGAC-prescribed actions were performed, parts replaced or reworked, test results, and certificates or approvals of the maintenance organisation. This documentation will be the primary evidence of compliance if CASA or third parties inquire.

7. Coordinate with maintenance providers and parts suppliers. The DGAC AD may require specific parts, modifications or tooling. Engage maintenance organisations early to ensure availability and to allow for any lead times. Remember that the AD applies to "all part numbers" of the TGB attachment fittings, so replacement parts must be checked carefully for compatibility and for whether the DGAC AD specifies particular part remediation processes.

8. Consider operational restrictions during remediation. The AD does not state whether affected helicopters must be grounded pending corrective action. Given the safety risk described , possible loss of the TGB , evaluate operational risk and consider suspending flights for affected helicopters until the DGAC-mandated inspections or corrective actions are complete, consistent with organisational safety management systems and any regulatory guidance.

9. Check for CASA follow-up. The AD references the CASA delegate’s signature and an effective date, but provides no enforcement detail (Compliance, signature block). Operators should check CASA’s AD register or communications for any additional instructions, forms, or confirmation requirements related to this AD, such as filing evidence of compliance or applying for alternative means of compliance, none of which are detailed in the AD text.

10. Maintain situational awareness for amendments. The AD shows an identifier and the notation "2/2008 DM" and references a revised effective date. After completing the DGAC-prescribed actions, monitor CASA publications for any later amendments, superseding ADs or clarifications. The AD text provided does not include a full amendment history, so subsequent changes could appear elsewhere.

Following these steps implements the AD’s explicit requirements: determine if the AD applies, obtain and implement DGAC AD UF-2007-027, and complete the work in accordance with the stated effective date of 12 December 2007. The AD’s text does not provide alternative compliance processes, record formats, or enforcement details, so prudent operators will document compliance thoroughly and seek clarification from CASA where operational or legal uncertainty remains.