AD/F50/102 - State of Design Airworthiness Directives

AD/F50/102 implements three principal legal and technical concepts: State of Design AD incorporation by reference, applicability determination, and retrospective catch‑up compliance. The Directive is framed as a State regulator's instrument to ensure that "State of Design ADs are complied with" for Australian‑registered or soon‑to‑be‑certified Fokker F50 (F27 Mk 50) aeroplanes.

Incorporation by reference: CASA does not reproduce the substantive technical measures contained in the Netherlands ADs. Instead, it tells Australian operators to consult and apply those foreign ADs (or later EASA‑approved revisions). That is, the substantive technical obligations remain located in the Netherlands/EASA AD documents; CASA's instrument makes those obligations enforceable in the Australian context by requiring operators to determine applicability and to perform the actions where necessary. The Directive explicitly directs the reader to the EASA AD website to access the Netherlands ADs.

Applicability determination: The Directive distinguishes between an obligation to apply an AD and the reality that not every AD applies to every variant of the type. The first numbered requirement is to "Determine the applicability of the Netherlands Airworthiness Directives (AD) listed in Table 1." The Directive therefore places the onus on the aircraft operator, owner or maintenance organisation to assess whether each listed AD is relevant to the specific aircraft based on manufacture date, configuration and modification status. The Directive itself records CASA's understanding that some listed ADs will not apply to some aeroplanes.

Retrospective catch‑up compliance: Table 1 consists largely of Netherlands ADs that are once‑only actions for which the compliance date or compliance period has already passed. The Directive's background statement explains that these ADs "require once‑only actions for which the compliance date and/or period has passed" and that CASA has determined they may be applicable to recently registered Australian aircraft. The mechanical effect is to require operators who have not previously performed those once‑only actions, despite the original compliance dates having passed, to now perform them. The Directive thus operates as a catch‑up instrument.

Temporal split by certificate status: The compliance timing is conditional. If a certificate of airworthiness has not yet been issued for the aircraft, compliance must occur before issuance. If a certificate has been issued, the Directive requires completion within 60 days after the Directive's effective date (7 July 2010). This creates a temporal compliance asymmetry that binds new entries to the Australian register before certification and requires in‑service aeroplanes to remedy gaps promptly.

Scope and content of technical actions: The Table 1 titles indicate a broad range of technical measures , placards, inspection or replacement of components (propeller bolts, fuel control units, autopilot computer, fire detection elements), wiring checks, structural brace or strut modifications, cockpit recorder modifications, and speed limitation placards. The Directive does not provide technical detail; it delegates that detail to the Netherlands ADs and their EASA‑approved revisions.

Authority and administrative form: The Directive is issued by CASA (signed by a delegate) and formatted as a domestic AD that references State of Design ADs. It is an example of a regulator imposing imported technical obligations to maintain a consistent safety standard across jurisdictions for a type certificated abroad.

AD/F50/102 directly affects every party with operational, maintenance, certification or ownership responsibility for Fokker F50 (F27 Mk 50) series aeroplanes in or entering the Australian register. That includes aircraft owners, operators (airlines, charter operators, lessors), maintenance organisations and certificating authorities responsible for issuing certificates of airworthiness.

Owners and operators bear the primary compliance cost. The Directive places the onus on them to determine the applicability of each Netherlands AD listed in Table 1 against their aircraft's manufacture date, configuration and modification history. Where an AD is applicable and not previously accomplished, the owner/operator must perform the specified actions. Practical actions may include ordering parts, scheduling inspections or modifications, allocating maintenance man‑hours, and temporarily removing the aeroplane from service for the work. The Directive makes completion a precondition to the issue of a certificate of airworthiness for un‑certificated aircraft, and for certificated aircraft imposes a 60‑day compliance window from the Directive's effective date.

Maintenance organisations and approved maintenance providers are affected operationally, because they must interpret the Netherlands ADs (or later EASA‑approved revisions) and implement the technical measures. The Directive requires them to have access to the State of Design AD texts (the Directive points to the EASA AD website). Maintenance providers will need the technical capability, parts supply, and possibly engineering approvals to carry out modifications or replacements that these ADs specify. Some ADs may require specialised parts (e.g. autopilot computer replacement, propeller component checks), which can raise logistical costs if parts are obsolete or long lead times exist.

