AD/DHC-1/25 Amdt 3 - Wing Flaps

The AD uses a compact set of administrative and technical concepts. Applicability identifies the subset of the fleet covered: "All English production (C1) all models and Portuguese production (T Mk 20) aircraft." The Requirement concept is the mandatory action phrase "Action in accordance with De Havilland Support TNS CT(C1) No. 166, Issue 5, dated 1 June 2007." That links mandatory compliance to an external technical support document which presumably contains the inspection methods, acceptance criteria and any associated remedial actions.

Compliance timing is a two-part concept: an initial compliance trigger and repeating intervals. Initial compliance is set at the next annual maintenance check after the AD's effective date, subject to an exception where "the satisfactory condition of the flap brackets and associated structure is already known." This introduces a factual predicate that can discharge immediate inspection if the operator holds adequate evidence of satisfactory condition. The repeating-interval concept is expressed as a dual metric: repeat at intervals not exceeding "300 flight hours or six years, whichever occurs first." That ties inspection frequency to utilisation (flight hours) and to calendar time, creating an inspection duty that applies both to high-usage and low-usage aircraft.

The AD distinguishes components for inspection by reference to "flap brackets and associated structure" and, in the Background, by reference to "Inner Hinge Bracket" and "Reinforcing Channel." The Background notes that inner hinge bracket inspections are unchanged, while reinforcing channel inspection was introduced in Amdt 2. The safety hazard concept is fatigue cracking attributed to "repeated use of the footstep on the flap."

Administrative provenance and effectivity are core concepts: the AD is an instrument of CASA, effective 22 June 2011, signed by the CASA Delegate on 17 June 2011. The AD text sets its own amendment history and records specific prior amendments (notably Amdt 2 effective 27 September 2007) and the reason those amendments were made (revision of the requirement document and introduction of time/flight-hour compliance).

Finally, the AD is procedural rather than prescriptive in the sense that it directs action "in accordance with" a named maintenance support document rather than embedding step-by-step inspection methodology or acceptance criteria in the AD text itself. That shifts the technical detail burden to the referenced De Havilland Support TNS CT(C1) No. 166, Issue 5, dated 1 June 2007.

The AD explicitly names the affected aircraft: "All English production (C1) all models and Portuguese production (T Mk 20) aircraft." Practically, that identifies owners, operators, custodians and maintenance organisations responsible for those specific DHC-1 Chipmunk series aeroplanes. The AD does not list individual registration marks or serial numbers in the supplied text; it uses production and model descriptors. Therefore, an entity that operates or maintains any Chipmunk that falls within the English production C1 models or the Portuguese manufacture T Mk 20 is within the AD's scope.

Those who perform or authorise maintenance actions are affected because the AD requires action "in accordance with De Havilland Support TNS CT(C1) No. 166, Issue 5, dated 1 June 2007." The named technical support document will be the operative specification for how to carry out the inspections; maintenance organisations will therefore need access to, and to apply, that document. If the operator claims the component's "satisfactory condition" is already known, the onus is on the operator to demonstrate that status at the time the next annual maintenance check would fall due, because the AD states the initial inspection is excepted only when satisfactory condition is already known.

Regulatory and certifying personnel are also affected. The AD is issued by the Civil Aviation Safety Authority and signed by a Delegate; CASA or its delegates will be the authority documenting and recording compliance. The AD itself does not set out enforcement mechanisms in the text supplied, but compliance records and maintenance release paperwork will be the usual administrative artefacts relied on by regulators to verify compliance.

Suppliers of parts and repair vendors may be indirectly affected because the AD draws attention to cracking in "flap brackets and associated structure" and the reinforcing channel. If inspections reveal defects needing repair or replacement, parts supply chains, repair facilities and possibly De Havilland or third-party providers of approved repair instructions will be engaged to return the aircraft to an airworthy state in accordance with the technical support document.

Owners of aircraft that do not fall within the stated applicability (other than English production C1 models and Portuguese T Mk 20 production) are not identified as affected by this AD in the supplied text. The AD states that Amdt 3 "adds the Portuguese manufactured (T Mk 20) to the applicability," which indicates a change in the affected set. The Background also references prior amendments and scope changes, which is relevant for operators of aircraft newly captured by the amendment.

