AD/ROBIN/39 - State of Design Airworthiness Directives

This AD uses a small set of recurring regulatory concepts: applicability, mandatory action, equivalence, terminating action, compliance period, and linkage to Certificate of Airworthiness. The AD's Applicability clause lists by type the specific aeroplane models captured: all Robin HR200-100, HR200-120, HR200-120B, HR200-160, HR200-100S, R2160, R2100, R2100A, R2160D, R2112, R2160I and R2120U aircraft. That list is the initial gate for every duty under the AD; if the aircraft is not one of those types the AD does not apply on its face.

Requirement 1 is a positive duty of inquiry: operators must determine the applicability of each CAA (NZ) AD listed in Table 1. Requirement 2 is a positive duty to act where a listed CAA (NZ) AD is applicable and not already accomplished: perform the actions required by that CAA (NZ) AD. The AD therefore imposes both an investigative obligation and a remedial obligation. The investigative obligation places a compliance-cost risk on owners and operators, because they must examine aircraft configuration, modification history and log books to determine whether each listed AD is applicable.

Equivalence: Note 1 provides a limited recognition mechanism for French DGAC ADs. If the CAA (NZ) AD refers to an equivalent DGAC AD and the DGAC AD is reflected in the aircraft log books as having been complied with, then the CASA AD treats that entry as evidence that the equivalent CAA (NZ) AD need not be re-done. The AD therefore creates a binary evidentiary shortcut: a logbook entry recording compliance with the DGAC AD equals compliance with the listed NZ AD, provided the NZ AD identifies the DGAC AD as a compliance means. The AD also lists some NZ ADs with “No Equivalent”, meaning the equivalence shortcut is not available for those entries (see Table 1 entries DCA/R2000/38 and DCA/R2000/39).

Terminating action concept: the Background explains that the listed ADs are of two kinds , one-time actions for which compliance dates or periods have passed, or ongoing inspection/action requirements until a terminating action is applied and its compliance date has passed. That distinction affects compliance strategy: for some ADs a single modification or replacement (a terminating action) ends the need for recurring inspections; for others a one-off inspection or modification may already be late.

Compliance period: the AD explicitly prescribes the compliance window for its two operative requirements: within 30 days after the AD’s effective date or prior to the issue of a Certificate of Airworthiness, whichever occurs first. This creates a short, fixed calendar deadline tied to the official effective date (5 December 2007) and an operational trigger (CoA issuance).

Cross-jurisdictional recognition: the AD operates by incorporating actions mandated by a foreign regulator’s ADs (CAA (NZ) and sometimes DGAC) into Australian compliance obligations for aircraft on Australia’s register. The AD therefore functions as a transposition mechanism, not by re-stating technical requirements, but by reference to the foreign AD texts listed in Table 1 (Note 2 supplies a URL to CAA (NZ) ADs).

Finally, the instrument is administrative and prescriptive: it leaves technical specifics to the referenced CAA (NZ) ADs rather than restating them. That approach reduces duplication of technical content but increases dependence on access to and correct interpretation of the foreign AD texts and associated logbook evidence.

Primary affected persons and entities are the owners and operators of the applicable Robin models listed in the Applicability clause: all Robin HR200-100, HR200-120, HR200-120B, HR200-160, HR200-100S, R2160, R2100, R2100A, R2160D, R2112, R2160I and R2120U aircraft. The AD’s operative requirements (Requirements 1 and 2) put duties on whoever holds operational responsibility for those aircraft at the relevant compliance times , typically the registered operator and/or owner. The compliance text ties obligations into Certificate of Airworthiness issuance, so persons seeking to obtain a CoA for an aircraft of the listed type are immediately affected; the compliance deadline may fall before the CoA is issued.

Maintenance organisations and certificated maintenance personnel are secondary but materially affected actors. The AD requires performance of actions mandated by the NZ CAA ADs where applicable; those actions are technical and will generally be performed by licensed maintenance organisations or persons competent under Australian maintenance regulations. Maintenance organisations will need access to the NZ and DGAC AD texts, spare parts, and possibly design approvals or engineering orders to carry out terminating modifications. The AD also creates a record-keeping obligation because equivalence depends on logbook entries indicating compliance with an equivalent DGAC AD (Note 1).

Type Certificate holder Alpha Aviation Design Ltd is identified in the Background as the type certificate holder for the models listed in Applicability. That identification means the TC holder may be involved in clarification requests or provision of service information for terminating actions; the AD does not allocate duties to the TC holder but places the listed ADs into Australian regulatory effect for the TC holder’s types.

