AD/SF340/105 - Landing Gear - Emergency Extension Valve

The directive rests on a few tightly defined technical and regulatory concepts, all drawn directly from the text.

• Applicability: The AD applies to SAAB AB, Saab Aerosystems SAAB SF340A and SF340B aeroplanes (Applicability). This confines the scope to a single aircraft family and its variants named.

• Prescriptive maintenance action: The core action is a "functional check of the landing gear emergency extension valve" carried out in strict accordance with specified SAAB technical publications: Service Bulletin SB 340-32-136 (or later NAA approved revision) or SAAB 340 MRB Report, Section F, Revision 6, task number 323106.2 (Requirement). The AD does not provide an alternative procedure outside those documents; it accepts later NAA-approved revisions to the SB as an allowed variant.

• Restorative duty: If discrepancies are found during the functional check, the AD requires that the valve functionality be "restored" (Requirement). The text does not detail acceptable repair standards or parts, but it points to the AMM, Chapter 32, for a full system description (Requirement).

• Timing model change: The AD requires an inspection cadence anchored to calendar time rather than to flight hours. The compliance schedule prescribes an initial check within six months of the AD’s effective date and thereafter "at intervals not to exceed 2 years" (Compliance). The Background explains SAAB’s change from an earlier MRB task interval expressed as 5,000 flight hours to a two-year calendar interval on the grounds that valve lubrication performance depends on calendar time since last operation.

• Procedure modification: SAAB revised the functional check to include cycling the emergency release handle five times; the AD directs compliance with the SB or MRB task which, per the Background, reflects that revision (Background). Consequently, the procedural content of the check now includes operator action (handle cycling) rather than passive inspection alone.

• Cross-reference to other authority: The AD notes that EASA AD 2008-0054 dated 5 March 2008 "refers" (Requirement note). That indicates parallel regulatory attention and that operators, maintainers or regulators may consult the EASA AD for additional context.

• Legal form and effective date: The AD has an explicit effective date: 8 May 2008 (Compliance). It is issued by CASA through a delegate signature and is titled AD/SF340/105, which denotes its identity for regulatory compliance and record-keeping.

These concepts define the AD’s mechanics: specific aircraft, a specified maintenance action drawn from manufacturer and MRB documents, a calendar-based interval, a requirement to restore function before flight if discrepancies are found, and cross-reference to EASA material. The AD shifts maintenance attention from flight hours to calendar time because the root cause identified,internal lubrication loss,is sensitive to elapsed time, not solely to usage metrics (Background).

The AD explicitly affects the operator, owner and maintenance organisations responsible for SAAB SF340A and SF340B aeroplanes as stated under Applicability. The text names SAAB AB and Saab Aerosystems in the Applicability field, but the practical burden falls on the aircraft operators and maintenance organisations that perform recurring inspections and corrective maintenance on those aeroplanes.

Specific affected parties and their roles, as implied or stated by the AD, are:

• Aircraft operators/owners: They must ensure that the functional check is scheduled and performed within the specified compliance window,within six months of the effective date and then every two years thereafter (Compliance, item 1). Where a discrepancy is found, the operator must ensure the aeroplane is not returned to service until functionality has been restored (Compliance, item 2).

• Maintenance providers/engineers: The AD mandates the method of inspection be “in accordance with” SAAB SB 340-32-136 or the MRB task 323106.2, or later NAA-approved revision of the SB (Requirement). Therefore maintenance organisations must possess, understand and apply the current SB or MRB task procedures and refer to AMM Chapter 32 for the full system description. They carry the on-the-ground tasking: cycling the emergency release handle as specified, identifying seized valves or other discrepancies, and effecting repairs that restore functionality.

• Certification/airworthiness authorities and their delegates: The AD is issued by a CASA delegate (signature block). The presence of the AD itself signals a regulatory requirement that CASA expects operators and maintenance organisations to follow. The AD also notes a related EASA AD (Requirement note), which indicates that national and regional authorities share oversight interest.

• Aircraft dispatch/planning functions: The compliance schedule,initial action within six months and recurring every two years,requires planning to accommodate checks within scheduled maintenance or line-down time. Where a discrepancy requires restoration before further flight, dispatch functions may face immediate grounding until the valve is restored.