Finally, insurers, lessors and pilots might be consequentially affected because demonstration of compliance may be necessary to maintain airworthiness certification, insurance cover or fulfil contractual obligations. The AD text itself identifies those who must perform the inspection actions but does not explicitly address these downstream stakeholders.

The AD places a specific duty on operators and maintenance organisations to carry out inspections. The textual duty is: "Action in accordance with De Havilland Support TNS CT(C1) No. 166, Issue 5, dated 1 June 2007." That is both the procedural duty and the substantive reference for the technical steps to be taken. The initial timing duty is: "At the next annual maintenance check after the effective date of this AD, unless the satisfactory condition of the flap brackets and associated structure is already known." The repeated duty is: "Repeat the inspection at intervals not to exceed 300 flight hours or six years, whichever occurs first."

Rights or exemptions are narrowly specified. The AD permits an exception to the immediate initial inspection when "the satisfactory condition of the flap brackets and associated structure is already known." The AD does not define what constitutes "satisfactory condition" nor prescribe the evidentiary form for that knowledge. Because the AD directs compliance to a named technical support document, the content of that document will likely determine the technical acceptance criteria; however, the AD text itself does not reproduce those criteria. The operator's right to assert satisfactory condition therefore exists, but the document is silent on documentary standards or proof,operators and maintenance organisations should therefore ensure that any claim of prior satisfactory condition is documented in maintenance records sufficient for regulatory oversight.

The AD does not include in its supplied text any explicit right to derogate, to obtain alternative methods of compliance, or to apply for exemptions. The AD similarly does not include repair instructions or alternative compliance pathways in the text provided. It refers instead to the De Havilland Support TNS CT(C1) No. 166, Issue 5, which will be the operative document for the technical content and may itself contain guidance on repairs, replacement parts, or approved alternatives. The AD also does not identify a process for seeking relief from the requirement within the present text.

The duty attaches recurrently: inspections must be repeated "at intervals not to exceed 300 flight hours or six years, whichever occurs first." That creates a continuing inspection obligation linked to both utilisation and calendar time. The AD does not delineate record-keeping requirements in the supplied text, but the combination of an initial trigger tied to the annual maintenance check and recurring intervals implies that operators must schedule and document inspections and any remedial actions to demonstrate ongoing compliance.

Finally, the AD imposes no repair obligation in the text supplied beyond the action reference. The remedial duty,what to do upon finding cracking,must be sourced from "De Havilland Support TNS CT(C1) No. 166, Issue 5, dated 1 June 2007." Operators therefore have the duty to follow the content of that support document for both inspection technique and remedial action.

The supplied AD text does not include explicit penalty provisions, fines, or a specified enforcement procedure. The document records administrative provenance: it was signed by Glen Steemson, "Delegate of the Civil Aviation Safety Authority," and became effective on 22 June 2011. The AD format records Applicability, Requirement, Compliance, Background and effective date, but does not, in the text provided, set out sanctions for non-compliance.

The absence of penalty language in the AD text means that any enforcement action, penalties, or regulatory consequences would be governed by the broader regulatory framework under which CASA issues ADs rather than by the words within this AD itself. The AD does not say what constitutes demonstrable compliance records or who will verify them. The AD likewise does not set out compliance reporting requirements, approval pathways for alternative methods of compliance, or a formal process for remediating non-compliance within the instrument text shown.

Because the AD mandates inspection "in accordance with De Havilland Support TNS CT(C1) No. 166, Issue 5," enforcement may practically depend on whether operators follow the referenced technical document. The AD does not state whether the referenced document is endorsed, mandatory, or advisory beyond the AD's instruction to act "in accordance with" it, but the phrasing in the AD creates an obligation to apply the referenced document. Any regulatory enforcement measures or penalties would need to be sought, stated or applied under the relevant enabling aviation safety laws and CASA procedures, none of which are reproduced in or specified by the supplied AD text.

