AD/SF340/111 - State of Design Airworthiness Directives

The directive is built on the following core legal and operational concepts present in the source text.

• State-of-design compliance: The AD is a direct instrument to ensure Australian-registered SAAB 340 aircraft meet the State of Design (Swedish) airworthiness directives listed in Table 1. The Background states that the SADs "require once-only actions for which the compliance date has passed" and that CASA "has determined that these SADs may be applicable to some Australian aircraft" (Background).

• Applicability determination: The AD does not automatically assume every listed SAD applies to every SAAB 340. Instead it requires the responsible person to determine applicability for each individual aircraft (Requirement, item 1). This places the initial decision duty on the operator, owner, nominated maintenance provider, or certificated engineer charged with continuing airworthiness.

• Mandatory accomplishment if applicable: If the operator determines an SAD is applicable and not previously accomplished, the AD mandates performance of the actions required by that SAD or any later EASA-approved revision (Requirement, item 2). That is a concrete legal obligation to carry out the technical actions specified in the State-of-Design ADs.

• Acceptable alternatives via EASA: The directive expressly accepts Service Bulletins that have been approved by EASA as Alternative Methods of Compliance (AMOCs) for the listed SADs. The AD states that those EASA-approved service bulletins "are considered acceptable for compliance with the equivalent requirements of this Airworthiness Directive" (Requirement, final paragraph). That creates a bounded pathway for alternative compliance where EASA has approved them.

• Compliance timing linked to airworthiness certification: The AD links timing to the certificate of airworthiness status. For aircraft without a certificate the actions must be completed before issuance. For certificated aircraft the AD sets a 60-day window from the effective date of the AD before the aircraft may fly again without the listed actions if they are applicable and outstanding (Compliance paragraph).

• Limited scope to once-only actions: The AD’s background clarifies these SADs involve once-only actions and that their original compliance dates in the State-of-Design ADs have passed. The AD therefore acts as a catch-up mechanism for outstanding historical one-off modifications or inspections (Background).

• Reference to authoritative source: The AD includes a Note advising that Swedish Airworthiness Directives may be accessed via the EASA AD internet database at the URL provided (Note 1). The AD thus anchors detailed technical requirements to the Swedish/EASA AD texts rather than reproducing them in full.

These elements combine to make the AD a compliance-enforcement device focused on validating and, where necessary, completing once-only State-of-Design mandated tasks for SAAB 340 aircraft registered in Australia.

The AD explicitly applies to "SAAB 340 aircraft" (Applicability line). That captures every SAAB 340 aeroplane on the Australian registry, subject to the operator's determination of SAD applicability for each airframe. The source language places the initial compliance decision on the person responsible for the aircraft’s continuing airworthiness. The Requirement begins by instructing the reader to "Determine the applicability of the Swedish Airworthiness Directives (SAD) listed in Table 1" (Requirement, item 1). Practically, that will be the aircraft operator, owner, or an authorised maintenance organisation or certifying staff acting under their regulatory authorization.

Affected parties therefore include:

• Operators and owners of SAAB 340 aircraft registered in Australia, who must initiate and document the applicability determination and, where required, ensure the specified actions are performed.

• Maintenance organisations and certifying engineers responsible for carrying out the required inspections, replacements or modifications prescribed by the SADs or EASA-approved revisions. The AD requires the actions in the State-of-Design ADs or EASA-approved revisions; those actions will be technical tasks that fall to maintenance providers.

• CASA as the regulator, which issued the AD and whose delegate signed the instrument. The AD records that it "becomes effective on 27 August 2010" and bears the signature of Mike Higgins, Delegate of CASA (signature block), indicating CASA’s administrative responsibility for issuing and publishing the directive.

• Persons involved in certification processes: where a certificate of airworthiness has not yet been issued for an aircraft, the AD makes continued certification conditional on completion of applicable listed actions "before issue of the certificate of airworthiness" (Compliance paragraph). That affects certifying authorities and personnel who process Certificates of Airworthiness for SAAB 340s.