Airworthiness regulators and inspectors are affected because they must check compliance when issuing or reissuing Certificates of Airworthiness and during safety oversight; the AD explicitly conditions compliance timelines on CoA issuance. The AD’s Note 2 provides a URL for accessing the NZ CAA ADs; regulators and maintainers will rely on that or other official sources to locate the referenced AD texts.

Prospective buyers, leasees and financiers are indirectly affected because the AD may impose remedial costs or modifications that must be documented in logbooks before a CoA is issued or transferred; the compliance status may affect valuations and transaction conditions. Because the AD flags that not all listed ADs will apply to all aircraft given manufacture date or configuration, purchasers must undertake due diligence to determine which of the listed ADs, if any, remain outstanding on a particular airframe.

Finally, because two of the listed NZ ADs have “No Equivalent” in the Equivalent DGAC AD column (Table 1 entries DCA/R2000/38 and DCA/R2000/39), operators cannot rely on DGAC logbook entries to discharge those specific obligations. That distinction affects decisions about whether prior maintenance satisfies the AD.

Key duties in the AD are set out in the two numbered Requirements and the Compliance clause. Duty 1 is an affirmative duty to determine the applicability of each CAA (NZ) AD listed in Table 1. Duty 2 is an affirmative duty to perform the actions required by any applicable CAA (NZ) AD that has not previously been accomplished. The Compliance clause adds a temporal limitation: these duties must be discharged within 30 days after this AD became effective (effective date 5 December 2007) or before the issue of a Certificate of Airworthiness for the aircraft, whichever occurs first. The instrument therefore creates an early-action requirement tied to administrative certification.

Rights or reliefs in the AD are limited and narrowly specified. Note 1 establishes an evidentiary equivalence right: where a CAA (NZ) AD refers to an equivalent DGAC AD and the DGAC AD is reflected in the aircraft log books as having been complied with, then no further action is required for the equivalent CAA (NZ) AD. That is the sole explicit mechanism in the AD for satisfying obligations without undertaking the listed NZ AD. The AD also acknowledges in the Background that, because of date of manufacture or aircraft configuration and modification status, not all ADs in Table 1 will be applicable to all models. That acknowledgement operates as a recognition of a de facto exemption for aircraft whose specific configuration renders a listed AD inapplicable, but it leaves determination of applicability to the owner/operator.

The AD does not, in the text provided, create a process for seeking an alternative method of compliance, nor does it set out appeals or review rights within the document itself. It also does not specify penalties or enforcement processes in its body. The only procedural concession is the logbook equivalence for DGAC ADs where the NZ AD references such equivalence. For obligations linked to Certificate of Airworthiness issuance, the AD effectively uses the certification process as both a trigger and, potentially, an enforcement point: compliance is required prior to a CoA if that occurs before 30 days elapse.

Practical duties that flow from the AD include: obtaining and reading the referenced CAA (NZ) AD texts (Note 2 supplies a URL), examining aircraft logbooks and modification records to assess whether each AD applies, documenting determinations and any remedial actions in the maintenance records, and completing the physical actions required by the referenced ADs where they apply and are outstanding. Where a DGAC AD is referenced in the CAA (NZ) AD and logbook evidence exists, the duty to perform the CAA (NZ) AD falls away for that particular AD, but the operator carries the burden of proof via logbook entries.

Because the AD references foreign ADs and leaves technical detail to them, operators have the practical right to rely on the foreign AD texts for the technical scope of required actions. The AD’s reliance on foreign documents imposes an interpretative duty on the operator and their maintenance provider to ensure the foreign AD text is correctly identified and complied with.

The AD text provided does not include an express penalties clause or an enforcement section. The document prescribes mandatory actions and a compliance period, and links compliance to Certificate of Airworthiness issuance: the Compliance provision requires performance of the two Requirements within 30 days of the AD’s effective date or prior to issue of a Certificate of Airworthiness, whichever occurs first. That linkage functions as a practical enforcement mechanism because failure to demonstrate compliance may delay or prevent issuance of a Certificate of Airworthiness for an aircraft of the specified type.

Because this AD is administrative in form and issued by the Civil Aviation Safety Authority (the signature block records David Punshon, Delegate of CASA, and the date 29 November 2007), enforcement in practice will fall to CASA’s usual oversight and certification processes. The AD itself does not set out sanctions, fines, or criminal consequences; it only sets out operational obligations and a compliance timeline. The absence of express penalties in the instrument means parties must look to the broader regulatory regime (for example, Civil Aviation safety and regulatory statutes and regulations) to identify formal enforcement measures, licensing consequences, or statutory penalties that CASA may apply for non-compliance. The AD as provided does not state those statutory powers.