In short, the AD imposes inspection duties and specifies the technical source for how to discharge them, it identifies effective dates and applicability, and it is signed by the CASA Delegate; however the AD as supplied does not itself articulate penalties, fines, or administrative enforcement steps. Parties seeking to understand sanction exposure will need to review the broader statutory and regulatory regime under which CASA operates, as that detail is not contained in the AD excerpt provided.

The AD text supplied does not reference other statutory provisions, regulations, or safety rules by citation. It is an administrative instrument issued under the authority of the Civil Aviation Safety Authority, as indicated by the signature and the format, but the AD itself does not cite its enabling provision or describe how it integrates with airworthiness certification, maintenance release requirements, or continuing airworthiness responsibilities in statute or regulation.

Operationally, the AD interacts with maintenance cycles by making the "next annual maintenance check" the trigger for initial compliance unless satisfactory condition is already known. That creates a scheduling interaction between the AD and an operator's established maintenance calendar. The AD also prescribes repeat-intervals tied to flight hours and calendar time, which interacts with operators' flight recording, utilisation monitoring and maintenance planning practices.

The AD makes compliance conditional on both a named technical support document and knowledge of "satisfactory condition." The named document is "De Havilland Support TNS CT(C1) No. 166, Issue 5, dated 1 June 2007." That interaction means operators must obtain and apply that specific document in order to meet the AD's requirement. If an operator instead relied on a different maintenance procedure, the AD, as written, directs adherence to Issue 5 of TNS CT No. 166; therefore the AD interacts with document control processes within maintenance organisations and with De Havilland's support documentation.

The AD notes prior amendment history in its Background. It records that "Amendment 2, effective 27 September 2007, was issued in response to a revision of the requirement document and introduced a compliance of flight hours and calendar time." That describes an interaction between AD amendment and the technical requirements in the referenced document, indicating the AD changes as a response to revisions in the support documentation.

Beyond these points, the AD text supplied does not set out express cross-references to other Australian legislative instruments, international airworthiness directives, or civil aviation regulations. The absence of such cross-references in the AD means that any legal interaction with other laws or instruments must be inferred from the standard regulatory context in which CASA issues ADs, which is not reproduced in the supplied text. Users seeking to understand how this AD sits within the full legal regime will need to consult the enabling aviation legislation and CASA procedural documents that establish enforcement, alternative compliance pathways and the legal effect of ADs, none of which are contained in the AD excerpt.

The document itself is labelled AD/DHC-1/25 Amdt 3 and identifies the amendment as Amdt 3, dated 13/2011, with effective date 22 June 2011. The Background contains explicit reference to the content of prior amendments and the reasons for them. The Background states that cracking was reported in the subject flap components and that "The Inner Hinge Bracket inspections are unchanged from the previous issues of this Directive." The Background also remarks that "the inspection of the Reinforcing Channel was a new requirement introduced in the previous amendment (Amdt 2) of this Directive."

Amdt 2 is specifically identified as having an effective date of 27 September 2007 and is described as being issued "in response to a revision of the requirement document and introduced a compliance of flight hours and calendar time." The current amendment, Amdt 3, "adds the Portuguese manufactured (T Mk 20) to the applicability of the AD. A review has indicated that the inspection is applicable to the Portuguese manufactured model." The requirement reference retained in Amdt 3 is De Havilland Support TNS CT(C1) No. 166, Issue 5, dated 1 June 2007, which the AD instructs operators to follow.

The AD also records that the Reinforcing Channel inspection had been introduced earlier, and that inner hinge bracket inspections were unchanged in this amendment cycle. The amendment log in the Background is therefore the only place that a history is recorded in the supplied text. The AD itself does not include a full lineage table of all prior versions, nor does it reproduce the full text of Amdt 1 or the original AD that established the requirement. The AD content indicates at least three instrument states: the original directive that predated Amdt 2, Amdt 2 effective 27 September 2007 which introduced the reinforcing channel inspection and flight-hour/calendar compliance, and Amdt 3 effective 22 June 2011 which added Portuguese-manufactured T Mk 20 to applicability.