The Australian certificating authority and CASA itself are affected administratively. CASA's conditional requirement that, where no certificate exists, compliance occurs before issuance, effectively makes compliance a precondition tying technical AD compliance to the certification process. CASA (or its delegates issuing certificates) will need processes to verify that applicants have properly determined applicability and performed required actions or can demonstrate earlier compliance. The Directive is issued by a CASA delegate (signed by Mike Higgins), indicating internal CASA administrative allocation to produce and enforce the AD.

Lessors and financiers are indirectly affected because actions required by the Netherlands ADs may result in ground time, costs and changes to asset condition. They may need to be consulted if modifications change weight or performance characteristics or if the work is chargeable under leasing arrangements. The Directive does not discuss commercial allocation of costs, so owners and operators should review leases or contracts.

Finally, because the Directive imports foreign ADs, those who hold maintenance records and historical compliance evidence (previous registries, original manufacturer records) are crucial. Where ADs are once‑only and compliance dates have passed, proof of earlier accomplishment will determine whether further action is necessary. The Directive explicitly notes some ADs may not be applicable depending on manufacture or modification status; the practical burden of demonstrating non‑applicability sits with the responsible parties.

Duties

• Determine applicability: The Directive places a positive duty on the responsible party to "Determine the applicability of the Netherlands Airworthiness Directives (AD) listed in Table 1." This is the first and foundational duty; without it, the remainder of the Directive cannot be operationalised.

• Perform required actions where applicable: The second duty is contingency‑based and compulsory where an AD is applicable and not previously accomplished. The Directive requires the operator to "perform the actions required by that AD or later EASA‑approved revision." That duty imports the substantive, technical obligations from each listed Netherlands AD into the responsibility set of the Australian operator.

• Meet the timing requirements: The Directive creates two timing rules. If the aircraft does not yet have an Australian certificate of airworthiness, the imported AD requirements must be complied with before issue. If the aircraft already has a certificate of airworthiness, the operator has 60 days after the directive's effective date to comply. The duty therefore includes a temporal component which may force expedited maintenance planning for in‑service aeroplanes.

• Use EASA‑approved revisions where available: The Directive allows compliance by reference to a "later EASA‑approved revision" of a Netherlands AD. The duty therefore encompasses keeping updated with any EASA‑approved revisions and applying those where they supersede the Netherlands AD text.

Rights and practical entitlements (as expressed or implied by the Directive)

• Right to determine non‑applicability: The Directive recognises that some ADs listed may not be applicable due to manufacture date, configuration or modification status. That recognition functions as an entitlement to a reasoned determination that an AD does not apply; the burden to make that determination sits with the operator. The Directive's statement that "CASA appreciates ... some of the ADs listed ... will not be applicable" formalises that the non‑applicability determination is a legitimate outcome.

• Right to rely on later EASA‑approved revisions: Operators are permitted to comply with "later EASA‑approved revision" of a listed Netherlands AD. Practically, that provides a right to adopt an updated or clarified technical requirement from the EASA process, rather than being bound strictly to the historical Netherlands AD text as of its issue date.

• Entitlement to access the referenced ADs: The Directive points to the EASA AD database as the source of the Netherlands ADs. While not a "right" in a legal sense, the Directive explicitly directs operators where to obtain the texts they must apply.

Operationally, the Directive does not articulate procedural rights such as appeal or review within its own text, nor does it specify documentation or evidence standards to demonstrate compliance; it likewise does not set out penalties or enforcement mechanisms in the text. The Directive's duties are operationally rigorous: responsible parties must identify applicability, then either document why a listed AD does not apply or carry out the specified corrective/inspective/modify actions within the identified timeframe.

