AD/SF340/28 - Passenger Door Handle

The AD rests on a small set of interlocking concepts that determine its practical effect and scope.

• Applicability by serial number. The directive applies only to SF340A aircraft numbered SF340A‑004 through SF340A‑159 and SF340B aircraft numbered 340B‑160 through 340B‑259 (Applicability). This creates a targeted covered population rather than a type‑wide mandate for all SF340s.

• Mandatory action by reference. The AD does not set out specific maintenance works or inspection steps itself; it imposes a mandatory obligation to carry out "action in accordance with LFV AD 1‑048" (Requirement). The AD therefore functions as an incorporative instrument, making an external directive binding on the named Australian aircraft.

• Manufacturer paperwork reference. The AD notes that SAAB‑Scania SB 340‑52‑014 "refers", indicating that the manufacturer service bulletin is part of the technical chain of documents that support LFV AD 1‑048 and the required remedial measures (Note).

• Revised effective date for Australian registered aircraft. The Compliance clause sets a revised effective date of 11 July 1991 for Australian registered aircraft (Compliance). The Background explains this adjustment as a response to the Swedish CAA's required effective date and the date of receipt of the directive.

• Safety hazard focus. The Background links the AD to occurrences of cracked spring pins on passenger door handles that can render door operation impossible, which in an evacuation could produce a "critical condition" (Background). The AD thus targets a discrete component failure mode (spring pins in passenger door handles) with direct safety implications for evacuation.

• Cross‑jurisdictional adoption. The AD explicitly imports the LFV (Swedish) airworthiness directive 1‑048 into Australian regulatory effect, and aligns the Australian effective date to the circumstances described by the issuing authority (Background; Compliance). This is a mechanism by which national authorities adopt foreign mandatory corrective actions for aircraft registered domestically.

Taken together, these concepts show that the AD operates as a narrowly framed, document‑referencing mandatory correction aimed at a specific hardware fault and targeted aircraft, with the Australian application linked to an externally issued directive and a manufacturer service bulletin.

The AD directly affects operators and owners of the specified SAAB SF340 airframes listed in the Applicability clause: SF340A serial numbers SF340A‑004 through SF340A‑159 and SF340B serial numbers 340B‑160 through ‑259. Those Australian registered aircraft within those serial‑number ranges are the covered population for whom the AD imposes a compliance obligation, with an effective date of 11 July 1991 (Applicability; Compliance).

Secondary actors affected include maintenance organisations that provide inspections, repairs and modifications for the SF340 series for Australian operators. Because the AD imports the requirements of LFV AD 1‑048 and references SAAB‑Scania SB 340‑52‑014 (Requirement; Note), maintenance providers will need access to those documents to determine the exact technical steps required and to perform them in a manner that satisfies the AD. They will also need to align their maintenance scheduling and parts procurement with the AD's timelines and with operators' operational needs.

Regulatory decision‑makers and inspectors within the Civil Aviation Safety Authority (or equivalent enforcing body) are affected in that they are responsible for ensuring the AD is applied to the named Australian registered aircraft and for verifying compliance with the imported directive as the declared Australian effective date requires (Compliance). The Background indicates interaction with the Swedish CAA, and thus foreign regulatory authorities and the manufacturer may be engaged in information exchange and technical support.

Indirectly, passengers and third parties have a safety interest since the AD is premised on door handle spring pins that, if cracked, "can make door operation impossible" and thereby "could lead to a critical condition in an emergency evacuation" (Background). Airline operations and scheduling may be affected where aircraft are grounded or taken out of service to effect the actions required by LFV AD 1‑048, although the AD text does not specify the operational tolerances or allowable deferrals , it defers those particulars to the incorporated LFV AD.

Financially, the immediate economic burden lies with the operators and possibly their maintenance contractors, who must implement the actions called for in LFV AD 1‑048 and any instructions in SAAB‑Scania SB 340‑52‑014. The source does not allocate costs to any third party or the regulator; the text creates an enforceable technical duty for those who own and operate the affected aircraft under Australian registration.

The AD creates a singular, focused duty: Australian operators of the specified SF340 serial numbers must carry out "action in accordance with LFV AD 1‑048" (Requirement). The AD itself does not enumerate step‑by‑step obligations, tolerances or time‑in‑service limits; instead, it makes compliance with the foreign directive mandatory for the named Australian registered aeroplanes. The Compliance clause fixes the operative date for that duty as 11 July 1991 for Australian registered aircraft (Compliance). The AD therefore transforms an externally prescribed set of corrective or inspection measures into a domestic legal duty by reference.