Two operational enforcement features are present in the document: first, the short deadline linked to CoA issuance creates an administrative lever. If compliance cannot be shown, a CoA may be withheld. Second, the requirement to record equivalence (where the NZ AD cites a DGAC AD) in the aircraft log books means that logbook review becomes a point of compliance verification; inspectors can check entries that the AD itself recognises as discharging some obligations.

The AD also identifies which foreign ADs are equivalent and which are not (Table 1). For ADs where the Equivalent DGAC AD column reads "No Equivalent," operators cannot use DGAC logbook entries to discharge the NZ AD requirement; lack of that equivalence increases the practical enforcement exposure for those particular ADs.

Because the AD does not specify penalties, affected parties should presume that enforcement, if necessary, will follow the standard CASA administrative and regulatory toolkit and that inspectors and certification officers will treat the AD as mandatory for the specified types. The AD’s wording indicates that CASA expects the listed ADs to have safety relevance despite some being one-time actions where the compliance date has passed; CASA therefore converted the overseas ADs into local mandatory obligations via this instrument.

This AD operates by reference and transposition rather than by restating technical requirements, so its legal operation is integrative: it imports foreign regulator AD obligations (CAA (NZ) ADs and, where listed, equivalent French DGAC ADs) into Australian enforcement via CASA’s AD issuance. The AD therefore creates a regulatory bridge between CASA’s Australian jurisdiction and the design-state ADs of other authorities. Note 1 explicitly recognises that some CAA (NZ) ADs refer to equivalent DGAC ADs as a means of compliance; the AD instructs that, where the DGAC AD compliance is recorded in logbooks, no further action is required for the equivalent CAA (NZ) AD. That recognition builds cross-jurisdictional deference into the Australian AD’s operation.

The AD also interacts with the administrative process for issuance of a Certificate of Airworthiness. The Compliance clause conditions required actions on a fixed calendar period or CoA issuance, whichever comes first. That creates a practical intersection with CoA procedures: evidence of compliance will be relevant to certification decisions and audits. The AD does not, however, specify how CASA will verify compliance at the point of certification, nor does it provide an internal appeals process within the instrument.

The instrument’s background remarks that Alpha Aviation Design Ltd is the Type Certificate holder. That fact situates the AD within the broader design approval framework: while the AD does not directly delegate duties to the TC holder, interaction with design approvals, service bulletins and manufacturer data is implied. In practice, maintenance organisations may need data or parts from the TC holder to carry out terminating actions; the AD presumes such interactions when it requires operators to "perform the actions required by the CAA (NZ) AD" (Requirement 2).

The AD’s reliance on foreign ADs means that legal effects outside CASA’s instrument remain relevant. For example, if a CAA (NZ) AD referenced a particular technical compliance action tied to a DGAC AD, and the DGAC AD has been superseded or amended, the operator must ensure they are following the correct version because the AD treats equivalence only where the original CAA (NZ) AD identifies the DGAC AD as a means of compliance. Note 2 supplies a URL for accessing NZ CAA ADs; this evidences that the AD expects operators to consult the foreign ADs directly. The AD does not alter or displace the text of the foreign ADs; it makes performance of those ADs a local obligation where applicable.

Because the AD does not cite or reproduce any Australian statutes, users are not told within the instrument how it fits into the broader regulatory penalties or enforcement mechanisms. Those interactions must be assessed by consulting the underlying Australian aviation safety statutes and CASA’s enforcement policies outside this AD document.

The provided AD document does not include any amendments to AD/ROBIN/39 itself beyond its original signature and effective date. The instrument header contains repeated identifiers including "AD/ROBIN/39", "State of Design Airworthiness Directives", and "1/2008 DM". The AD lists the effective date of this CASA instrument as 5 December 2007 (final compliance paragraph) and is signed by David Punshon on 29 November 2007. No later amendments, revisions, or superseding notices are included in the text provided.

The Table 1 entries list a set of New Zealand CAA ADs with their effective dates, which reflect the amendment history of those foreign ADs rather than of the CASA AD itself. Most of the listed NZ ADs carry an effective date of 29 June 2006. DCA/R2000/26 shows an effective date of 29 September 2006 and DCA/R2000/39 shows an effective date of 31 August 2006; these dates indicate when the respective NZ ADs became effective in New Zealand (as recorded in Table 1). The CASA AD thereby imports a set of foreign ADs that have their own effective dates and histories.