The AD text itself sets mandatory compliance obligations and a fixed effective date, but it does not specify civil or criminal penalties, administrative fines, or enforcement procedures within its wording. The instrument is an explicit regulatory directive: it becomes effective on 7 July 2010 and requires compliance before issuance of a certificate of airworthiness (if none exists) or within 60 days for certificated aircraft. Those temporal conditions are the primary enforcement levers articulated in the document.

What the Directive does specify, and which is relevant to enforcement logic, is the linkage between compliance and certification processes. By requiring compliance before the issue of a certificate of airworthiness for un‑certificated aircraft, the Directive empowers the certificate issuance process as a control point. Issuing officers will, in practice, require demonstration that required actions have been completed before granting a certificate. For aircraft already certificated, the compact 60‑day window creates an administrative obligation that CASA is placing on operators to remedy past non‑compliances quickly. The Directive's signed authority (a CASA delegate) is the formal provenance of these obligations.

The absence of explicit penalty language in the document means the AD itself does not enumerate sanctions. That silence requires readers to infer enforcement will rely on CASA's broader regulatory powers and certification controls outside this text (for example, the ability to refuse certificate issuance or to take enforcement action under general aviation safety statutes and regulations). However, those broader powers are not stated in this instrument and therefore cannot be asserted as part of this Directive's text. What the Directive does provide is a clear regulatory standard and timeline; failure to meet that standard will place the operator in breach of the Directive and therefore in a non‑compliant posture with CASA.

Practically, the enforcement risk profile for an operator is therefore:

• For a new certification applicant, non‑compliance will prevent issuance of a certificate of airworthiness until the required actions are completed.

• For certificated aircraft, failure to meet the 60‑day compliance window will leave the operator non‑compliant with a CASA AD; in operational terms this will likely expose the operator to regulatory follow‑up, and may trigger administrative processes for rectification. The Directive gives CASA the factual basis to require rectification.

• For maintenance organisations, incorrect or incomplete applicability determinations that later prove erroneous create a risk that additional actions will be mandated and that inspections or rework could be required.

Because the Directive references external Netherlands/EASA ADs, enforcement may also depend on the clarity of those ADs and on whether the operator followed a later EASA‑approved revision as permitted. The Directive grants the option to comply with later EASA‑approved revisions; a disputed determination about whether the revision was applicable or whether the work performed satisfied the requirement could become an enforcement focal point.

In short, this instrument defines the enforceable obligations and timings but does not itself state discrete penalties; enforcement will flow from CASA's implementation of its regulatory functions (certification checks, compliance audits or other enforcement actions), using the Directive as the standard against which performance is measured.

AD/F50/102 operates as a regulatory import mechanism that ties Australian airworthiness oversight to the State of Design's airworthiness directives, specifically Netherlands ADs as accessible via the EASA AD database. The Directive's fundamental interaction with other legal instruments is therefore one of incorporation and harmonisation: CASA is requiring Australian operators to comply with foreign State of Design ADs (or later EASA‑approved revisions) as part of Australian regulatory compliance.

Interaction with certification law and procedures is explicit. The Directive conditions compliance on certificate of airworthiness status: if a certificate of airworthiness has not been issued, compliance must be completed before issuance; if a certificate has already been issued, operators have 60 days to comply. That requirement integrates the AD into the certification framework. Practically, the directive becomes a pre‑issue requirement for new certificates and an in‑service compliance requirement for existing certificates, connecting the technical AD obligations to domestic certification processes.

The instrument also interacts with maintenance and continuing airworthiness obligations. Although the Directive does not recite maintenance law provisions, it imports technical requirements from the State of Design ADs that will typically be executed under an organisation's approved maintenance procedures and recorded in maintenance logs. The Directive's demand to "perform the actions required by that AD or later EASA‑approved revision" makes those foreign ADs operationally binding in Australia for the listed aeroplanes.

Because the Directive references the EASA AD database, it also interacts with international regulatory material. Operators must consider both the original Netherlands ADs and any subsequent EASA‑approved revisions. The Directive therefore creates an operational dependency on EASA's ongoing AD regime; future EASA revisions can be the authorised compliance vehicle, subject to the terms of those revisions.