• Parts suppliers and overhaul organisations: Although the AD does not list replacement parts, any restoration to functionality could involve parts or component overhaul. Organisations that supply spares or overhaul valve components will be implicated operationally.

The AD does not articulate exemptions, approvals for alternative methods of compliance within its text except in the sense that a "later NAA approved revision" of the SAAB SB is permitted (Requirement). The AD does not specify who funds the checks or repairs; operational cost consequences fall to the operator or their contracted maintenance organisation by operational practice (the AD imposes the actionable duty but not the funding mechanism in the text).

The text sets out specific duties and a narrow set of permitted choices for compliance. These are explicit in the Requirement and Compliance fields.

Duties imposed by the AD

• Perform a functional check of the landing gear emergency extension valve for each applicable aeroplane in accordance with either: SAAB Service Bulletin SB 340-32-136 (or a later NAA approved revision) or SAAB 340 MRB Report, Section F, Revision 6, task number 323106.2 (Requirement). The AD thus imposes a duty to follow one of the listed, normative technical procedures.

• Restore functionality where discrepancies are found during any functional check described in Requirement 1 (Requirement). That restoration must be effected "before further flight" as specified in Compliance item 2.

• Comply with the timing: carry out the initial check within six months after the AD’s effective date and repeat at intervals not exceeding two years (Compliance, item 1). The initial six-month window and subsequent two-year maxima are mandatory scheduling rules in the AD.

Rights and permitted choices in the AD

• Choice of prescriptive document: The AD allows operators to choose between the SAAB Service Bulletin SB 340-32-136 (or later NAA approved revision) or the SAAB 340 MRB Report Section F Rev 6 task 323106.2 as the procedural authority for the functional check (Requirement). The allowance of a "later NAA approved revision" for the SB creates a limited right to adopt updates approved by the relevant national aviation authority.

• Reference to AMM for system description: The AD directs users to the SAAB 340 AMM Chapter 32 for a full system description (Requirement). That is an informational right to consult the AMM; the AD does not create alternative technical standards beyond those referenced.

Statements not present in the AD (silences worth noting)

• The AD does not provide an explicitly stated process for accepting alternative methods of compliance (AMOCs) or exemptions within its own wording. It does, however, accept later NAA approved SB revisions. The AD does not specify allowable repair parts, overhaul limits, or the technical standard for "restore functionality" beyond the directions in the referenced SB/MRB/AMM.

• The AD does not specify any appeals, penalty regimes or administrative review processes on its face. It does not, within the text, grant delegated authority to a particular maintenance organisation to certify compliance; that detail is left to operational practice and the referenced documents.

Practical implications of duties and rights

• Operators must schedule and resource a time-based inspection (calendar intervals), manage aircraft availability when a discrepancy is found (grounding until repair), and ensure that their maintenance providers have the relevant SAAB documents or later NAA-approved SB revisions. The AD gives a prescriptive path but does not set out funding, certification, or document-control mechanisms; those responsibilities fall to the operator and maintenance organisation in the normal course.

All cited requirements are taken from the Requirement and Compliance fields and the AMM/MRB references in the text.

The AD text itself does not enumerate penalties, fines or explicit enforcement procedures. The instrument states the corrective requirements, the operative documents to be used, and the compliance deadlines, but it does not set out civil or criminal sanctions, nor a specific enforcement mechanism or procedure within its text.

What the document does show about enforcement posture

• The AD is a formal instrument issued by the delegate of the Civil Aviation Safety Authority (David Punshon) and has an explicit effective date of 8 May 2008 (Compliance). Its form and placement as an "Airworthiness Directive" denote that it is a regulatory safety directive; the AD text, however, includes only the prescriptive duties and timing. The signature block demonstrates an issuing authority.

• The AD refers to SAAB technical publications and an EASA AD (Requirement note). The coexistence of national AD issuance and reference to EASA AD 2008-0054 indicates that the subject received attention from more than one aviation regulator, which typically increases the likelihood of enforcement scrutiny by regulators. The AD text itself, though, does not detail which administrative powers will be used if an operator fails to comply.

Absence of internal penalty clauses