• Operators of aircraft produced or modified such that particular SADs are not applicable. The AD itself recognises that "due to date of aircraft manufacture or aircraft configuration and modification status, some of the SADs listed in Table 1 will not be applicable to any aircraft presently registered in Australia." That observation narrows the universe of affected aircraft but the obligation to determine applicability remains.

Who pays: the AD’s structure places the burden of execution on the operator/owner and their maintenance providers because they must determine applicability and perform the required actions. The source text does not allocate monetary compensation or funding; therefore the financial cost of inspections, part replacements, modifications or engineering work required by any applicable SADs will fall to the responsible operator or maintenance organisation.

The AD creates specific duties and identifies acceptable compliance mechanisms. The document itself does not frame rights or remedies, but the duties are explicit.

Primary duties

• Applicability determination. The operator or responsible person must "Determine the applicability of the Swedish Airworthiness Directives (SAD) listed in Table 1." That is the AD’s first, affirmative duty (Requirement, item 1). This requires a factual, airframe-by-airframe assessment against the content of each SAD in Table 1.

• Accomplish required actions. If an SAD is applicable and has not been previously accomplished, the operator must "perform the actions required by that SAD or later EASA-approved revision" (Requirement, item 2). The duty is to do the technical tasks specified by the Swedish AD or any later EASA-approved revision of that SAD. Thus, compliance is not optional for applicable and outstanding SADs.

• Use of EASA-approved AMOCs. The AD states that "Service Bulletins approved by EASA as Alternative Methods of Compliance (AMOC) to the SADs listed in Table 1 are considered acceptable for compliance." This provides a permitted alternative compliance pathway, but only where EASA has given approval.

Timing duties

• For aircraft without an issued certificate of airworthiness, completion of applicable actions is required "before issue of the certificate of airworthiness" (Compliance).

• For aircraft with an existing certificate of airworthiness, applicable actions must be completed "before further flight after 60 days from the effective date of this Directive" (Compliance).

These timing elements structure when the duties must be met, and potentially affect scheduling of maintenance and aircraft utilisation.

Rights and procedural features

• Right to use EASA-approved AMOCs. The acceptance of EASA-approved service bulletins as AMOCs is a specific procedural right to comply by an alternate method, provided EASA approval exists. The AD does not articulate any domestic CASA AMOC process; it expressly recognises EASA approvals.

• Right to rely on State-of-Design AD text. The AD directs operators to consult the Swedish ADs via the EASA database URL (Note 1). The AD therefore recognises the State-of-Design texts as the authoritative technical requirement to be applied.

What the AD does not specify

• The AD does not reproduce the substantive technical content of the Swedish ADs. It therefore delegates the technical detail of inspections, modifications or replacements to those State-of-Design documents or their EASA-approved revisions.

• The AD does not specify record-keeping, certification entries, or show formal processes for CASA acceptance after completion. The AD likewise does not set out sanctions, enforcement mechanisms, or appeal pathways within the instrument itself. Those subjects will be governed by other applicable regulatory provisions, but they are not specified in the document.

Overall, the AD imposes clear positive duties on operators to assess and, if required, execute once-only State-of-Design actions, while granting a narrow compliant path for EASA-approved alternative methods.

The AD text does not set out specific penalties, fines, or criminal sanctions for non-compliance. The instrument’s content is limited to the scope of the technical obligation, timing, and acceptance of EASA-approved AMOCs. The only enforcement-adjacent content in the document is the compliance deadlines and the effective date: "This Airworthiness Directive becomes effective on 27 August 2010" and the compliance conditions for certificated and non-certificated aircraft (Compliance paragraph).

What the AD makes explicit regarding enforcement

