AD/DHC-1/21 Amdt 2 - Wing to Fuselage Attachment Links

This AD rests on a small set of interlocking concepts: applicability by production model and part number, a mandatory reference to a manufacturer technical note, a fixed compliance window tied to hours in service or the next Maintenance Release inspection, and the rationale of preventing chafing caused by misalignment.

• Applicability: The AD identifies English production (C1) all models and Portuguese (T Mk 20) production models (Applicability). The background clarifies that T Mk 20 inclusion is conditional: "depending on the wing attach fitting part number fitted to the aircraft. This part number will need to be determined by a physical inspection or aircraft records" (Background). The operative concept is therefore model-based but subject to part-number verification.
• Normative technical reference: Instead of prescribing the inspection and corrective steps within the AD text, the directive requires compliance "in accordance with British Aerospace T.N.S. No. 161, Issue 3, dated 1 August 1985" (Requirement). Therefore the AD functions as a legal hook that makes an external technical procedure mandatory for affected aircraft.
• Compliance timing: The AD sets a dual trigger: within "100 hours time in service after the effective date of this AD" or "at the next scheduled inspection for Maintenance Release issued after the effective date of this AD, whichever is the later" (Compliance). It also institutes an ongoing trigger: the action must be performed "at any time the wing attachment links are removed" (Compliance). These timing rules create both an initial compliance window and a continuing obligation linked to removal of the components.
• Rationale and risk addressed: The background cites reported cases of misfit and consequent chafing of structural members, and mentions that Amendment 1 reflected a revised shimming procedure in Issue 3 of the Requirement Document (Background). The AD’s technical objective is to prevent spar and tie bar chafing from misaligned attachment links.
• Amendment mechanics: The document is labelled "Amdt 2" and records that Amendment 1 revised requirements to reflect Issue 3; Amdt 2 extends applicability to Portuguese Chipmunks but leaves substantive requirements unchanged (Background). The AD becomes effective 21 June 2011 (Compliance).

From an incentives and cost-structure perspective visible in the text, the duty to perform the technical actions falls on those responsible for aircraft maintenance and airworthiness (operators and maintainers by implication), who must obtain and execute the British Aerospace technical note. There is a compliance burden in identifying correct part numbers by physical inspection or records, obtaining the T.N.S., and performing shimming/inspection actions within the specified hours or at the next Maintenance Release. The AD embeds procedural specificity without the technical detail, pushing technical implementation to the external manufacturer document. The AD thus centralises legal obligation while decentralising technical execution to maintenance organisations following the referenced technical standard.

The AD identifies a defined population of aeroplanes and the implied responsible parties who must act.

• Affected aircraft: The AD's Applicability line states it applies to "English production (C1) all models and Portuguese (T Mk 20) production models" (Applicability). The background expands on the T Mk 20 inclusion: whether a Portuguese-manufactured Chipmunk is captured depends on the wing attach fitting part number fitted to that aircraft (Background). Determination of capture for a T Mk 20 requires "a physical inspection or aircraft records" (Background).
• Responsible actors: The AD text does not list named categories (for example, "the owner" or "the operator") in statutory terms, but the obligations are framed as maintenance/airworthiness actions that must be carried out on the applicable aeroplanes. The Compliance wording prescribes timing relative to maintenance events ("next scheduled inspection for Maintenance Release") and component removal, which implies that the circle of affected parties includes the maintenance organisation signing Maintenance Releases and the person or entity responsible for scheduling and executing those maintenance actions. The signature by a CASA delegate (Glen Steemson) shows the issuing regulator but does not name enforcement addressees in the instrument itself.
• Records and inspection actors: Because the background requires part-number determination by "physical inspection or aircraft records" for Portuguese-manufactured Chipmunks (Background), custodians of maintenance logs and records, and personnel conducting physical inspections, are directly implicated. Accurate records or the capacity and access to perform a physical inspection are therefore necessary to establish whether a particular T Mk 20 airframe falls within the AD's ambit.
• Suppliers of technical information and parts: The AD makes British Aerospace T.N.S. No. 161, Issue 3, the operative technical standard (Requirement). Holders of, or access to, that document, and maintenance personnel who can apply its shimming procedure, are functionally affected.