• The AD includes no explicit penalty table, no enforcement powers, and no prescribed administrative process for breach, nor does it provide a mechanism for alternative methods of compliance or appeal within the document text. There is no text specifying reporting requirements, mandatory written record retention details or enforcement contact points.

What operators and maintainers should infer from the AD text

• Because the AD prescribes mandatory technical actions and timing, operators should treat compliance as a regulatory obligation to be integrated into maintenance schedules. The AD makes clear that "restore functionality" is required before further flight where discrepancies exist, which implies immediate operational consequences (aircraft out of service until fixed). The AD’s effective date anchors the compliance timing.

• Since the AD does not itself specify penalties, the practical enforcement route,administrative action, grounding orders, certificate action, or civil penalties,would come under the general enforcement powers of the aviation regulator in practice. The AD’s text, however, provides no internal detail on those mechanisms; readers must look to CASA’s broader enforcement framework for specifics beyond the AD.

In short, the instrument provides no explicit penalty provisions; it provides prescriptive duties and timing, leaving enforcement mechanisms and penalties to the regulatory apparatus referenced by the form and issuer of the AD rather than to the AD text itself.

The AD text refers to other technical and regulatory instruments and thereby establishes cross-links with external documents. The directive itself does not reproduce those documents but requires compliance with them.

Interacting technical documents and authorities cited in the AD

• SAAB Service Bulletin SB 340-32-136: The AD explicitly requires the functional check be done "in accordance with SAAB Service Bulletin (SB) 340-32-136 or later NAA approved revision" (Requirement). That binds the AD’s technical content to the SB’s procedural details, and permits later revisions approved by the relevant National Aviation Authority (NAA) as substitutes.

• SAAB 340 MRB Report, Section F, Revision 6, task number 323106.2: The AD authorises compliance instead with this MRB task as an acceptable procedural path (Requirement). The MRB is the manufacturer’s maintenance review board documentation that is commonly used to define maintenance tasks and intervals.

• SAAB 340 AMM Chapter 32: The AD points to the Aircraft Maintenance Manual Chapter 32 for full system description (Requirement). The AMM will contain technical detail necessary for understanding the valve system and carrying out restorative actions.

• EASA AD 2008-0054: The AD contains a note that EASA AD 2008-0054 dated 5 March 2008 "refers" (Requirement note). This indicates the existence of parallel or prior regulatory action by the European Aviation Safety Agency and suggests regional coordination or corroboration of the safety issue.

Relationships and implications

• The AD operates by mandating adherence to those external SAAB documents or approved revisions thereof. Practically, the directive creates a regulatory obligation that depends on manufacturer and NAA documents for technical detail; changes or approvals made in those documents (for example, a later NAA-approved SB revision) are expressly acceptable under the AD text.

• The Background explains a movement from a flight-hour based interval (5,000 flight hours) in the MRB to a calendar-based interval of every two years because valve lubrication deteriorates with elapsed calendar time (Background). The AD therefore replaces or supplements a flight-hour metric with a calendar-time metric for this task. Where other regulatory instruments rely on flight-hour metrics, this AD mandates a calendar-based schedule for the affected task.

• The presence of an EASA AD reference indicates cross-jurisdictional attention. The AD’s technical requirements mirror the SAAB-specified change and provide national regulatory force to it. The AD’s text does not explicitly harmonise legal authority across jurisdictions; it merely notes the EASA AD’s relevance.

Gaps and limits within the AD text

• The AD does not incorporate the external documents by schedule or annex; it simply refers to them. Any operational question about the precise technical steps, acceptable repair parts, or recording of compliance must be answered by consulting the SAAB SB, MRB task, and the AMM,documents not reprinted in the AD.

• The AD does not set out a procedure for approving alternative methods of compliance (AMOCs) within its text beyond acceptance of later NAA-approved SB revisions. Where an operator might wish to propose a different procedure or interval, that mechanism is not detailed in this AD and will be subject to the regulator’s general processes for AMOC or exemptions outside the AD text.

• The AD describes changes to MRB intervals (from 5,000 flight hours to 2-year calendar intervals) but does not itself amend MRB documents; it compels compliance with the specified MRB revision or SB. The legal effect is that the AD requires following the procedure and interval it references; the MRB or SB remain the working technical standard.