Because this AD references external documents rather than embedding their text, any amendment to the NZ CAA ADs or the DGAC ADs would, in practice, affect what actions are required by Australian operators if those foreign ADs are still listed or referenced. The CASA AD, however, does not include an express mechanism for automatic incorporation of future amendments to the listed foreign ADs; it lists the relevant NZ CAA AD numbers and effective dates as they stood at the time the CASA AD was issued. That means operators should verify the current status of each referenced NZ AD and any subsequent revisions by consulting the NZ CAA or the published AD sources (Note 2 gives a URL for the NZ CAA AD home).

The AD lists 20 NZ CAA AD entries in Table 1 (DCA/R2000/1 through /12; /18; /20; /26; /29; /35; /36; /38; /39). These entries represent the universe of foreign ADs CASA considered relevant at the time of issuance. The AD itself shows no record of being amended in the provided text; any amendment history beyond the instrument’s initial signature and effective date is not present in the source material supplied.

The supplied document contains no litigation history. There are no references to court decisions, administrative appeals, judicial reviews, or other disputes in the text. The AD is an administrative instrument issued by the Civil Aviation Safety Authority and signed by a CASA delegate; the document does not record any legal challenges to its issuance, nor does it cite any case law.

Because the AD does not include litigation references, readers seeking information on any judicial treatment or appeals relating to AD/ROBIN/39 must search external legal and administrative records, tribunal decisions or court databases. The AD itself provides no narrative or procedural detail about contestation, review rights, or appeals processes related to its application.

Given the absence of litigation information in the source, practitioners should not assume litigation has or has not occurred; they should check relevant administrative and court registries if litigation history is material to a particular compliance or transactional matter.

There are several material practical pitfalls and interpretative traps in this AD as drafted. First, the AD places the initial onus on the owner/operator to determine applicability of each listed NZ CAA AD. That is a non-trivial investigatory task. Table 1 contains 20 separate NZ AD entries, each with a different subject matter (for example, "Aft Fuselage Side Cover Plates", "Battery Protection Fuse - Modification", "Fuel Tank Filler Caps", "Aileron Bellcrank", "Cabin Compartment Barrier - Inspection and Modification", "Fuel Shut - Off Mechanism"). Operators must obtain the full text of each referenced NZ AD to assess technical applicability and required actions. The AD does not summarise the technical scope of each NZ AD; it only provides brief titles and references, so an operator who fails to retrieve and read the foreign AD text risks misunderstanding applicability or technical requirements.

Second, the equivalence mechanism in Note 1 is narrow: it only applies where the CAA (NZ) AD refers to an equivalent DGAC AD and that DGAC AD compliance is reflected in the aircraft log books. Two related pitfalls arise. One, the operator must locate and interpret the relevant DGAC AD and the CAA (NZ) AD to confirm the equivalence was properly cited. Two, the logbook entry must be sufficiently precise to demonstrate that the DGAC AD was complied with and that the compliance matches the CAA (NZ) AD’s requirements. A generic or incomplete logbook entry may be insufficient; the AD requires that the DGAC AD "is reflected in the aircraft log books as been complied with" which invites scrutiny of the logbook language.

Third, some Table 1 entries explicitly show "No Equivalent" in the Equivalent DGAC AD column (DCA/R2000/38 and DCA/R2000/39). For those ADs the operator cannot rely on DGAC logbook entries to discharge the obligation; the operator must perform the NZ AD action if applicable and outstanding. That increases the immediate remediation burden for those items.

Fourth, the compliance timing is tight. The instrument requires actions within 30 days after the effective date (i.e., within 30 days of 5 December 2007) or prior to the issue of a Certificate of Airworthiness, whichever occurs first. If an operator is in the process of obtaining a CoA, the CoA trigger may demand earlier compliance. This creates coordination risk between maintenance providers and certification authorities; if actions cannot be completed before a CoA application is determined, the CoA might be delayed.

Fifth, the Background notes that the listed ADs include some one-time actions "for which the compliance date and/or period has passed" and some recurring inspection/action requirements until a terminating action is applied and that terminating action’s compliance date and/or period has passed. That causes a factual nuance: an operator may find that, for a particular AD, the compliance window in the foreign AD has already expired and that a terminating action has not been recorded; it may be unclear whether the foreign AD requires a late compliance action or whether non-applicability results from manufacture date. Determining whether a given AD is inapplicable because the aircraft was manufactured after the risk period, or whether a late remedial action is required, may require technical records and possibly consultation with the TC holder or CASA.