Who pays and who decides, insofar as the AD text shows it: the operator or the party holding the aircraft's maintenance responsibility will need to arrange and pay for the inspection/shimming work and for obtaining the referenced technical instruction, and the maintenance authority signing the Maintenance Release will decide on timing relative to scheduled inspections. The AD itself assigns the action to "action in accordance with" the T.N.S., and sets the timing: those who schedule and conduct Maintenance Releases determine the actual date of compliance where the "next scheduled inspection for Maintenance Release" is used as the compliance trigger (Compliance).

The AD prescribes several discrete duties and leaves other legal rights or exceptions unspecified.

Duties expressly stated in the instrument:

• Follow the British Aerospace technical instruction: The AD requires "Action in accordance with British Aerospace T.N.S. No. 161, Issue 3, dated 1 August 1985" (Requirement). The duty is to carry out whatever actions that Requirement Document prescribes.
• Observe the compliance timing: The AD mandates the action be completed "Within 100 hours time in service after the effective date of this AD or at the next scheduled inspection for Maintenance Release issued after the effective date of this AD, whichever is the later" (Compliance). This creates a specific window for initial compliance.
• Perform the action whenever the wing attachment links are removed: The AD adds "and at any time the wing attachment links are removed" (Compliance). This introduces an on-going maintenance trigger that extends beyond the initial compliance window.
• Determine capture for Portuguese (T Mk 20) production models: For T Mk 20 aircraft, the AD requires those responsible to determine applicability by establishing the wing-attach fitting part number, either by physical inspection or via aircraft records (Background). This is a duty of verification where model status is ambiguous.

Rights or exemptions stated or implied:

• The AD text does not offer express exemptions, alternative means of compliance, or appeals procedures. The background explicitly says "There is no change to the requirements or compliance (except to require compliance after the effective date of this amendment)" (Background), indicating Amendment 2 did not create new waivers or alternative compliance pathways. Any rights or relief mechanisms are not documented within this instrument.

Practical implications of these duties:

• Maintenance decisions: The instrument ties legal compliance to Maintenance Release scheduling. Whoever controls the Maintenance Release inspection cycle effectively chooses whether compliance occurs within the 100-hour window or at the later scheduled inspection.
• Documentation obligations: Because the AD requires part-number determination "by a physical inspection or aircraft records" for T Mk 20 applicability, there is an implicit duty to maintain or be able to access accurate aircraft records and to perform or permit physical inspection where records are incomplete.
• Technical reliance: The AD delegates the technical content and prescriptive measures to British Aerospace T.N.S. No. 161 Issue 3. Compliant parties must obtain and apply that document to discharge their duty.

The AD does not delineate rights to challenge, the process for seeking an alternative means of compliance, or compensatory entitlements for costs incurred; none of those features are included in the text supplied.

The AD text does not specify civil or criminal penalties, nor does it set out enforcement mechanisms within this document. The only enforcement-adjacent facts visible in the text are procedural and temporal obligations.

• Absence of specified penalties: The AD does not contain sentences that prescribe fines, suspensions, or other sanctions for non-compliance, and it does not describe inspection, audit, or enforcement processes in this instrument. The text focuses exclusively on applicability, technical requirement referencing, compliance timing and the factual background that prompted the directive.
• Compliance as a performance requirement: The AD prescribes mandatory action "in accordance with British Aerospace T.N.S. No. 161, Issue 3" and sets specific time triggers for that action (Requirement; Compliance). Those directives function as legal obligations within the document, but the AD itself does not say who enforces them or what penalties follow a breach.
• Operational enforcement cues within the text: The Compliance section ties the AD to Maintenance Release scheduling and to component removal events. Practically, these are points at which compliance would be observable in aircraft maintenance records: the AD requires action within 100 hours TIS after the effective date or at the next Maintenance Release inspection and whenever the wing attachment links are removed (Compliance). This creates traceable moments for auditors or inspectors to check whether the mandated action has been completed and recorded.
• Evidence and records: The background requires part-number determination "by a physical inspection or aircraft records" for T Mk 20 applicability (Background). That requirement creates a record-keeping and inspection trail that could be examined to verify whether an aircraft was within the AD's ambit and whether the mandated action was performed.