Rights and entitlements are not explicitly set out within the AD. The instrument does not specify a right of appeal, an administrative review mechanism, or a process for seeking an alternative means of compliance within the text provided. The AD does not itself provide derogations, alternative procedures or extension regimes; any such mechanisms, if available, would need to be sought in the documents it incorporates (LFV AD 1‑048) or via the general regulatory framework of the Civil Aviation Safety Authority. The AD does not record any temporary relief or operational exemptions for aircraft out of compliance; it simply states the required action and the Australian effective date.

Because the AD refers to SAAB‑Scania SB 340‑52‑014, operators and maintenance organisations have the duty to obtain and apply the manufacturer material insofar as it is relevant to the LFV AD requirements (Note). The AD's short Background characterises the safety risk: cracked spring pins that "can make door operation impossible," which in an evacuation could be critical (Background). That safety description identifies the rationale that underpins the duty , to mitigate the door‑operation failure mode.

Practically, the duty entails that the operator must: (a) obtain the LFV AD 1‑048; (b) procure and review SAAB‑Scania SB 340‑52‑014 when it is relevant to the remedial action; and (c) implement the specified actions by the Australian revised effective date. The operator's rights to be informed of what is required are satisfied only to the extent that the external LFV AD and SAAB SB are accessible; the AD does not reproduce the contents of those documents.

The AD does not explicitly set out record‑keeping obligations, but because it imposes a mandatory corrective action, operators can expect to be required, under the broader civil aviation regulatory system, to retain evidence of compliance. The AD text itself, however, does not specify the format, retention period, or auditing process for such records.

The AD text supplied does not specify statutory penalties, infringement notices, or civil or criminal sanctions for non‑compliance. The document is presented within the "SCHEDULE OF AIRWORTHINESS DIRECTIVES" under the Commonwealth of Australia Civil Aviation Regulations context (header), and it mandates compliance with LFV AD 1‑048 for the named aircraft with a revised Australian effective date (Requirement; Compliance). The AD itself functions as a regulatory instrument that imposes a mandatory duty; enforcement mechanisms and penalties, if any, are not articulated in the text provided.

Because the AD is an entry in the civil aviation regulatory schedule and imports a foreign directive as mandatory action, non‑compliance would, in the ordinary course, expose the operator to regulatory enforcement measures available to the enforcing authority, but the AD text does not identify those measures or their scope. The Background and other clauses make no reference to enforcement processes, inspected evidence, or administrative proceedings. The AD therefore creates the compliance obligation but leaves the enforcement rulebook and penalties unspecified in this text.

The Requirement clause makes the foreign directive binding; the Compliance clause fixes the date by which Australian operators must meet that binding obligation. Enforcement discretion, inspection, and verification procedures would typically follow the enforcing authority's standard practices, but the AD does not describe them. The Note indicating SAAB‑Scania SB 340‑52‑014 is referenced for technical content does not extend to enforcement language.

For practitioners advising affected parties, it is important to note that the AD imposes a duty without detailing enforcement within its own text. Any questions about penalties, acceptable records of compliance, or processes for seeking relief or alternative compliance methods would need to be resolved by reference to the broader Civil Aviation Regulations and guidance issued by the enforcing authority, or possibly by consulting LFV AD 1‑048 to see whether it contains compliance‑time frames or enforcement guidance that the importing instrument makes binding.

The AD is an instance of cross‑document and cross‑jurisdictional incorporation. It does not operate in isolation; it explicitly imports LFV AD 1‑048 (a directive issued by the Swedish CAA, LFV) and references SAAB‑Scania Service Bulletin SB 340‑52‑014 (Requirement; Note). By making LFV AD 1‑048 mandatory for the specified Australian registered SF340 aircraft, the AD aligns domestic regulatory obligations with a foreign airworthiness directive and a manufacturer service bulletin. This creates a legal dependency on external documents for the technical content of the mandatory measures.

The Compliance clause establishes a revised Australian effective date of 11 July 1991 for Australian registered aircraft (Compliance), which interacts with the timing and sequencing of obligations under the foreign directive. The Background explains that the effective date required by the Swedish CAA was extended due to the receipt date of the directive, and the Australian AD mirrors that accommodation by setting the revised date. This shows a direct interaction between administrative timing decisions made by a foreign authority and the domestic schedule of obligations.

The AD is embedded in the Civil Aviation Regulations framework (header), and thus operates within that statute‑based regime even though it does not itself reproduce the legislative enforcement architecture. The AD's importation of LFV AD 1‑048 raises potential questions about legal interpretation: where the Australian AD is silent, operators must consult the incorporated LFV AD and related manufacturer documents for technical detail. Where those documents contain directions or compliance timeframes, they form part of the domestic regulatory obligation as incorporated by the AD.

The AD does not refer to other Australian laws, such as general administrative law remedies, accreditation requirements for maintenance organisations, or occupational health and safety standards; nor does it claim precedence over other regulatory instruments. The AD's scope is limited to importing a specific corrective action for a specific set of serial‑numbered aeroplanes, with a stated effective date. Interaction with other regulatory requirements , for example, maintenance record‑keeping obligations, operational limitations pending rectification, or type‑certificate related constraints , is not described in the AD and would need to be understood through the wider regulatory framework rather than from the AD text itself.