• Mandatory nature of compliance steps. By requiring determination of applicability and mandatory accomplishment of applicable SAD-prescribed actions, the AD establishes a regulatory obligation that must be satisfied before issuance of a certificate of airworthiness or before further flight after the 60-day window for certificated aircraft (Requirement items 1 and 2; Compliance paragraph).

• Administrative issuance. The AD is issued and signed by "Mike Higgins, Delegate of the Civil Aviation Safety Authority," dated 2 August 2010. The signature line evidences administrative issuance by CASA rather than, for example, a private circular.

What the AD does not address

• The AD does not list penalties, enforcement procedures, or administrative processes by which CASA will verify compliance. It does not give notice of the sanctions that might follow a failure to comply. The instrument therefore leaves enforcement mechanisms and consequences unstated within its own text.

Implications for practitioners

• Because the AD imposes time-bound and categorical duties, operators should treat it as a binding regulatory requirement and expect CASA to consider the AD in any regulatory oversight, certification or continuing airworthiness assessment. The AD itself, however, does not describe the enforcement route or penalty amounts.

• For clarity on enforcement powers, penalties, rectification notices or directions that might follow non-compliance, affected parties should consult CASA’s broader regulatory framework, statutory instruments and enforcement policy. Those materials are outside this AD’s text and are not provided within the source document.

In short, the AD sets the mandatory technical duties and timing but does not articulate the enforcement mechanisms or penalties within its own text.

The AD positions itself as a domestic mechanism to ensure compliance with foreign State-of-Design airworthiness directives. The instrument interacts with other regulatory instruments and technical sources as follows, based on the source text.

Relationship to State-of-Design (Swedish) ADs and EASA

• The AD explicitly references Swedish Airworthiness Directives (SADs) listed in Table 1 and requires compliance with those SADs or later EASA-approved revisions (Requirement, item 2). This links Australian regulatory requirements to the technical obligations issued by the State of Design.

• The AD accepts Service Bulletins that are "approved by EASA as Alternative Methods of Compliance (AMOC)" for the listed SADs as acceptable for compliance with the AD (Requirement, final paragraph). That creates a legal interface with EASA's approval processes for alternative compliance.

Interaction with Certification of Airworthiness

• The compliance timing is tied to the certificate of airworthiness regime. The AD requires completion of applicable actions "before issue of the certificate of airworthiness" where a certificate has not been issued, and "before further flight after 60 days from the effective date of this Directive" where a certificate has been issued (Compliance paragraph). Thus the AD operates as a condition precedent for the issuance of a CoA in the case of un-certificated aircraft and as a continuing airworthiness obligation for certificated aircraft.

Delegation and administrative process

• The instrument is issued by CASA and signed by a CASA delegate. It thus forms part of CASA’s administrative regulatory output. The AD itself does not specify how CASA will integrate compliance evidence into certification files or continuing airworthiness records.

What the AD does not do

• The AD does not reproduce the foreign SADs in full; instead it requires reference to and compliance with those SADs. It therefore relies on cooperation between the operator and the State-of-Design/EASA sources for technical detail.

• The AD does not specify domestic AMOC procedures or provide domestic technical acceptability criteria beyond acceptance of EASA AMOCs. It does not mention any interaction with other Australian aviation instruments, statutory provisions, or record-keeping obligations. Those interactions are not provided in the source text.

Practical implication for legal and compliance teams

• Operators must treat the Swedish ADs listed in Table 1 and any later EASA-approved revisions as the substantive technical standards to be applied in compliance with this CASA AD. They must therefore consult the EASA AD database or the Swedish ADs themselves for the step-by-step technical requirements referenced by this AD.

• Where an EASA-approved service bulletin exists as an AMOC for a listed SAD, the AD expressly accepts it as satisfying the AD requirement. That channels operators toward the EASA approval process where an alternative compliance method is desired.

The AD thus serves as a domestic enforcement mechanism that imports State-of-Design technical obligations and recognises EASA-approved alternatives, while leaving broader enforcement and administrative interaction with other Australian regulatory instruments unstated.