Because the instrument does not state enforcement authorities, sanctions, or appeal processes, practitioners should not infer from this text alone what legal consequences exist for non-compliance, nor what procedural steps apply for enforcement or dispute. The instrument’s silence on penalties means that any enforcement or sanction mechanisms, and their procedures, are not recorded here.

The AD constructs its obligations by referencing a manufacturer technical standard and by linking compliance to maintenance-release processes and aircraft records. The document itself does not reference statute, regulation, or other Acts; it does, however, create mandatory interaction points with specific maintenance documentation and procedures.

• Interaction with manufacturer technical documentation: The AD's operative command is to act "in accordance with British Aerospace T.N.S. No. 161, Issue 3, dated 1 August 1985" (Requirement). The AD therefore imports the technical content of that external document into its legal requirement. Implementation of the AD necessarily requires access to, and reliance upon, that technical standard.
• Interaction with maintenance processes and records: Compliance timing is expressly linked to a "scheduled inspection for Maintenance Release" (Compliance). This ties the AD into the operational regime of Maintenance Releases and the scheduling practices of maintenance organisations. Further, the background requires the determination of wing-attach fitting part numbers "by a physical inspection or aircraft records" (Background), creating an interface with record-keeping obligations and physical inspection routines.
• Interaction with previous AD amendments: The Background notes that "Amendment 1 of this AD revised the requirements to reflect Issue 3 of the Requirement Document" and that "This amendment is issued to include the Portuguese manufactured Chipmunk (T Mk 20) in the applicability of the AD" (Background). Amdt 2 therefore operates as an amendment to earlier AD/DHC-1/21 versions, adjusting applicability rather than altering technical content or compliance timing. The AD therefore interacts with the AD series for this aircraft model.
• No cross-reference to enabling legislation or enforcement procedures: The AD does not cite the legislative instrument or regulation under which CASA or its delegate issues ADs, nor does it contain any cross-reference to broader aviation safety laws or penalties. The interaction with broader legal frameworks, including enforcement mechanisms, is not stated in this text.

In practice, implementation of this AD will require alignment between the obligations it imposes and a maintenance organisation's scheduling, record-keeping and access to manufacturer technical material. The AD also requires parties to resolve applicability for certain airframes (T Mk 20) by consulting records or performing physical inspections, thereby interacting operationally with records law or institutional record-keeping practice. The AD does not itself specify how conflicts between the referenced T.N.S. and local procedural requirements are to be resolved.

The document is labelled Amendment 2 (Amdt 2) to AD/DHC-1/21. The AD contains a concise statement of its amendment lineage and effect.

• Current instrument identification: The document header shows AD/DHC-1/21 Amdt 2, and the body repeats that identifier (multiple headings). The Compliance section records "This Amendment becomes effective on 21 June 2011." The signature block carries the date 16 June 2011 and the name Glen Steemson, "Delegate of the Civil Aviation Safety Authority" (signature block).
• Relationship to Amendment 1: The Background states that "Amendment 1 of this AD revised the requirements to reflect Issue 3 of the Requirement Document which revised the shimming procedure" (Background). That sentence explains the substantive change introduced in Amdt 1: the Requirement Document (T.N.S.) was updated to Issue 3, and Amdt 1 aligned the AD's instructions with that new Issue.
• Effect of Amendment 2: The Background explains this amendment's purpose: "This amendment is issued to include the Portuguese manufactured Chipmunk (T Mk 20) in the applicability of the AD." It adds the explanatory caveat: "A recent review indicates that TNS 161 may be applicable to T Mk 20 Chipmunks, depending on the wing attach fitting part number fitted to the aircraft. This part number will need to be determined by a physical inspection or aircraft records." The Background concludes by noting "There is no change to the requirements or compliance (except to require compliance after the effective date of this amendment)" (Background). That sentence says Amdt 2 did not alter the substantive technical duty or timing other than fixing the effective date after which compliance is required.
• Effective date and promulgation: The instrument records an effective date for the amendment of 21 June 2011 and a signing date of 16 June 2011. The signature is by a CASA delegate, indicating the AD was issued via delegated authority (signature block).
• Technical-document revision history implicit in AD history: The Background links Amdt 1 to a change in the Requirement Document (Issue 3 of T.N.S. No. 161, which "revised the shimming procedure"). The AD thus records a two-stage history: first, update technical instruction (Amdt 1); second, extend applicability to additional production origin/models after review (Amdt 2).