In summary, the AD ties regulatory obligations to manufacturer documents and an EASA AD reference. It shifts the maintenance timing metric to a calendar-based interval for this task and relies on SAAB and NAA approvals for technical detail; it does not itself set cross-jurisdictional harmonisation procedures or alternate compliance pathways beyond those stated.

The AD text provides a compact record that indicates the dates and technical revisions relevant to the subject, but it does not include an internal amendment log or later amendments. The practical amendment history present in the text comprises the following items:

• SAAB MRB change: The Background states that SAAB "has revised the check to cycle the emergency release handle 5 times and amended the interval in MRB section F from 5,000 FH to every 2 years." That indicates a manufacturer-originated technical amendment to the MRB task and interval. The AD requires compliance with MRB Section F, Revision 6, task number 323106.2, which reflects the revision as of that MRB revision (Background; Requirement).

• Service Bulletin revisions: The Requirement text explicitly allows SAAB Service Bulletin SB 340-32-136 or a "later NAA approved revision." That language anticipates and permits future SB updates that receive NAA approval. The AD does not itself list subsequent SB revisions post-issue, but it creates a pathway for operators to follow later NAA-approved revisions without seeking an amendment to the AD text itself (Requirement).

• Regulatory cross-reference: The AD includes a note that EASA AD 2008-0054 dated 5 March 2008 "refers." That EASA AD date precedes the CASA effective date, implying parallel or prior action at the regional level. The AD itself is dated 6 March 2008 in signature but becomes effective on 8 May 2008 (signature and Compliance). There is no further amendment entry in the text.

What the AD does not include on amendment history

• There is no in-text record of any subsequent amendments to AD/SF340/105 after its effective date. The document does not present an amendment log, consolidation note, or revocation clause. The AD does not state whether it supersedes any prior ADs specific to the same task or whether it will be superseded by future ADs.

• The AD does not state whether the MRB Revision 6 referenced is the first to introduce the change from 5,000 flight hours to 2 years or whether earlier MRB revisions had related commentary. It simply identifies MRB Section F, Revision 6, task 323106.2 as an operative document.

Operational takeaway

• For operational compliance, the relevant amendment history is that SAAB changed the MRB task interval and check procedure (to five handle cycles and to a two-year calendar interval), and the AD requires work per the SB or MRB task as identified. The AD’s acceptance of later NAA-approved SB revisions means that future SB updates, if NAA-approved, may be implemented without a separate AD amendment procedure.

• Users tracking historical obligations should note the effective date (8 May 2008), the signature date (6 March 2008), and the underlying MRB revision number (Revision 6) as the relevant snapshot of the technical standard that the AD enforces.

The AD document does not reference any litigation, court decisions, or administrative hearings. There is no litigation history set out within the text.

What the absence of litigation references means in practice

• The AD is a short regulatory safety directive and records only the prescriptive and timing requirements. It contains no mention of legal challenges, appeals or case law arising from the directive. This silence means that, within the four corners of the AD, there are no recorded disputes, injunctions, or judicial outcomes to consider.

• Because the AD refers to EASA AD 2008-0054 and SAAB documents, operators or interested parties who wish to explore whether there has been subsequent legal contestation, interpretive rulings, or enforcement actions should consult external sources: regulator administrative records, court decisions, or enforcement notices. None of that material is included or referenced in the AD text.

Practical implication for practitioners

• Legal or compliance teams reviewing the AD should not assume the absence of litigation more broadly; the AD does not document litigation. If there is a need to know whether the AD has been contested, amended, or subject to judicial review, teams must conduct independent searches of CASA records, tribunal and court databases, and possibly EASA records. The AD itself gives no litigation trail to follow.

• For immediate operational compliance, the lack of litigation history in the AD does not change the stated duties: the functional check and restoration requirement, and the compliance intervals, remain the operative obligations as written.

In sum, the AD contains no litigation or case references. Any enquiry into enforcement disputes or legal contestation must look beyond the AD to external regulatory and judicial sources.

The AD is compact, but several practical misinterpretations or operational hazards can arise if readers do not attend closely to its text and the documents it references. The following points are grounded in the AD’s wording and are designed to prevent common errors.

1. Confusing the documents versus the required action