The Directive does not explicitly discuss interactions with lease contracts, manufacturer warranties, or commercial arrangements. However, in practice, performing once‑only retroactive actions that were originally required in the State of Design may trigger contractual obligations (for example, lessor/lessee cost allocation, responsibilities under transfer agreements) and could affect continuing airworthiness records that underpin other regulatory obligations. The Directive's requirement that some actions be completed before issue of a certificate of airworthiness may affect sale or import transactions and therefore contract completion.

Finally, the AD does not incorporate or reference domestic legislative penalty provisions or enforcement pathways within its own text; it is a regulatory instrument that must be read alongside the broader CASA regulatory framework and the legislative instruments that empower CASA to issue ADs and to enforce compliance. The Directive's linking of compliance to certification suggests that CASA intends the Directive to be applied within the usual certification and surveillance processes, creating practical ties to other legal and administrative requirements governing Australian aircraft operation.

The document presented is a single CASA Airworthiness Directive labelled AD/F50/102, with metadata indicating the directive is 12/2010 and dated 15 June 2010, becoming effective on 7 July 2010. The directive itself does not record any previous versions of AD/F50/102, nor does it include an amendment log for the directive text. The document's content is simple and administrative: it lists State of Design (Netherlands) ADs and sets out the two requirements and the compliance timetable.

The Directive imports a number of Netherlands ADs, each with its own issue date shown in Table 1. Those Netherlands ADs have their own independent issue and revision histories (for example, AD numbers and issue dates in Table 1 range from 87‑090, issue date 7 December 1987, through to 97‑060, issue date 30 June 1997, and later entries into the 1990s). AD/F50/102 expressly permits compliance with a listed Netherlands AD "or later EASA‑approved revision," which implicitly recognises that the State of Design ADs may have subsequent revisions or superseding instruments issued by EASA. The Directive therefore allows the operator to adopt later revisions authorised by EASA, but AD/F50/102 itself does not record or track any such later revisions.

The only internal dating and versioning in the CASA AD is the following:

• AD identifier: AD/F50/102
• Date signed: 15 June 2010 (signed by Mike Higgins, Delegate of CASA)
• Effective date: 7 July 2010
• Document code: 12/2010

No rescission, amendment or supersession of earlier CASA ADs is recorded in the text provided. The directive does, however, function as a consolidating instrument in the sense that it aggregates a list of State of Design ADs as of its issuance and requires operators to check their applicability. Any subsequent CASA action that amended AD/F50/102 or replaced it would need to be published separately; that is not present in this document.

Because AD/F50/102 allows compliance by reference to later EASA‑approved revisions, operators must monitor the EASA AD database for changes to those Netherlands ADs and for any superseding EASA ADs. AD/F50/102 itself does not identify particular EASA revision numbers or dates; it leaves that identification task to the operator performing the applicability check.

In short, the directive contains a single issuance event (15 June 2010, effective 7 July 2010), lists a set of Netherlands ADs with their historic issue dates, and provides flexibility to comply with later EASA‑approved revisions. No amendment history of the CASA AD itself is set out in the supplied text.

The text of AD/F50/102 does not record any litigation history, judicial review, or administrative appeals related to this Directive. There are no case citations, tribunal decisions or references to disputes in the document itself. The instrument is an administrative regulatory directive issued by CASA and signed by a delegate; the document content is confined to regulatory requirements, Table 1 of referenced Netherlands ADs, compliance timing and a background statement.

Because the document contains no litigation record, this instrument does not, on its face, identify any precedential or contested legal point that has been tested in court or tribunal. The Directive does not include a statement of rights of review or appeal within its own text, nor does it set out internal review procedures. Any challenge or litigation arising from the Directive would therefore be external to the document and is not recorded here.

For a practitioner seeking to determine whether this Directive has been the subject of subsequent judicial or administrative proceedings, the document as supplied provides no evidence either way. The Directive does, however, point to external materials (the EASA AD database) for the technical mandates, and those State of Design ADs may themselves have histories of amendment or contest in their jurisdiction; nothing of that history is contained in the CASA text.