The AD text contains no further historical amendments, transitional measures, grandfathering clauses, or sunset dates beyond the effective date of Amdt 2. It also does not provide a full chronology of previous amendment texts or a consolidated version of requirements; it instead identifies the operative Requirement Document (British Aerospace T.N.S. No. 161 Issue 3) and instructs compliance with it.

This AD does not record any litigation history, judicial decisions, or administrative appeals. The document’s Background refers to operational reports but not to legal proceedings.

• No cases cited: The AD's Background says "Cases have been reported where the wing to fuselage attachment links have been fitted out of alignment resulting in chafing of the spar and/or tie bar, by the links" (Background). These references are to technical/operational incidents and not to litigation. There is no mention in the AD of disputes, appeals, court decisions, or precedent.
• Absence of challenge information: The document does not indicate whether the AD, or previous amendments to it, have been the subject of administrative review, stakeholder challenge, or litigation. The AD simply records its technical rationale and amendment purpose.
• Implications for practitioners: Because this instrument contains no litigation record, practitioners seeking precedent, case law, or judicial interpretation of AD/DHC-1/21 or its amendments will not find those materials in this text. The AD does not describe dispute resolution channels or timelines for contesting the directive; none are specified here.

In short, the AD records operational incidents prompting a safety measure and documents the technical and applicability decisions taken by the issuing authority, but it does not include or reference any legal contestation or judicial treatment of the directive.

This AD contains several practical traps and points of potential operational friction that arise from its wording and structure.

• Applicability ambiguity for Portuguese (T Mk 20): The AD includes "Portuguese (T Mk 20) production models" in Applicability but then qualifies that inclusion in Background: "TNS 161 may be applicable to T Mk 20 Chipmunks, depending on the wing attach fitting part number fitted to the aircraft. This part number will need to be determined by a physical inspection or aircraft records" (Background). The gotcha: a T Mk 20 operator must not assume automatic inclusion; they must verify part numbers. If records are incomplete, they must arrange a physical inspection. Failure to confirm capture status may lead to missed compliance obligations or unnecessary work.
• Reliance on an external document not reproduced in the AD: The AD requires action "in accordance with British Aerospace T.N.S. No. 161, Issue 3, dated 1 August 1985" (Requirement). The technical measure is not summarised or reproduced within the AD. The gotcha: operators must obtain the referenced T.N.S. and interpret and apply its instructions accurately. Lack of access to the T.N.S., misinterpretation of its steps, or reliance on an earlier or different Issue could result in non-compliance.
• Timing interplay with Maintenance Releases can extend the compliance window: The AD requires action "Within 100 hours time in service after the effective date of this AD or at the next scheduled inspection for Maintenance Release issued after the effective date of this AD, whichever is the later" (Compliance). If an organisation’s Maintenance Release cycle is scheduled beyond 100 hours after the effective date, this wording allows the operator to defer until that later inspection. The gotcha: scheduling choices by the maintenance provider can delay corrective action; operators must be deliberate about whether to rely on the "next scheduled inspection" trigger or to perform the action sooner.
• Ongoing trigger on component removal: The AD requires action whenever "the wing attachment links are removed" (Compliance). The gotcha is operational: routine maintenance tasks that remove those links will re-trigger the AD requirement and may require additional inspection/shimming work each time the component is removed, potentially increasing maintenance cost and downtime.
• Amendments did not change the requirements: The Background stresses "There is no change to the requirements or compliance (except to require compliance after the effective date of this amendment)" (Background). The gotcha: operators familiar with an earlier published version of the AD might assume the amendment relaxed or altered technical instructions. Instead, Amdt 2 only changed applicability timing and scope to include some T Mk 20s.
• Record-keeping and documentary proof: Because part-number applicability can be resolved "by aircraft records" (Background), incomplete or poorly organised records could force a physical inspection or leave operators uncertain about their obligations. Ensuring records accurately reflect part numbers is therefore critical.
• Vintage documentation: The cited technical standard is dated "1 August 1985" and is identified as Issue 3 (Requirement). The gotcha: operators should be attentive to whether they hold the correct Issue edition; reliance on an earlier Issue could produce non-compliance with the AD’s specific direction to follow Issue 3.