The source document contains a single issuance block and does not list any subsequent amendments, revocations, or supersessions within its text. The identification headers present are:

• AD/SF340/111, State of Design Airworthiness Directives, Issue 16/2010 (document title block).

• The AD states at multiple points that it "becomes effective on 27 August 2010" and bears the signature and date "2 August 2010" under the name Mike Higgins, Delegate of CASA. The Compliance paragraph repeats the effective date and describes the timeframes tied to certificate of airworthiness status (Compliance paragraph).

No later amendments are printed in the document, and no prior versions or revision history are included. The instrument contains a table of State-of-Design ADs (Table 1) which itself lists SAD issue dates ranging from 1984 to 1990 for particular technical items; those SAD issue dates are part of the content imported by the AD but are not domestic amendments to the CASA AD.

Consequence for users seeking amendment information

• The document does not include a domestic amendment log. Users requiring updated status, rescissions, or later CASA actions will need to consult CASA’s public AD register or subsequent CASA notices external to this text.

• For the substantive technical texts that this AD imports by reference, the AD allows compliance with "later EASA-approved revision[s]" of the listed SADs. That implies that the domestic AD contemplates and accommodates later technical revisions made under EASA auspices. It does not, however, record any such later revisions or explicitly incorporate them into the domestic AD text.

In short, the instrument as presented is a single-issue AD effective 27 August 2010 with no appended amendment history in the printed source. The AD does permit compliance to be met by later EASA-approved revisions of the State-of-Design ADs, but it does not itself list or track such revisions.

The source document contains no litigation history, references to judicial or administrative appeals, nor descriptions of any disputes arising from AD/SF340/111. There are no case names, tribunal decisions, or references to enforcement actions in the AD text.

What the AD does show relevant to potential dispute pathways

• The AD is an administrative regulatory instrument issued by CASA and signed by a delegate. Any legal challenges or enforcement proceedings that might arise from non-compliance would therefore be matters outside the AD text and would rely on the wider legislative and regulatory framework governing CASA’s powers and aviation safety enforcement in Australia. Those frameworks and any dispute records are not included in the source document.

• The AD’s content , requiring operators to determine applicability and to perform specified State-of-Design actions or EASA-approved AMOCs , is prescriptive. Absent litigation history in the AD itself, legal professionals should look to CASA’s enforcement policies, civil penalty provisions and administrative law precedents for context if litigation or contested enforcement is an issue. Those sources are not contained in this instrument.

For research or litigation preparation, practitioners must therefore obtain external records from CASA, court dockets, and administrative tribunals to identify any matters that may have arisen from this AD after its effective date.

The AD’s concise wording embeds several practical pitfalls and points that merit careful attention, all grounded in the source text.

• Applicability is an active duty. The AD does not assume applicability across the fleet. The operator must "Determine the applicability" of each SAD listed in Table 1 (Requirement, item 1). Failure to carry out and document an applicability assessment could leave an operator non-compliant even if no substantive technical work is required.

• The AD covers once-only items with past due dates. CASA states that the SADs "require once-only actions for which the compliance date has passed" (Background). Because the original State-of-Design compliance windows are already past, there is a higher immediate compliance pressure on aircraft where the SADs have not yet been done. Operators must therefore have maintenance and engineering resources ready to execute these one-off tasks promptly where applicable.

• Timing hinge on certificate of airworthiness status. The compliance timing differs depending on whether a certificate of airworthiness has been issued. For non-certificated aircraft the requirement is "before issue of the certificate of airworthiness"; for certificated aircraft the deadline is "before further flight after 60 days from the effective date of this Directive" (Compliance). Operators bringing previously un-certificated SAAB 340s into service must complete the applicable tasks before certification, which could delay entry into service.

• EASA-approved AMOCs only. The AD allows service bulletins approved by EASA as AMOCs to satisfy the AD. The AD does not mention CASA approvals of alternative methods. Therefore, operators seeking to rely on an alternative method of compliance must ensure the alternative is EASA-approved, or else use the State-of-Design ADs; domestically approved alternatives are not recognised in the AD text.