• The Requirement offers two alternative procedural sources: SAAB SB 340-32-136 (or later NAA-approved revision) or SAAB 340 MRB Report, Section F, Revision 6, task 323106.2. Operators sometimes assume that a reference to an MRB task alone is sufficient without reading the SB, or vice versa. The AD permits either route, but the chosen document is the operative procedural authority for the functional check (Requirement). Do not treat the MRB reference as mere guidance; it is a permissible normative procedure.

2. Misreading the timing requirements

• The Compliance table contains two separate items. Item 1 mandates the check "within the next 6 months after the effective date of this AD, and repetitively thereafter at intervals not to exceed 2 years." Item 2 states "Before further flight, after the effective date of this AD." That second item applies to restoration of functionality after a discrepancy is found during a check (see Requirement). Practically, the sequence is: perform checks within six months and then every two years, and if a check reveals a discrepancy, effect repairs and do not return the aeroplane to service until functionality has been restored. Do not interpret the "before further flight" clause as a standalone requirement to check every aircraft immediately; it is a restraint tied to discovered discrepancies.

3. Calendar-based interval replaces flight-hour interval for this task

• The Background explains SAAB amended the interval from 5,000 flight hours to every two years because valve lubrication performance is dependent on calendar time. That means operators cannot rely purely on flight-hours tracking to meet this AD’s repetitive intervals; they must track calendar dates (Background). Where maintenance programmes are organised primarily by flight hours, failure to convert this task to calendar scheduling can create non-compliance.

4. Cycling the emergency release handle five times is a manufacturer revision, not optional

• The Background explains that SAAB revised the check to cycle the emergency release handle five times and that the AD requires a functional check in accordance with the SB or MRB task, which reflects that change. Operators must ensure the procedural documents they use include the five-cycle requirement (Background; Requirement). If a maintenance team follows an older SB or MRB that omits the five cycles, that would not meet the AD’s specified sources unless the older document has been superseded by a later NAA-approved revision.

5. Later NAA-approved revisions are accepted for the SB but not for the MRB in the AD text

• The Requirement permits the SB or a "later NAA approved revision" of the SB, but the MRB citation is given as "Revision 6, task number 323106.2" with no explicit allowance for later MRB revisions. That suggests operators should be cautious: if relying on the MRB as their procedural authority, confirm that the MRB revision in use matches Revision 6 or that any later MRB revision is acceptable under national approval practice. The AD text specifically permits later NAA approval only in respect of the SB (Requirement).

6. "Restore functionality" is not defined within the AD

• The AD requires restoration of functionality where discrepancies are found but does not define the standards or parts to be used. Practitioners must consult AMM Chapter 32 or the SB/MRB task to determine acceptable restoration procedures and to ensure that repairs satisfy airworthiness criteria (Requirement). Do not assume cosmetic or temporary measures suffice; the AD requires functional restoration and that the aircraft not return to flight until that is achieved (Compliance).

7. The AD references an EASA AD but does not reproduce it

• The AD notes that EASA AD 2008-0054 refers, but it does not include EASA’s text. If operators rely on EASA materials for further interpretation, they must obtain and read the EASA AD separately; the CASA AD does not substitute for EASA’s statements (Requirement note).

8. Effective date versus signature date

• The signature block is dated 6 March 2008, but the AD becomes effective on 8 May 2008 (Compliance). The six-month compliance window runs from the effective date, not from the signature date. Operators should count compliance deadlines from 8 May 2008 (Compliance).

9. Record-keeping and proof of compliance are not specified

• The AD does not state a particular record-keeping format or retention period for proof of compliance. Operators should ensure maintenance records show the functional checks, date, the SB/MRB revision used, findings, and corrective actions. The AD’s silence on documentation requirements does not relieve operators of standard airworthiness record-keeping obligations; it does require them to be able to demonstrate the checks occurred and that any discrepancies were fixed before flight (Requirement; Compliance).

10. Potential for unplanned aircraft downtime

• Because the AD requires that aircraft not fly further until functionality is restored after a discrepancy is found, operators should account for the possibility of immediate grounding and repair time when planning inspections and line maintenance. The AD’s "before further flight" clause creates an operational risk that must be managed.