The requirement to act according to De Havilland Support TNS CT(C1) No. 166 Issue 5 dated 1 June 2007 suggests that the technical support document was revised prior to or by 1 June 2007; Amdt 2 is described as having been issued in response to a revision of the requirement document, although the AD does not enumerate what specifically changed within TNS CT No. 166. The supplied AD text places the sourcing of inspection and remedial action procedures with that De Havilland document rather than reproducing them, and binds operators to the specific issue and date cited.

The supplied AD contains no litigation history, no references to judicial proceedings, and cites no cases. The document is an administrative safety instrument and its Background recounts a technical motivation but does not reference any disputes, appeals or court actions. There are no notes in the AD text indicating that this directive has been the subject of litigation or that its validity has been contested.

Because the AD text does not record any appeals, petitions for review, or other legal processes, the only supported claim is that the AD itself, as presented, contains no litigation history. Any litigation that may have arisen in practice is not referred to in the supplied text and therefore cannot be asserted on the basis of this document alone. Users who require the litigation record for this AD will need to consult external court or tribunal databases or CASA records; those sources are not reproduced within the AD excerpt provided.

The AD's compact wording contains several operative points that can lead to compliance uncertainty if not carefully interpreted.

1. Dependency on an external technical document: The Requirement is to act "in accordance with De Havilland Support TNS CT(C1) No. 166, Issue 5, dated 1 June 2007." The AD does not reproduce the inspection procedures, acceptance criteria or remedial steps; operators must obtain and follow the named document. A practical risk is that operators will need to ensure they have the specified Issue 5 version, because the AD cites that precise issue and date. The AD does not state whether later issues are acceptable, or whether certain parts of the De Havilland document remain subject to later revision. The AD gives no instruction on how to handle conflicting versions of the support document.

2. "Satisfactory condition already known" exception: The initial inspection requirement is subject to the exception "unless the satisfactory condition of the flap brackets and associated structure is already known." The AD does not define what documentation or evidence will satisfy regulators that the condition is "known". This creates a potential evidentiary ambiguity: an operator will need to determine what maintenance records, inspection certificates or parts history adequately establish satisfactory condition at the time the next annual maintenance check falls due. Absent a definition in the AD, reasonable operators will need to adopt conservative record-keeping practices.

3. Dual metric repeat interval: The repeat interval is specified as "not to exceed 300 flight hours or six years, whichever occurs first." That structure has implications for both high-utilisation aircraft (300 flight hours will drive the interval) and low-utilisation aircraft (the six-year calendar cap will still require inspection even with low hours). Operators with light utilisation may therefore incur a long calendar-recurrence inspection obligation; conversely, those with heavy utilisation may incur frequent inspections. The AD does not address whether partial flight hours or prorated intervals are acceptable.

4. Scope of affected components: The AD refers to "flap brackets and associated structure" and, in Background, to "Inner Hinge Bracket" and "Reinforcing Channel." It also notes that inner hinge bracket inspections remain unchanged and that reinforcing channel inspection was introduced earlier. Operators must therefore ensure that their inspection programmes cover the reinforcing channel in addition to previously inspected hinge brackets. The AD does not include photographs, part numbers or explicit diagrams in the supplied text; the operator must rely on the referenced technical support document for component identification.

5. Applicability phrasing: The AD lists "All English production (C1) all models and Portuguese production (T Mk 20) aircraft." The phrasing relies on production descriptors rather than serial-number lists. For mixed-production fleets or aircraft with ambiguous provenance, operators might need to verify whether a given airframe is within the English C1 production or Portuguese T Mk 20 production. The AD does not provide a cross-reference table of serial numbers.

6. No penalties or enforcement detail in the text: Since the AD does not specify penalties or enforcement mechanisms in the supplied text, operators may assume there is discretion in enforcement. That assumption is risky because the broader regulatory framework likely provides a compliance mandate, but such enforcement mechanisms are not described in the AD itself. The operator should not treat the absence of penalty language as absence of enforceability.

7. Timing and effectivity: The AD is effective 22 June 2011 and the signature is dated 17 June 2011. If maintenance cycles occur close to that effective date, operators must determine whether their next annual maintenance check falls before or after the effective date and whether the "satisfactory condition already known" exception applies. The AD does not specify how to handle inspections that were performed shortly before the effective date; operators must therefore ensure their records demonstrate the timing and scope of recent inspections.