If a client requires information on whether AD/F50/102 has been subject to legal challenge, remaking, or replacement since 7 July 2010, the next steps are to (a) consult CASA's AD register and archives for any superseding CASA ADs or formal revocations/amendments, and (b) search administrative and judicial records for any proceedings naming CASA or AD/F50/102. Those searches are outside the text of the Directive itself and not recorded in the supplied instrument.

Several practical pitfalls and friction points derive directly from the Directive's structure and wording:

1. Retroactive catch‑up obligations: Table 1 mainly lists once‑only Netherlands ADs whose original compliance deadlines have passed. The Directive makes those obligations current for recently registered Australian aircraft. If an operator registers an aeroplane in Australia that previously operated elsewhere, absence of documentation proving prior compliance will translate into mandatory remedial work. The Directive's background expressly notes these are once‑only actions "for which the compliance date and/or period has passed."

2. Burden of applicability determination: The Directive places the initial responsibility on the operator to determine applicability for each listed Netherlands AD. This is a technically demanding task: it requires access to the Netherlands AD text, knowledge of the aircraft's build standard and modification history, and technical competence to interpret conditional applicability clauses in the foreign ADs. The Directive recognises possible non‑applicability but does not prescribe the standard of proof or documentation required to support a non‑applicability finding.

3. Evidence and records gap risk: Because many ADs are historic, maintenance records proving prior compliance may not be easily obtainable, especially for older aeroplanes that changed operators or registries. The Directive's practical effect is that lack of documentary proof will likely necessitate physical inspection or corrective work, which can be costly and time consuming.

4. Parts obsolescence and logistics: Some listed ADs require replacement (for example autopilot computer replacement, specific propeller components). For older types, spare parts can be scarce or obsolete, causing long lead times and potential extended aircraft downtime. The Directive gives no transitional relief for parts unavailability.

5. Ambiguity over "or later EASA‑approved revision": While the option to comply with later EASA‑approved revisions can ease technical compliance when improved procedures are available, it also creates a source of uncertainty. Operators must identify whether a later EASA revision exists and whether that revision changes the scope, means or compliance status compared with the original Netherlands AD. There is room for interpretative dispute over which revision is "later" and "EASA‑approved" for the purposes of compliance.

6. Timing pressure for certificated aircraft: The 60‑day compliance window for aircraft with existing certificates of airworthiness is short. Operators may find it hard to locate records, order parts and schedule maintenance within that window. The Directive does not provide an extension mechanism within its text.

7. Certification linkage: For un‑certificated aircraft, the Directive requires compliance before issue of the certificate of airworthiness. That condition effectively makes the AD a gating item for import, registration, or returning a stored aircraft to service. Sellers, buyers and lessees need to be alert to this gating effect.

8. Cross‑jurisdictional reliance: The Directive requires Australian operators to follow Netherlands/EASA ADs. Differences in regulatory drafting styles, references to local standards, or to modifications approved under different authorities may complicate direct transposition into Australian maintenance practice. The Directive does not provide specific local engineering acceptance procedures.

9. No enforcement detail in text: Because the Directive does not specify enforcement mechanisms or penalty provisions, operators lack clarity within the document about the formal processes CASA will use if non‑compliance is identified. That creates uncertainty in planning risk responses.

10. Wide technical variety: Table 1 contents span placards and labels through structural struts and engine systems. This breadth means a wide range of competencies and parts are potentially implicated; operators must coordinate multiple technical disciplines to resolve compliance.

Users must therefore plan for documentary searches, potential inspections and parts logistics, prepare technical interpretations for applicability, and be ready to document non‑applicability when appropriate. The Directive supplies the list and the obligation, but the practical compliance path is materially operational and record‑intensive.

The Directive sets out a concise compliance algorithm. Implementing it requires administrative, technical and evidentiary steps; below is a practical, source‑grounded compliance checklist derived from the Directive's text.

1. Identify affected aeroplanes: Confirm the fleet or individual Fokker F50 (F27 Mk 50) aeroplanes that are on the Australian register or are intended to be certificated in Australia. AD/F50/102 applies to "Fokker Aircraft B.V. F27 Mark 050 aeroplanes" as listed in the applicability line.