These are practical operational pitfalls embedded in the AD’s drafting: conditional applicability that depends on part numbers, reliance on an external technical document not included in the AD, compliance timing tied to maintenance scheduling, and an ongoing trigger when components are removed. Each creates points at which maintenance planners, record custodians, and inspection personnel must make explicit decisions to avoid oversight.

The AD prescribes a clear, if externally referenced, compliance pathway. Below is a stepwise checklist derived directly from the instrument to implement compliance.

1. Establish applicability to each airframe in your fleet.

   • For English production (C1) models: the AD lists "English production (C1) all models" in Applicability, so those airframes are in scope (Applicability).
   • For Portuguese production (T Mk 20): determine whether TNS 161 applies by checking the wing-attach fitting part number fitted to the aircraft, "by a physical inspection or aircraft records" (Background). If the part number is consistent with the parts that TNS 161 covers, the aircraft is in scope.

2. Obtain the normative technical document.

   • Secure British Aerospace T.N.S. No. 161, Issue 3, dated 1 August 1985. The AD makes that document the operative technical standard to follow: "Action in accordance with British Aerospace T.N.S. No. 161, Issue 3, dated 1 August 1985" (Requirement).

3. Plan timing and scheduling.

   • The AD is effective 21 June 2011 (Compliance).
   • Perform the actions required by T.N.S. No. 161 Issue 3 "Within 100 hours time in service after the effective date of this AD or at the next scheduled inspection for Maintenance Release issued after the effective date of this AD, whichever is the later" (Compliance). Determine whether to schedule work during an upcoming Maintenance Release inspection or to perform it sooner to satisfy the 100-hour window, noting the AD’s "whichever is the later" formulation.
   • Ensure that any removal of the wing attachment links during maintenance prompts immediate or contemporaneous execution of the T.N.S. procedures, because the AD also requires the action "at any time the wing attachment links are removed" (Compliance).

4. Execute the technical procedures.

   • Follow the step-by-step inspection, shimming and corrective procedures set out in British Aerospace T.N.S. No. 161 Issue 3. The AD does not list those steps, so strict adherence to the T.N.S. is required to meet the AD’s command.

5. Document compliance.

   • Record the inspection and corrective actions in aircraft maintenance records, including references to British Aerospace T.N.S. No. 161 Issue 3, the date of completion, hours in service at completion, and any parts or shims fitted. For T Mk 20 airframes, retain the inspection or records evidence establishing the wing-attach fitting part number that determined applicability.

6. Maintain a compliance schedule.

   • Since the AD triggers again upon removal of the wing attachment links, add an entry to your maintenance procedures to ensure the T.N.S. requirements are revisited whenever those links are removed in future maintenance.

7. Communicate with maintenance release signatories.

   • The AD ties compliance to "the next scheduled inspection for Maintenance Release" (Compliance). Ensure whoever signs Maintenance Releases is aware that the AD creates a compliance deadline that can be met at a subsequent Maintenance Release if that release is scheduled later than 100 hours after the effective date. Clarify responsibilities for scheduling and verifying the AD-related tasks on the Maintenance Release documentation.

8. Verify part numbers physically or via records.

   • For T Mk 20 aircraft where applicability is uncertain, perform the physical inspection of the wing-attach fitting to determine the part number or locate the relevant aircraft records showing the fitted part number (Background). If records are incomplete, plan for the physical inspection to establish coverage under the AD.

9. Retain evidence of having used the correct Issue.

   • The AD requires adherence to Issue 3 of T.N.S. No. 161 specifically (Requirement). Document that the maintenance was performed to Issue 3 and retain a copy or citation of that Issue in the maintenance file.

10. Monitor for further amendments.

• The AD is labelled Amdt 2 and references Amendment 1 changes (Background). Maintain attention to any further AD changes that could alter applicability, timing, or the normative technical document.

This checklist follows strictly from the AD’s wording: the requirement to follow a specific T.N.S., the defined compliance timing, the need to determine applicability for certain production models by part-number verification, and the on-going trigger linked to component removal. The AD does not provide alternative compliance methods, exemptions, or a process for seeking relief; none are contained in this text.