Finally, the AD’s reference to SAAB‑Scania SB 340‑52‑014 means manufacturers' service bulletins operate as part of the technical regime. Operators should treat that bulletin as an operative document for performing the required actions, but the AD does not specify whether any inconsistencies between LFV AD 1‑048 and the SB are to be resolved in favour of one document; such resolution mechanisms are not present in the AD and would arise from the content of the incorporated documents or the broader regulatory scheme.

The AD record includes a single, explicit amendment‑type detail: the Compliance clause sets a "revised effective date of 11 July 1991 for Australian registered aircraft" (Compliance). The Background explains why that revision occurred: the Swedish CAA's effective date requirement was extended due to the directive's receipt date (Background). No other amendments, rescissions, supersessions or continued applicability notes are contained in the AD text provided.

There is no chronological series of amending entries listed in the source. The AD does not include a formal history table, versioning identifiers beyond the AD number (AD/SF340/28), or a record of later revisions. The only temporal adjustment documented in the provided text is the alignment of the Australian effective date to 11 July 1991, which appears to respond to receipt timing issues raised by the Swedish CAA.

The AD references external documents (LFV AD 1‑048 and SAAB‑Scania SB 340‑52‑014) that may themselves have amendment histories, but the AD does not summarise or reproduce those histories. The AD therefore functions as a snapshot incorporation: it binds the actions required by LFV AD 1‑048 as they stood at the relevant point in time and fixes the Australian effective date accordingly. Any later amendments to LFV AD 1‑048 or to SAAB‑Scania SB 340‑52‑014 are not reflected in this AD text and would require either a new AD or an explicit amendment to be domestically binding, unless the broader regulatory regime provides for automatic adoption of subsequent foreign amendments , which this AD does not state.

Practitioners should therefore treat this document as recording a single adoption event with a specific effective date and should not assume the AD captures subsequent revisions of the referenced LFV or SAAB documents without separate domestic action.

The provided AD text contains no litigation history. It does not cite, summarise, or reference any court decisions, enforcement actions, administrative appeals, or disputes related to AD/SF340/28 or to the underlying LFV AD 1‑048 or SAAB‑Scania SB 340‑52‑014. The document is a regulatory directive entry and does not include judicial or tribunal outcomes.

Because the AD does not record any litigation, practitioners seeking case law on the validity, enforcement, scope, or interpretation of this particular AD will need to search external records and repositories of administrative and court decisions. The AD itself offers no indication of contested points, judicial questions, or precedential materials arising from enforcement or compliance disputes.

The absence of litigation history in the AD text does not imply there has been none. It simply indicates that the schedule entry does not purport to summarise such material. Any litigation that may have occurred concerning LFV AD 1‑048, SAAB‑Scania SB 340‑52‑014, or this domestic adoption is beyond the scope of the provided document and would need to be identified through independent legal research in judicial and administrative archives.

The AD contains several features that create practical pitfalls for operators, maintenance providers and advisers. These are matters of form and mechanism embedded in the AD text rather than hidden substantive requirements.

• No technical steps reproduced. The AD does not reproduce the technical inspection or repair actions; it mandates "action in accordance with LFV AD 1‑048" (Requirement). The required steps, compliance timeframes and permissible alternatives are therefore contained in an external document. Operators who assume the AD itself contains the work‑scope risk failing to perform the exact procedures LFV AD 1‑048 mandates. The AD's Note that SAAB‑Scania SB 340‑52‑014 "refers" reinforces that the technical content is scattered across multiple documents (Requirement; Note).

• Document acquisition and currency risk. Because compliance depends on LFV AD 1‑048 and SAAB‑Scania SB 340‑52‑014, the operator must obtain those documents and ensure they are the correct issue/effectively‑incorporated versions. The AD does not state the specific edition or revision of the LFV AD or the service bulletin that is required, which can lead to ambiguity unless the imported documents themselves fix their revision status. Failure to use the correct revision that LFV intended could expose an operator to enforcement risk, but the AD does not clarify this point.

• Narrow serial‑number scope. The AD applies only to discrete serial ranges (Applicability). Operators of similarly configured SF340s outside those serial numbers may be tempted to ignore the directive, but differences in build or service history might mean that safety‑relevant hardware exists on other airframes. Conversely, owners within the serial ranges may incorrectly think that only a subset of their fleet is affected without checking all aircraft records.

• Timing and operational impact. The Compliance clause sets a revised effective date (11 July 1991) for Australian registered aircraft (Compliance), but the AD does not specify permissible ferry flights, deferral allowances, or grounding criteria. If LFV AD 1‑048 contains strict grounding requirements, operators will need to balance operational disruption against safety obligations. The AD's failure to spell out operational mitigations or acceptable temporary measures is a practical gap.