These are practical points strictly derived from the AD text and its citations to SAAB documents. They are intended to prevent misinterpretation of the document’s concise but specific requirements.

The AD prescribes a straightforward compliance route; the practical steps below rest on the AD’s Requirement and Compliance text and the Background that describes the procedural change.

1. Identify affected aeroplanes and applicable documents

• Confirm which aircraft in the fleet are SAAB SF340A or SF340B aeroplanes (Applicability). Gather the following documents: SAAB Service Bulletin SB 340-32-136 (and check for any later NAA-approved revisions), SAAB 340 MRB Report Section F Revision 6 (task number 323106.2), and SAAB 340 AMM Chapter 32 for the system description (Requirement).

2. Plan the compliance window

• The AD becomes effective on 8 May 2008 and requires the initial functional check "within the next 6 months after the effective date" (Compliance, item 1). Schedule each aircraft for the initial check within that six-month window. After the initial check, schedule repetitive checks at intervals not to exceed two years (Compliance, item 1). Because the AD explains valve lubrication depends on calendar time, use calendar dates to manage recurrence rather than flight-hour counters (Background).

3. Perform the functional check per the operative document

• Execute the functional check in strict accordance with either SAAB SB 340-32-136 (or its later NAA-approved revision) or SAAB 340 MRB Report Section F Revision 6 task 323106.2 (Requirement). Ensure the check incorporates the SAAB-revised action,cycling the emergency release handle five times,if that action is contained in the operative SB/MRB document (Background). Use AMM Chapter 32 for the full system description to understand system interfaces, test points and safety precautions.

4. Document findings and actions

• Record the date of the check, the technical document and revision used (SB revision or MRB Revision 6), the personnel performing the check, any discrepancies discovered and the corrective actions taken. Although the AD does not specify record-keeping details, the evidence of compliance should clearly demonstrate adherence to the SB/MRB procedure and timing set by the AD (Requirement; Compliance).

5. Restore functionality where discrepancies are found

• If a check finds a seized or malfunctioning emergency extension valve or any other discrepancy, restore functionality in accordance with the AMM and SB/MRB instructions (Requirement). The AD mandates that functionality be restored before further flight after the effective date of this AD (Compliance, item 2). Do not release the aeroplane for operation until the valve operates correctly under the functional test conditions specified in the operative document.

6. Use accepted revisions where permitted

• The AD allows use of SAAB SB 340-32-136 or a later NAA-approved revision. If a later SB revision is available and has NAA approval, ensure that the revision is appropriately logged in maintenance records and that its procedural changes are fully implemented (Requirement). If an operator prefers to use the MRB path, confirm that the MRB revision in use matches Revision 6 or that any subsequent MRB revision is validated by the relevant authority, because the AD text identifies MRB Revision 6 explicitly (Requirement).

7. Coordinate with planning and dispatch

• Because a found discrepancy precludes further flight until restored, coordinate the checks during scheduled maintenance windows or when aircraft can be appropriately grounded. Plan for technician availability and for potential part replacement or overhaul if restoration requires component change.

8. Cross-check EASA AD where relevant

• The AD notes EASA AD 2008-0054 dated 5 March 2008 "refers" (Requirement note). Obtain and review the EASA AD for any additional instructions or clarifications that may affect technical procedures, compliance timing, or cross-jurisdictional consistency.

9. Verify compliance intervals and calendar tracking

• Set up calendar reminders or maintenance programme entries that ensure each aircraft undergoes the functional check within two years of the previous check, and not simply at a 5,000 flight-hour threshold. The AD’s Background explains that calendar time is the relevant metric because internal lubrication degrades with elapsed time (Background).

10. Seek clarification where necessary

• If there are technical uncertainties,e.g. ambiguity about which revision of the MRB to use, or what constitutes acceptable restoration,refer to the AMM Chapter 32 and the SB/MRB task. If ambiguity persists, operators should consult their NAA or CASA for interpretive guidance. The AD text itself does not set out an AMOC process beyond acceptance of later NAA-approved SB revisions (Requirement).

By following the exact referenced SAAB documents for procedural detail, scheduling the tasks per the calendar-based intervals mandated, documenting the checks and any repairs, and not returning aircraft to flight until functionality is restored, an operator will meet the AD’s express requirements as written.