8. Historical changes: The Background notes changes in previous amendments, including the introduction of flight-hour and calendar time compliance in Amdt 2. Operators upgrading maintenance programmes must ensure that their inspection intervals reflect the AD's current repeat intervals and that they did not rely only on older inspection regimes.

Each of these "gotchas" stems from the AD's concise form and reliance on an external technical document for the substantive inspection and repair instructions. Careful documentation, confirmation of aircraft production origin, access to the specified De Havilland support document and clear maintenance scheduling are needed to avoid compliance ambiguity.

Compliance requires a combination of administrative steps and technical action in accordance with the AD's express text.

1. Establish applicability. Confirm whether the aircraft is within "All English production (C1) all models" or "Portuguese production (T Mk 20) aircraft" as stated in the Applicability field. The AD uses production descriptors; operators should check the aircraft's production and serial information to confirm whether the AD applies.

2. Obtain the referenced technical document. The AD Requirement is to take "Action in accordance with De Havilland Support TNS CT(C1) No. 166, Issue 5, dated 1 June 2007." Obtain that specific issue and date of the TNS CT No. 166 document. The AD ties compliance to that document; do not substitute a different issue without confirming acceptability with the relevant authority.

3. Determine initial compliance timing. Schedule the inspection for "the next annual maintenance check after the effective date of this AD" (effective date 22 June 2011) unless you can demonstrate that "the satisfactory condition of the flap brackets and associated structure is already known." To rely on the exception, ensure you have clear, dated maintenance records demonstrating the satisfactory condition of the referenced components that would be persuasive to a regulator or certifying authority.

4. Perform inspections per the De Havilland document. Once the operator has TNS CT No. 166 Issue 5, follow the inspection procedures, acceptance criteria and any remedial instructions contained in that document. The AD text directs action "in accordance with" that document, so the substantive inspection steps and any repair instructions should be carried out as described there.

5. Implement repeat-interval programme. After the initial inspection, schedule and perform repeat inspections "at intervals not to exceed 300 flight hours or six years, whichever occurs first." Integrate these intervals into the maintenance control programme, flight-hour tracking and calendar scheduling so that inspections are not missed.

6. Record-keeping. Maintain clear maintenance records that show the date of each inspection, the flight hours at inspection, the inspection findings and any corrective actions taken in accordance with the De Havilland support document. Given the AD's exception for prior "satisfactory condition" and its reliance on a named support document, robust documentation will be central to demonstrating compliance.

7. Parts and repairs. If inspections reveal cracking or other defects, apply the remedial actions specified in TNS CT No. 166 Issue 5. The AD text does not itself set out repair procedures; compliance requires following the technical document for repairs and parts replacement. Ensure that any parts installed or repairs carried out meet the acceptability criteria in the De Havilland support document and are documented.

8. Liaise with certifying authorities. If there is uncertainty over the acceptability of prior inspections, the status of the referenced technical document, or the appropriateness of alternative procedures, engage the relevant CASA office or authorised delegate for direction. The AD is signed by a CASA Delegate, and CASA will be the competent authority for queries about acceptable compliance means; the AD text does not set out alternative methods of compliance in itself.

9. Audit and oversight. Include the AD inspection requirement in internal audits, continuing airworthiness management processes and, where applicable, in contracts with maintenance organisations. Operators should verify that maintenance providers have access to TNS CT No. 166 Issue 5 and apply it correctly.

10. Update maintenance manuals and procedures. Amend the aircraft maintenance programme and maintenance control documentation to incorporate the AD's inspection frequency and references to De Havilland Support TNS CT(C1) No. 166 Issue 5. Ensure that planner and certifying staff are aware of the requirement to perform reinforcing channel inspections in addition to inner hinge bracket inspections where applicable.

Taken together, these steps discharge the AD's duties as expressed in the supplied text: act according to the named support document, perform initial inspection at the next annual maintenance check unless satisfactory condition is recorded, and repeat inspections within the 300 flight-hour or six-year cap. Where the AD text is silent (for example on the evidentiary standard for "satisfactory condition" or the acceptability of later issues of the technical document), conservative and documented practices are the practical compliance route.