• Technical detail resides in external documents. The AD does not quote the substantive technical steps from the Swedish ADs. The operator must consult the actual SADs via the EASA database to know the exact inspections, replacements or modifications required (Note 1). Misreading the AD as self-contained will lead to omissions.

• Variation in applicability by manufacture/configuration. The AD expressly recognises that "due to date of aircraft manufacture or aircraft configuration and modification status, some of the SADs listed in Table 1 will not be applicable to any aircraft presently registered in Australia" (Background). Operators must therefore match SAD scope and applicability criteria to their aircraft serial numbers, configuration status and modification history.

• Table 1 content requires careful parsing. Table 1 lists seven SADs by identifier, issue date and title. These are the State-of-Design directives to be considered. The Table entries are:

  • SAD 1-038, Issue Date 1990-06-29, Title: "Yaw oscillations".
  • SAD 1-016, Issue Date 1987-06-18, Title: "Inspection of cabin fluorescent lighting system".
  • SAD 1-013, Issue Date 1986-01-31, Title: "Cabin fluorescent lighting system".
  • SAD 1-009, Issue Date 1985-08-15, Title: "Engine controls - replacement and sealing".
  • SAD 1-002, Issue Date 1984-09-27, Title: "Engine and engine-performance monitoring".
  • SAD 1-001, Issue Date 1984-09-12, Title: "Inspection and replacement of certain parts".
  • The Table also contains a note directing operators to the EASA AD website for the SAD texts (Table 1 and Note 1).

  Some of the SAD titles are terse and require consultation of the full SAD text to understand precise part numbers, inspection intervals (if any), or detailed steps.

• No domestic record-keeping or proof procedure specified. The AD does not say how operators should certify completion domestically, or where to lodge evidence of compliance. Practitioners should not assume an explicit CASA process exists based on this AD alone.

• Possible confusion over earlier compliance. The AD requires that, if an SAD "has not been previously accomplished" then perform the action. Operators need to have traceable maintenance records to demonstrate prior accomplishment; absence of clear evidence may create compliance uncertainty.

• Effective date vs signature date. The AD bears a signature dated 2 August 2010 while stating that it "becomes effective on 27 August 2010" (Background and Compliance). This creates a 60-day window for certificated aircraft; operators must pay attention to the later effective date for their scheduling.

These points are all derivable directly from the source text. They underline the need for careful technical review, strict applicability assessment, and close coordination between operators and maintenance organisations.

The AD’s own Requirement and Compliance paragraphs set a compact, legally prescriptive pathway. Below is a practical step-by-step compliance checklist strictly aligned to the AD language.

1. Identify affected airframes

   • Confirm which SAAB 340 aircraft on your registry you operate, own, or maintain. The AD’s Applicability line reads "SAAB 340 aircraft." Start with a serial-numbered fleet list and configuration records.

2. Obtain the State-of-Design SAD texts

   • Use the EASA AD database URL referenced in the AD (Note 1) to obtain the full Swedish Airworthiness Directives listed in Table 1. The AD does not reproduce the technical requirements, so the full SAD texts are the authoritative source for required actions.

3. Determine applicability for each SAD on each aircraft

   • Perform the step the AD mandates: "Determine the applicability of the Swedish Airworthiness Directives (SAD) listed in Table 1" (Requirement, item 1). For each SAD, check applicability criteria such as serial number ranges, serial-numbered components, installation status, manufacture/modification dates and configuration differences.

4. Establish whether the SAD action has been previously accomplished

   • For any SAD found to be applicable, examine maintenance records to see if the required actions were previously performed. The AD requires action only when an SAD "is applicable and has not been previously accomplished" (Requirement, item 2).