2. Obtain the Netherlands AD texts: For each AD number listed in Table 1, obtain the full Netherlands (State of Design) AD text and any subsequent EASA‑approved revisions. The Directive explicitly directs readers to the EASA AD database (http://ad.easa.europa.eu/). The Directive permits compliance with "that AD or later EASA‑approved revision."

3. For each listed Netherlands AD, perform an applicability assessment: The Directive's first requirement is to "Determine the applicability of the Netherlands Airworthiness Directives (AD) listed in Table 1." This step requires comparing each AD's applicability criteria (aircraft serial numbers, SB incorporation status, mod status, production blocks) against your aircraft's build standard, modification and configuration records. If an AD contains conditional applicability (e.g. only for aircraft with a particular part installed), document the basis for applicability or non‑applicability.

4. Compile and retain documentary evidence: For any AD you determine is not applicable, compile and retain the documentary evidence that supports that determination: build sheets, modification records, parts serial numbers, STC records, logbook entries, and prior AD compliance records. The Directive notes CASA appreciates some ADs will not be applicable due to manufacture date or configuration , however the onus of proof lies with the operator.

5. For any AD you determine is applicable and not previously accomplished, plan and execute the required actions: The Directive requires you to "perform the actions required by that AD or later EASA‑approved revision." Some actions may be inspections, replacements, placard installations, or structural modifications. Ensure work is performed under the appropriate approved maintenance authority and signed off in the aircraft maintenance records. If a later EASA‑approved revision provides an alternative method of compliance (AMOC) or changed compliance method, validate that it is an "EASA‑approved revision" before relying on it.

6. Schedule around the Directive's timing: If the aircraft does not yet have an Australian certificate of airworthiness, the Directive requires completion before issuance. If the aircraft already has a certificate of airworthiness, the Directive requires completion within 60 days after the Directive's effective date (7 July 2010). Prioritise ADs whose non‑compliance would prevent certificate issuance for new registrants, and schedule urgent work for in‑service aircraft to meet the 60‑day deadline.

7. Address parts and logistics early: For ADs requiring parts replacement (e.g. autopilot computer, fire detection elements, propeller bolts), source parts promptly. If parts are obsolete or unavailable, document efforts to source parts and liaise with CASA or your nominated certifying authority as early as possible; the Directive does not provide for extensions, so proactive engagement is prudent.

8. Maintain clear maintenance records and entries: Record all determinations, inspections, modifications and part replacements in the aircraft's maintenance logbooks and records, with reference to the specific Netherlands AD number and revision applied. While the Directive does not prescribe record formats, accuracy in serial numbers, task cards, signed maintenance releases and compliance statements will be required to demonstrate compliance, and are essential where compliance is a precondition for certification.

9. Monitor EASA revisions: Because the Directive permits compliance with a "later EASA‑approved revision," maintain a record of the version of the AD you relied on at the time of compliance. If EASA issues a later revision that materially alters compliance requirements after you have completed work, retain evidence that the revision post‑dated your compliance.

10. Communicate with CASA where necessary: If there is ambiguity about applicability, or difficulty in meeting the timing requirements (for example because of parts unavailability or complex inspections), engage CASA promptly to document the problem and seek guidance. The Directive itself does not provide extension mechanisms; early communication provides the regulator with notice and may shape any subsequent administrative response.

11. Coordinate with contractual parties: If the aircraft is leased, sold or financed, review the commercial obligations. The Directive does not specify cost allocation; parties should identify who bears the cost of retrospective compliance works and document arrangements accordingly.

12. Use qualified personnel and approvals: All work required by State of Design ADs must be carried out under the appropriate approvals (approved maintenance organisations or persons), and signed off in accordance with Australian continuing airworthiness requirements. Ensure the personnel interpreting the Netherlands ADs have appropriate engineering or maintenance approval to do so.

Implementing the above sequence will satisfy the Directive's two core obligations: determine applicability for each listed Netherlands AD, and where applicable and not previously completed, perform the actions required by that AD or a later EASA‑approved revision, within the timing windows the Directive prescribes.