Sixth, the AD references external documents via a web link (Note 2: http://www.caa.govt.nz/Airworthiness_Directives/Airworthiness_Directives_Home.htm). That link may change over time; relying on a single URL without alternative record sources creates operational risk. Operators should secure copies of the referenced CAA (NZ) AD texts for their records.

Seventh, because the AD does not set out enforcement penalties, an operator might underestimate the consequences of non-compliance. While the AD ties compliance to CoA issuance, the absence of an explicit on-the-face penalty requires operators to consult CASA’s general enforcement regime to ascertain the practical consequences. That legal uncertainty can increase transaction costs and risk.

Finally, because the AD transposes foreign ADs by reference, any operator who treats the AD as a mere checklist of table titles rather than consulting the foreign ADs risks non-conformance with the detailed technical measures. The AD’s brevity on technical measures is useful for a high-level mandate but is a compliance risk if practitioners do not follow up with the full foreign AD texts.

Step 1: Confirm applicability to your aircraft. Check whether your aircraft is one of the models listed in the Applicability clause: Robin HR200-100, HR200-120, HR200-120B, HR200-160, HR200-100S, R2160, R2100, R2100A, R2160D, R2112, R2160I and R2120U. If it is not, the AD does not apply on its face.

Step 2: Obtain the full texts of the CAA (NZ) ADs listed in Table 1. The AD lists 20 NZ CAA ADs (DCA/R2000/1 through /12; /18; /20; /26; /29; /35; /36; /38; /39) and gives a URL for NZ CAA ADs (Note 2). Retrieve the operative NZ AD documents and any related service information, SBs, or amendments referenced by them.

Step 3: For each listed NZ AD, conduct a factual determination of applicability. That requires review of the foreign AD text against the aircraft’s serial number, date of manufacture, configuration, and modification history. The AD’s Requirement 1 imposes this duty. Document the determination in the aircraft maintenance records.

Step 4: Where the CAA (NZ) AD refers to an equivalent DGAC AD, check maintenance records and log books for entries showing compliance with the DGAC AD. If an appropriate DGAC AD compliance entry exists in the log books, Note 1 in the CASA AD states that no further action is required for the equivalent NZ CAA AD. Ensure logbook entries are sufficiently detailed to demonstrate which AD and which action were complied with, including dates, parts changed, and references to the DGAC AD number.

Step 5: For any CAA (NZ) AD that is applicable and has not previously been accomplished, perform the actions required by the CAA (NZ) AD. That is Requirement 2. Engage appropriately certificated maintenance organisations and personnel to carry out inspections, modifications, replacements or terminating actions as specified in the foreign AD. Retain records of the work performed, parts installed and relevant certifications.

Step 6: Respect the compliance timing. Complete Steps 1-5 within 30 days after the effective date of this AD or prior to the issue of a Certificate of Airworthiness, whichever occurs first. The AD’s Compliance paragraph sets this deadline. If you are preparing an aircraft for CoA issuance, ensure these steps are completed and evidenced before the CoA application is finalised.

Step 7: Update aircraft log books and maintenance records with explicit entries showing the determinations, the CAA (NZ) AD numbers addressed, the actions taken (or the DGAC AD reference relied upon), dates and the identity and signature of the authorised maintenance certifier. Because the AD recognises DGAC AD compliance only where that fact is reflected in the log books, comprehensive maintenance records are essential for establishing that obligations have been met.

Step 8: If a terminating action is identified by a referenced AD, and that terminating action has been completed, document that the terminating action was applied and the date. This will stop recurring inspection obligations where the foreign AD provides for a terminating action and the termination has occurred and been recorded.

Step 9: If any doubt arises about applicability, equivalence, or the scope of the technical remedy in a foreign AD, consult: (a) the Type Certificate holder (Alpha Aviation Design Ltd is named in the Background as the TC holder), (b) the NZ CAA AD issuing authority’s current documentation, and (c) CASA for clarification. Keep written records of any requests for clarification and any responses received.

Step 10: Maintain a compliance file for audits and future transfer or sale. Given the AD’s linkage to Certificate of Airworthiness issuance and potential involvement of prospective buyers, financiers, or regulators, keep copies of the foreign ADs, your applicability determinations, maintenance work orders, parts invoices, logbook entries, and certification signatures in a readily accessible format.

Operational notes: prioritise the items listed as "No Equivalent" because those cannot be discharged by DGAC logbook entries. Also prioritise any ADs that impose terminating actions which may eliminate future inspection workloads. Finally, verify current versions of the foreign ADs before acting, because CASA’s AD imports the NZ ADs as they existed at the time; amendments to those foreign ADs after the CASA AD’s issue may affect future obligations and technical detail. If a foreign AD has been superseded, ensure you use the operative or most relevant version that was intended to be enforced by the CASA AD and document your basis for compliance.