5. If the SAD is applicable and outstanding, perform the required actions

   • Execute the inspections, part replacements, sealing actions, monitoring installations, or other prescribed tasks as set out in the Swedish AD text or a later EASA-approved revision of that specific SAD. The AD requires performing "the actions required by that SAD or later EASA-approved revision" (Requirement, item 2).

6. Consider EASA-approved AMOCs where available

   • If there exists a Service Bulletin that has been approved by EASA as an Alternative Method of Compliance for a listed SAD, that AMOC is "considered acceptable for compliance" with this AD (Requirement, final paragraph). If relying on an AMOC, ensure it is indeed EASA-approved and apply it as specified.

7. Meet the timing requirements tied to certificate status

   • For aircraft without an issued certificate of airworthiness: ensure that any applicable listed actions are completed "before issue of the certificate of airworthiness" (Compliance).
   • For aircraft with an issued certificate of airworthiness: ensure that any applicable actions are performed "before further flight after 60 days from the effective date of this Directive." The AD is effective 27 August 2010, so the 60-day grace period applies accordingly (Compliance).

8. Maintain documentary evidence of the applicability determination and the work performed

   • While the AD does not specify record-keeping procedures, the AD’s compliance depends on showing whether actions have been previously accomplished or have now been carried out. Maintain maintenance entries, engineer sign-offs, and copies of the specific Swedish AD passages or EASA-approved AMOC documents used.

9. Coordinate with your certifying staff and maintenance organisation

   • Because the AD can affect the issue of a certificate of airworthiness and the permissibility of further flight, ensure that certifying authorities, accountable managers and maintenance providers are aligned on applicability conclusions and scheduled works.

10. Monitor for later EASA revisions

    • The AD allows compliance with "later EASA-approved revision[s]" of the listed SADs. Check for any EASA-sanctioned revisions of the relevant Swedish ADs that may alter the required scope of work.

11. For uncertain applicability or technical scope, escalate to technical authority

    • Where applicability is ambiguous , for example due to historic modifications, undocumented configuration differences or unclear serial-number applicability , obtain a technical determination from an appropriate certifying engineer or seek clarification from CASA or the type certificate holder. The AD itself places the initial duty of determination on the operator, but recognises there will be cases where technical judgement is required.

12. Use conservative operational decisions pending completion

    • If an SAD is found to be applicable and remains outstanding, avoid further flight beyond the compliance deadline set out in the AD. For certificated aircraft, the AD requires completion "before further flight after 60 days from the effective date" (Compliance). Plan maintenance slots and logistic arrangements accordingly.

These steps follow the precise wording of the AD: determine applicability (Requirement, item 1), perform required actions if applicable and outstanding (Requirement, item 2), accept EASA-approved AMOCs (Requirement, final paragraph), and respect the compliance timings connected to the certificate of airworthiness (Compliance). The Table 1 SAD identifiers, issue dates and titles should be used as the index to the specific Swedish ADs in the EASA database.

For convenience, Table 1 entries are reproduced here exactly as they appear in the AD to guide the retrieval of the SAD texts:

• SAD 1-038, Issue Date 1990-06-29, Title: "Yaw oscillations".
• SAD 1-016, Issue Date 1987-06-18, Title: "Inspection of cabin fluorescent lighting system".
• SAD 1-013, Issue Date 1986-01-31, Title: "Cabin fluorescent lighting system".
• SAD 1-009, Issue Date 1985-08-15, Title: "Engine controls - replacement and sealing".
• SAD 1-002, Issue Date 1984-09-27, Title: "Engine and engine-performance monitoring".
• SAD 1-001, Issue Date 1984-09-12, Title: "Inspection and replacement of certain parts".

Keep in mind the AD’s own observation that some SADs "will not be applicable to any aircraft presently registered in Australia" due to manufacture date or configuration (Background). That is a reminder to document negative determinations as well as positive compliance outcomes. The AD is signed by a CASA delegate and becomes effective 27 August 2010 (signature block and Compliance).