• Reference to manufacturer bulletin without instructive hierarchy. The AD notes SAAB‑Scania SB 340‑52‑014 "refers" (Note). It does not say how to treat differences between the LFV AD and the SB if any exist. Operators must therefore examine both documents and may need to resolve any inconsistencies with the authority. That creates a potential compliance trap if an operator follows one document but not the other.

• Enforcement and record uncertainty. The AD does not articulate penalty provisions, enforcement procedures, or record‑keeping requirements (Penalties and enforcement). Operators may be uncertain what evidence will be acceptable to demonstrate compliance. This is a practical "gotcha" because inability to produce accepted records can cause enforcement outcomes even where substantive work was performed.

• Cross‑jurisdictional timing. The Background indicates the Swedish CAA extended the effective date due to receipt timing (Background). That historical detail suggests timing sensitivity in cross‑jurisdictional adoptions. Australian operators should not assume imported directives instantly take effect worldwide; domestic effective dates may reflect communication and receipt realities.

These features mean that compliance requires more than undertaking ad hoc inspections: it requires document control, version verification, careful scheduling to meet effective dates, and possibly dialogue with the regulator when technical ambiguities arise.

The AD makes compliance straightforward in principle: carry out the actions required by LFV AD 1‑048 and follow the relevant manufacturer material, timed to the Australian revised effective date of 11 July 1991. In practical steps, the operator should at minimum do the following, noting that these steps are derived from the AD's text and that the AD does not itself specify the technical work:

1. Identify affected aircraft. Verify whether each Australian registered SF340 in the operator's fleet falls within the serial‑number ranges listed: SF340A‑004 through SF340A‑159, and 340B‑160 through 340B‑259 (Applicability). Do not assume type designation alone is sufficient.

2. Obtain LFV AD 1‑048. Acquire the full text of LFV AD 1‑048 referred to in the Requirement. The AD makes compliance conditional on "action in accordance with LFV AD 1‑048" (Requirement). The specific inspections, replacements, or modifications required will be in that document.

3. Obtain SAAB‑Scania SB 340‑52‑014. Secure the manufacturer Service Bulletin referenced by the Note, since it "refers" and is likely to contain the technical procedures, parts information and illustrations required to carry out actions in the LFV AD (Note). Ensure you have the correct revision or issue as it relates to LFV AD 1‑048.

4. Review and plan. Cross‑check the LFV AD and the SAAB service bulletin for required actions, parts lists, compliance times, and any operational limitations. Confirm whether the LFV AD mandates immediate grounding, inspection intervals, or replacement at next maintenance, and plan for maintenance bookings accordingly.

5. Schedule and perform work. Engage a suitably certificated maintenance organisation to perform the actions demanded by LFV AD 1‑048, using SAAB‑Scania SB 340‑52‑014 as technical guidance where appropriate. Ensure work is executed to the standard required by the incorporated documents.

6. Meet the Australian effective date. Ensure the required actions are completed on or before the revised Australian effective date, 11 July 1991, to the extent that the LFV AD or local regulator requires compliance by that date (Compliance). If work cannot practically be completed by that date, contact the enforcing authority for guidance on interim measures or relief; the AD itself does not provide deferral mechanisms.

7. Document compliance. Although the AD does not specify record‑keeping requirements, retain clear maintenance records that demonstrate the actions required by LFV AD 1‑048 were completed. Include details of parts used, work orders, signatories, and dates, and retain copies of the LFV AD and the SB used. These records will be necessary to demonstrate compliance if inspected.

8. Verify and report. If LFV AD 1‑048 or the SAAB SB requires operators to report findings, compliance status, or part failures to the issuing authority or the manufacturer, follow those reporting instructions. The AD refers to those documents as the compliance source, so any reporting requirements they contain will be binding as part of the AD.

9. Monitor for amendments. Because the AD incorporates external documents, watch for any subsequent revisions to LFV AD 1‑048 or SAAB‑Scania SB 340‑52‑014 and for any domestic amendments to this AD. The AD as provided does not automatically capture later revisions.

10. Seek formal guidance if needed. If there are ambiguities between LFV AD 1‑048 and SAAB‑Scania SB 340‑52‑014, or uncertainty about compliance timing or acceptable alternatives, contact the enforcing authority for clarification. The AD itself does not resolve such conflicts.

These steps reflect the mechanism the AD sets out: compliance by following LFV AD 1‑048, using SAAB‑Scania SB 340‑52‑014 as supporting material, and meeting the Australian effective date (Requirement; Note; Compliance). The AD does not itself prescribe allowable deviations, record formats, or enforcement remedies, so operators seeking certainty should secure the incorporated documents and, where necessary, regulatory confirmation.