AD/LYC/118 Amdt 2 - Superior Air Parts - Cylinder Assemblies

This AD is structured around a small set of interrelated concepts that determine scope and action. The principal concepts and the text locations where they are stated are:

• Applicability. The AD applies to Lycoming Engines 320, 360 and 540 series reciprocating engines fitted with SAP PMA cylinder assemblies manufactured between April 2005 and November 2005, and it lists the specific SAP part numbers concerned (Applicability). The list of P/Ns is extensive and includes, for example, SL32000W-A1, SL36000TW-A22P and many variants. The AD notes that a complete list of aircraft models on which such Lycoming engines may be installed is available in FAA AD 2007-04-19R1 (Applicability, Note 1).

• Part number and serial number dual-criterion. The AD distinguishes between the part numbers (P/Ns) and serial numbers (S/Ns). Compliance requires first determining the P/Ns installed; if the engine contains a P/N listed in the Applicability, the operator must then check serial numbers in accordance with SAP Mandatory Service Bulletin B06-01 Revision E (Requirement, first sentence). Removal from service is mandated only where both the P/N and the S/N are identified by the procedure in the manufacturer’s MSB (Requirement).

• Prescriptive removal and prohibition. The AD commands removal from service of affected cylinder assemblies and forbids installation of any cylinder assembly with the listed P/Ns and S/Ns (Requirement, 1 and 2). The prohibition on installation is absolute for the identified P/N and S/N combinations.

• Compliance timeframe. The AD imposes the practical deadline of before 150 hours TTIS for action on affected cylinders (Compliance, 1). This is an operationally significant milestone because engines with affected assemblies must be addressed relatively early in their service life. For engines already beyond 150 TTIS, the AD allows for special flight permits to ferry aircraft to maintenance, but the AD does not provide the issuing conditions or administrative process for those permits (Compliance, Note 3).

• Reference instruments. The AD delegates the S/N identification procedure to SAP’s Mandatory Service Bulletin B06-01 Rev E dated 24 January 2007, and it refers to FAA AD 2007-04-19R1 amendment 39-15005 for a fuller list of aircraft models on which the engines may be installed (Requirement, Note 2; Applicability, Note 1). The AD itself does not reproduce the full serial-number list; it requires operators to follow the manufacturer’s service bulletin for that detail.

• Safety rationale. The Background sets the causal safety concern as cylinder separation events discovered in SAP-manufactured cylinders installed in various engines, and it connects separation to risks of engine failure, engine compartment fire, and airframe damage (Background).

• Amendment record. The AD contains an amendment history: it records the original issue effective on 2 March 2007, an Amendment 1 effective on 5 March 2007 that referenced the manufacturer’s service bulletin, and Amendment 2 effective on 7 June 2007 that corrects a manufacturing date range and makes editorial changes (Background; Compliance).

These concepts together form the AD’s structure: identify by P/N, check by S/N using the manufacturer’s MSB, remove and refuse installation of affected units, and meet the deadline of 150 hours TTIS or use a ferry permit for movement to maintenance. The AD relies on the SAP Mandatory Service Bulletin and the FAA AD as external instruments to provide lists and cross-references.

The document identifies several concentric groups that are affected directly and indirectly. The affected parties and how they are affected, grounded in the text, are:

• Aircraft owners and operators of aeroplanes fitted with Lycoming 320, 360, or 540 series reciprocating engines that have SAP PMA cylinder assemblies. The Applicability section lists the precise Lycoming engine models in which the listed P/N cylinder assemblies may be installed, for example AEIO-320 -D, -E; IO-320 -B, -D, -E; IO-540 -A, -C, -D, -N, -T, -V, -W; O-360 variants; and others (Applicability). Operators of aircraft with these engines must determine whether their engines are fitted with the listed SAP P/Ns and, if so, check S/Ns as required (Requirement).

• Maintenance organisations and certificated maintenance personnel. The Requirement directs that serial-number checks be made "in accordance with Superior Air Parts, Inc Mandatory Service Bulletin (MSB) B06-01 Revision E dated 24 January 2007" and that removal from service be performed as detailed in that MSB (Requirement). Maintenance providers will therefore perform inspections, S/N verification, physical removals, and record-keeping steps implicit in implementing the MSB procedure. These organisations also decide whether to apply for special flight permits where an engine’s cylinder assemblies exceed 150 hours TTIS and movement is required (Compliance, Note 3).

• Parts suppliers and installers. The AD prohibits installation of any cylinder assembly with the identified P/Ns and S/Ns into any engine (Requirement, 2). Suppliers and installers must ensure that they do not sell, fit, or accept for installation any cylinder assembly matching both criteria. This creates an immediate restriction on the supply chain for the specific P/N/S/N combinations.

• Owners of engines with cylinder assemblies produced by SAP between April 2005 and November 2005. The Applicability explicitly confines the manufacturing date window to that range. Anyone responsible for engines that may have received SAP cylinder assemblies in that period is within the affected set.

• Operators of aircraft types for which a complete model list is not repeated in the AD but cross-referenced to FAA AD 2007-04-19R1. The AD advises that a full list of aircraft models that may have the applicable Lycoming engines is available in the referenced FAA AD (Applicability, Note 1). Thus, operators who are uncertain whether their aircraft model is included must consult the FAA AD.

• Regulatory and oversight actors. CASA, via the delegate signature, is the issuing authority and therefore the entity that prescribes the action and effective date (signature; Compliance). The AD does not in this text specify enforcement procedures or penalties; however, CASA’s issuance and amendment record show regulatory control over the requirement’s timing and scope (Background; Compliance).

• Individuals or organisations relying on fielded evidence of failures. The Background notes that CASA’s action arises from discovery of nine separated SAP cylinder assemblies in other series (TCM 470, 520, 550) and one separated SAP cylinder in the Lycoming 320/360/540 series. That factual discovery affects any party concerned with fleet safety assessment and with decisions about fleet inspection priority.

Who pays. The text places the operational tasks on owners/operators and maintenance organisations. Those parties will bear the direct costs of inspections and removals, potential replacement parts procurement and labour, and downtime to effect the work. The AD does not specify who bears replacement part costs or whether the manufacturer assumes any cost responsibility; the document is silent on cost allocation.

Who decides. CASA decides the mandatory action and effective dates by issuing the AD and amendments (Background; Compliance). For the detailed serial-number determinations and removal procedure, the AD directs adherence to the SAP MSB B06-01 Rev E, so the manufacturer’s document determines the operative serial-number lists and procedure (Requirement). For ferrying beyond 150 hours TTIS, the AD notes that special flight permits may be issued, but it does not specify issuing criteria or which authority handles the permit process (Compliance, Note 3).

The AD imposes specific duties on operators, maintenance organisations, and parts suppliers, and it records limited rights available to operators. The duties and rights, as set out in the AD, are:

Key duties

• Determine part numbers of installed cylinder assemblies. The Requirement opens with a mandate: "Determine the P/N of the cylinder assemblies installed" (Requirement, 1). This is the preliminary duty that triggers subsequent obligations if a listed P/N is present.

• Check serial numbers per the manufacturer’s mandated procedure. If an engine is fitted with an affected P/N, the operator must "check the serial numbers (S/N) of the cylinder assemblies in accordance with Superior Air Parts, Inc Mandatory Service Bulletin (MSB) B06-01 Revision E dated 24 January 2007" (Requirement, 1). The AD delegates the serial-number identification procedure to the MSB, so compliance requires following the MSB’s steps exactly.

• Remove from service identified cylinder assemblies. The AD requires removal from service of any cylinder assemblies that are affected by both the AD’s applicability and the S/Ns detailed in SAP MSB B06-01 Rev E (Requirement, 1). The removal is absolute for units that match both criteria.

• Do not install affected cylinder assemblies. The AD explicitly instructs: "Do not install any cylinder assembly with part numbers and serial numbers identified in Requirement 1 of this AD, into any engine" (Requirement, 2). That prohibition extends to all engines, not merely the Lycoming models listed in the Applicability.

• Meet the compliance timeframe. The AD requires the above actions "Before cylinder assemblies reach 150 hours total time in service (TTIS)" (Compliance, 1). That deadline is a practical duty on operators to schedule inspections and potential removals early in the service life of the cylinder assemblies.

• Follow referenced documents. The AD requires adherence to the SAP MSB B06-01 Rev E for serial-number checks and removal procedure; that MSB is incorporated by reference as the operative method for identifying affected S/Ns (Requirement).

Limited rights and procedural notes

• Right to ferry under a special flight permit where TTIS exceeds 150 hours. The AD notes that "special flight permits may be issued to ferry the aircraft to a maintenance base" for aircraft that already have cylinder assemblies beyond 150 hours TTIS (Compliance, Note 3). The AD does not detail the permit-issuing conditions or process, only that such permits may be issued. This functions as a limited operational relief right to effect compliance without immediate grounding.

• Reliance on external lists. The AD allows operators to consult secondary documents for coverage clarity. For a complete list of aircraft models on which the Lycoming engines may be installed, operators are directed to FAA AD 2007-04-19R1 amendment 39-15005 (Applicability, Note 1). That cross-reference effectively grants operators the ability to confirm applicability via the FAA instrument.

• No installation or use of listed P/N/S/N cylinders. The prohibition on installation is presented as a duty, but it also functions as a right for other operators and maintenance providers to refuse to accept or fit listed assemblies, protecting airworthiness across the fleet.

Limitations and omissions in duties and rights in the text

• The AD does not set out remedial entitlement, reimbursement, replacement part supply, or warranty obligations. It does not allocate costs or specify manufacturer obligations for replacement, nor does it describe enforcement penalties for non-compliance within this document.

• The AD does not provide specific procedural steps for obtaining special flight permits or administrative contact points for compliance questions; these operational details are outside the AD’s expressed text.

• The AD does not specify record-keeping requirements, hours-counting methodology beyond the TTIS threshold, or post-removal actions such as reporting removed parts to CASA or the manufacturer. Those actions may be covered in the SAP MSB, FAA AD, or other regulatory instruments, but are not stated here.

In short, the AD’s key duties are precise: identify P/N, check S/N per MSB B06-01 Rev E, remove affected cylinders, do not install affected cylinders, and act before 150 hours TTIS. The rights are limited to the possibility of a special flight permit to reposition an aircraft for maintenance and access to cross-referenced instruments for clarification.

The text of this AD does not specify statutory penalties, monetary fines, or criminal sanctions for non-compliance. The document sets mandatory safety requirements and effective dates, but it does not record enforcement mechanisms or penalty provisions within the AD’s body as published here.

What the AD does specify about enforcement-adjacent matters

• Mandatory nature of the actions. The AD is framed as a requirement, using imperative language: determine P/N, check S/N per MSB, remove from service affected cylinders, and do not install such cylinders (Requirement). The use of "Remove from service" signals an enforceable safety directive in regulatory practice; however, this document does not set out the enforcement processes or sanctions applicable for breach.

• Effective date and amendment history. The AD records effective dates and amendments (Compliance; Background). Effective dates are enforcement-relevant because non-compliance after the effective date is the temporal axis upon which a regulator typically acts. This AD became effective on 7 June 2007 (Compliance), with prior issuances earlier in March 2007 (Background).

• Operational relief and permits. The AD allows that "special flight permits may be issued to ferry the aircraft to a maintenance base" where cylinder assemblies have greater than 150 hours TTIS (Compliance, Note 3). The existence of an administrative relief mechanism for movement implies regulatory discretion to permit limited non-compliant movement for safety or logistical reasons, but the AD does not describe the criteria, authority, or application process for such permits.

Enforcement mechanisms not present in the text

• The AD does not identify the enforcement authority for contraventions, nor does it specify administrative penalties, suspension or cancellation of certificates, compulsory reporting obligations, or civil liabilities tied to non-compliance.

• The AD does not detail inspection regimes, audit processes, or post-action verification steps that a regulator might use to confirm compliance.

• The AD does not state whether removal of affected assemblies must be reported back to CASA or to the manufacturer, or whether documentation of compliance must be retained and produced on request.

Implications for operators and maintenance organisations

• The absence of explicit penalties in the text provided does not mean non-compliance is without consequence; the AD imposes safety-critical duties that CASA has formalised. In regulatory practice, an AD is a legal instrument that operators are expected to follow. This document, however, leaves open how CASA will enforce compliance, and it directs operators to SAP MSB B06-01 Rev E for the procedural detail needed to satisfy the AD.

• The AD’s compliance timeframe (before 150 hours TTIS) creates an operational deadline that owners and operators must meet or seek the permitted relief of a special flight permit if already beyond 150 hours; failure to obtain such a permit or to remedy the condition could expose the operator to regulatory action under CASA’s broader powers, although those powers and penalties are not specified here.

• Because the AD delegates critical identification steps to the SAP MSB, maintenance providers should ensure they follow the MSB precisely. Any dispute over what constitutes compliance may require reference to the MSB and to CASA’s AD records.

In summary, the AD prescribes mandatory duties without specifying enforcement sanctions or procedural enforcement steps in this text. The practical enforcement context will depend on CASA’s broader regulatory framework and on adherence to the SAP MSB procedure that the AD mandates.

This AD expressly cross-references other regulatory and technical instruments and thereby establishes interaction points that operators must consult to resolve scope, detail, and aircraft model applicability. The relevant interactions recorded in the text are:

• Reference to Superior Air Parts Mandatory Service Bulletin B06-01 Revision E (24 January 2007). The AD requires operators to "check the serial numbers (S/N) of the cylinder assemblies in accordance with Superior Air Parts, Inc Mandatory Service Bulletin (MSB) B06-01 Revision E dated 24 January 2007" and to remove assemblies as detailed in that MSB (Requirement). The AD therefore incorporates by reference the MSB as the operative procedural document for identifying affected serial numbers and for the removal procedure. The practical effect is that compliance with the AD requires compliance with the MSB’s requirements and lists.

• Cross-reference to FAA Airworthiness Directive 2007-04-19R1 amendment 39-15005 dated 23 March 2007. The AD instructs that a complete list of aircraft models on which the applicable Lycoming engines might be installed is available in the FAA AD (Applicability, Note 1). The AD also notes that its Amendment 2 corrects a manufacturing date range based on Revision 1 of the FAA AD (Background). This establishes a harmonisation link between CASA’s AD and the FAA AD: CASA relies on the FAA instrument for aircraft-model scope and adjusted manufacturing date ranges. Operators must therefore consult the FAA AD for full model applicability.

• Relationship between the AD and manufacturer documentation. By delegating serial-number checking to the SAP MSB, the AD converts a manufacturer’s service bulletin into a regulatory requirement for the specified engines and parts. That elevates the MSB from advisory to mandatory status for the purposes of meeting this AD.

• Interaction with special flight permit processes. The AD allows for special flight permits to ferry aircraft having cylinder assemblies with greater than 150 hours TTIS to a maintenance base (Compliance, Note 3). The issuance of such permits is an administrative process that generally involves regulatory authorities and may involve other rules governing airworthiness and flight permissions; however, the AD itself does not detail the permitting process or reference the legislative instrument that governs special flight permits.

• Amendment and convergence with international directives. The AD’s Background records that Amendment 2 corrected the manufacturing date range based on the FAA AD Revision 1 and made editorial changes (Background). That demonstrates CASA’s use of FAA findings to refine its local AD, creating a coordination mechanism between the Australian and US regulatory instruments.

What the AD does not do in terms of legal interactions

• The AD does not purport to amend primary legislation, nor does it reference specific provisions of the Civil Aviation Act or subordinate regulations that give CASA authority to issue ADs. The document simply presents the AD as an operative instruction with an effective date and amendment history.

• The AD does not include text that establishes how it interacts with warranty claims, manufacturer liability, or private contractual remedies between owner and supplier. It is silent on allocation of replacement costs, tendering, or commercial recourse.

• The AD does not specify whether compliance with the SAP MSB and the FAA AD will satisfy any other international requirements; the cross-reference suggests coordination but does not create legal reciprocity statements in the text.

Operational consequences of these interactions

• Operators must consult at least three documents to satisfy scope and procedure: CASA AD AD/LYC/118 Amdt 2 itself, SAP Mandatory Service Bulletin B06-01 Rev E for serial-number identification and removal procedure, and FAA AD 2007-04-19R1 for the full aircraft-model applicability list (Applicability; Requirement, Note 2). This creates a dependent compliance chain: failure to follow any one of these documents may leave an operator uncertain whether they have fully met CASA’s mandate.

• The AD’s reliance on manufacturer and FAA documents implies that technical details, such as which serial numbers are affected, are controlled by external instruments. Operators must secure access to those documents and ensure they refer to the correct revisions and dates noted in the AD.

• Where the SAP MSB and the FAA AD diverge, the CASA AD instructs the operator to follow the MSB and the referenced FAA AD as cross-reference points; Amendment 2 corrected a manufacturing date range based on the FAA AD, indicating that CASA may update its AD to align with FAA findings. Operators should monitor amendments to all referenced documents.

In short, this AD does not operate in isolation; it mandates adherence to a MSB and relies on an FAA AD for completeness, establishing a web of regulatory and manufacturer-document interactions that operators must follow to achieve compliance.

The AD includes a concise amendment chronology and records editorial corrections. The timeline and changes stated in the document are:

• Original issue effective on 2 March 2007. The Background records that "The original issue of this AD became effective on 2 March 2007." This is the initial issuance of the AD in the CASA records (Background).

• Amendment 1 effective on 5 March 2007. The Background states "The amendment 1 of this AD made reference to the cylinders assemblies detailed in the manufacturer’s service bulletin and became effective on 5 March 2007." Amendment 1 incorporated a reference to the manufacturer’s service bulletin, thereby bringing the SAP Mandatory Service Bulletin into the compliance chain for serial-number procedures (Background).

• Amendment 2 effective on 7 June 2007. The Compliance section records the effective date for the current Amendment as "This Amendment becomes effective on 7 June 2007." The Background adds that this current amendment (which is the one recorded in the document) "corrects manufacturing date range based on Revision 1 of the FAA AD 2007-04-19 dated 23 March 2007 and makes a few editorial changes." Amendment 2 therefore adjusted the manufacturing date range and made editorial updates relative to the prior version (Background; Compliance).

• Manufacturer service bulletin revision referenced. The Requirement references "Superior Air Parts, Inc Mandatory Service Bulletin (MSB) B06-01 Revision E dated 24 January 2007" as the operative serial-number-checking procedure. Amendment 1 had previously made reference to the cylinder assemblies detailed in the manufacturer’s service bulletin (Background); Amendment 2 continues to rely on the MSB, now pointing specifically to Rev E.

• Basis for amendment. The Background explains the safety-relevant reason for the AD and for the amendment: discovery of separated SAP cylinder assemblies in TCM 470, 520, and 550 series engines and one separated assembly in Lycoming Engines 320, 360, and 540 series engines prompted CASA to issue the AD to prevent cylinder separation and related hazards. The Background states that the current amendment corrects the manufacturing date range based on FAA AD Revision 1 and makes editorial changes (Background).

• Notes on the FAA AD’s influence. The Applicability contains Note 1: "A complete list of aircraft models, applicable Lycoming engines might be installed on, but not limited to, may be found in FAA Airworthiness Directive 2007-04-19R1 amendment 39-15005 dated 23 March 2007." The Background’s mention of a corrected manufacturing date range based on the FAA AD indicates an iterative alignment between CASA’s AD and the FAA instrument.

• Administrative sign-off. The document is signed and dated "David Punshon, Delegate of the Civil Aviation Safety Authority, 26 April 2007." The signature timing sits between the March issuances and the June effective date; it provides the administrative record and the official responsible for the AD’s issuance (signature).

What the amendment record implies for operators

• Operators should note that the AD has undergone rapid iteration within a short timeframe in March to June 2007. The revisions modified cross-references and manufacturing date ranges. Consequently, operators need to ensure they consult the most recent version (Amendment 2 effective 7 June 2007) and the specific revision of the SAP MSB referenced.

• The AD’s amendment history shows a direct reliance on international harmonisation with the FAA AD; operators tracking applicability or serial-number lists should consult the FAA AD and the SAP MSB as part of a complete compliance package.

• The AD does not include tracked administrative corrections beyond the manufacturing date range correction and editorial changes. There is no record in this document of subsequent amendments after Amendment 2.

In sum, the AD’s amendment history covers an initial issue and two subsequent amendments within the March to June 2007 period, with Amendment 2 correcting the manufacturing date window and pointing to the SAP MSB Rev E as the operative procedural document.

The AD text provided does not record any litigation history. There are no references to legal challenges, court proceedings, judicial review, or administrative appeals within the document. The only legal-adjacent records are the AD’s own amendment timeline and the cross-referenced instruments (SAP MSB and FAA AD). The text itself is an administrative instrument and does not include litigation annotations.

What the absence of litigation history in the document means for practitioners

• The AD as presented contains no judicial decisions, appeals, or disputes recorded in its administrative text. Practitioners cannot infer from this AD whether litigation later occurred, whether CASA was challenged, or whether any enforcement actions prompted hearings; none of that information is included here.

• Where litigated issues might arise in practice, typical topics could include enforcement actions for non-compliance, supplier liability for defective parts, or disputes over the interpretation of the serial-number lists in the SAP MSB. This AD does not record such matters, so practitioners should not assume their presence or absence from this document alone.

• For due diligence, counsel advising affected parties should consult external records, CASA enforcement logs, civil court files and the manufacturer’s correspondence, none of which are reproduced in this AD. The AD points operators to the SAP MSB and FAA AD for technical detail; any litigation over technical interpretation would likely hinge on those referenced documents as much as on the AD itself.

• If a client requires knowledge of post-issuance disputes, enforcement actions, or indemnity claims related to this AD, the AD does not provide that information. Practitioners must source such materials independently from regulatory case files, court databases, or manufacturer records.

Administrative appeal and dispute mechanisms not present

• The AD does not set out any appeals or internal review mechanism for contesting the AD’s content or its application to a specific operator’s aircraft. It simply records the AD, its requirements, and effective date. Any formal mechanism to challenge the AD would exist outside this instrument and is not cited here.

In summary, the document contains no litigation history. For those needing to know whether litigation has since occurred, further independent research beyond this AD is required.

The AD contains several technical and procedural features that can cause practical confusion or operational risk if overlooked. These "gotchas" are grounded in the AD text and the way it ties into external documents. Key points to watch are:

• Dual-criterion for removal: P/N plus S/N. Removal is required only where the cylinder assembly is both of an affected part number and has a serial number identified in the SAP MSB B06-01 Rev E. The AD’s Requirement states operators must "Determine the P/N" and, if the engine is fitted with affected P/Ns, "check the serial numbers (S/N) ... in accordance with" the MSB, then "Remove from service any cylinder assemblies that are affected by both the applicability of this AD and the S/N as detailed in the procedure given in SAP MSB B06-01 Rev E." Practically, this means not all cylinders of the listed P/Ns may need immediate removal; serial numbers matter. Operators who remove units solely on P/N without checking S/N may incur unnecessary costs.

• Dependence on the SAP MSB for S/N lists and procedure. The AD does not reproduce the serial-number list in its text; it requires operators to consult SAP MSB B06-01 Rev E (Requirement). If an operator does not have the exact revision dated 24 January 2007 or uses an earlier/later revision, they risk misapplying the AD. The AD’s Amendment 1 previously made reference to the manufacturer’s service bulletin; Amendment 2 continues to rely on it. Practically, ensure you have B06-01 Rev E dated 24 January 2007, not another revision.

• The manufacturing date window may cause misapplication. The Applicability identifies assemblies manufactured by SAP "between April 2005 and November 2005" as the manufacturing date range. Amendment 2 "corrects manufacturing date range based on Revision 1 of the FAA AD" (Background). Operators must ensure they use the corrected date range referenced by Amendment 2 and not earlier, potentially incorrect ranges in earlier AD versions.

• Compliance clock is short: before 150 hours TTIS. The Compliance section mandates action "Before cylinder assemblies reach 150 hours total time in service (TTIS)". For cylinders already installed with non-zero TTIS, operators must calculate remaining safe time carefully. Failing to act before 150 hours could result in the need for a special flight permit for relocation. Keeping accurate TTIS records is therefore essential.

• Special flight permits are allowed but procedure is not described. Note 3 states that "special flight permits may be issued to ferry the aircraft to a maintenance base" for aircraft that have engine cylinder assemblies with greater than 150 hours TTIS. The AD does not specify how to apply for such a permit, the criteria for issuance, or who to contact. Operators must therefore consult CASA or their usual regulatory contact to obtain a ferry permit; assuming permits will be granted automatically is risky.

• Broad prohibition on installation. Requirement 2 says "Do not install any cylinder assembly with part numbers and serial numbers identified in Requirement 1 of this AD, into any engine." This is a broad prohibition, not limited to the listed Lycoming engines. Practitioners should note the absolute nature of the ban when processing parts inventory or accepting returns.

• Aircraft-model applicability may require FAA AD consultation. The AD does not reproduce the complete list of aircraft models that may carry the affected Lycoming engines; it directs operators to FAA AD 2007-04-19R1 amendment 39-15005 (Applicability, Note 1). Operators of obscure or less-common airframes should consult the FAA AD to confirm whether their aircraft-model/engine combinations are potentially affected.

• Potential supply chain confusion. The AD prohibits fitting certain P/N/S/N assemblies and requires removal where both criteria match. If suppliers or shops are not notified, there is risk of reinstallation or improper resale. Maintenance shops should quarantine stock and update inventory systems to flag the listed P/N/S/N combinations.

• No specification of reporting removed parts. The AD requires removal but does not demand reporting of removed cylinder assemblies to CASA or the manufacturer within this text. Operators should not assume reporting is unnecessary without checking the SAP MSB or other regulatory guidance. The AD’s silence on reporting could lead to inconsistent practices.

• Timing and document version control. The AD references specific documents and dates: SAP MSB B06-01 Rev E dated 24 January 2007, FAA AD 2007-04-19R1 dated 23 March 2007, and the AD’s own Amendment 2 effective 7 June 2007. Using an incorrect document version or the wrong revision date can produce non-compliant actions. Maintain a clear document control trail to show which documents and revisions were followed.

• Editorial and date corrections. The Background records that Amendment 2 makes editorial corrections and corrects the manufacturing date range. Operators relying on the original issue or Amendment 1 may follow incorrect manufacturing date parameters. Always apply the most recent amendment.

These gotchas cluster around precise serial-number matching, document-version control, the 150-hour TTIS clock, undefined permit procedures, and the broad installation prohibition. Operationally, they translate into the need for careful inventory checks, accurate hour tracking, and early engagement with maintenance providers and the regulator for ferry-permit arrangements.

The AD prescribes a concrete, document-referenced compliance pathway. Below is a stepwise, source-grounded procedure to comply with this AD. This is extracted from the Requirement and Compliance text, and from cross-references the AD makes.

Step 1 , Identify engines and cylinder assemblies

• Determine whether the aircraft has Lycoming Engines 320, 360 or 540 series reciprocating engines that may be fitted with SAP PMA cylinder assemblies. The Applicability lists the specific Lycoming engine models where the listed P/N assemblies may be installed; consult that list to identify potential inclusion (Applicability).

Step 2 , Determine installed cylinder part numbers (P/N)

• For each engine, determine the part numbers of the installed cylinder assemblies. The AD’s first directive is "Determine the P/N of the cylinder assemblies installed" (Requirement). Ensure maintenance records and physical component markings are used to confirm exact P/Ns.

Step 3 , If a listed P/N is present, check serial numbers per SAP MSB B06-01 Rev E

• Where the engine is fitted with any of the affected P/Ns (as listed in the Applicability), follow "Superior Air Parts, Inc Mandatory Service Bulletin (MSB) B06-01 Revision E dated 24 January 2007" to check serial numbers of the cylinder assemblies (Requirement). The AD directs that S/N checking be performed "in accordance with" the MSB; do not substitute another procedure unless it is an authorised revision.

Step 4 , Remove affected assemblies from service where both P/N and S/N match

• Remove from service any cylinder assemblies that are affected both by the applicability of this AD (the P/N and manufacturing date window) and by the serial numbers detailed in the MSB procedure (Requirement). The AD requires removal "as detailed in SAP MSB B06-01 Rev E" so follow the MSB’s method for physical removal and any instructions the MSB prescribes about handling, quarantining, tagging or further disposition.

Step 5 , Do not reinstall or install affected P/N/S/N assemblies into any engine

• Do not install any cylinder assembly with part numbers and serial numbers identified in Requirement 1 into any engine (Requirement, 2). Ensure all parts inventory, work orders, and procurement channels are updated to reflect this prohibition.

Step 6 , Comply before 150 hours TTIS or arrange for permitted ferry

• Ensure the actions above are completed before affected cylinder assemblies reach 150 hours total time in service (TTIS) (Compliance, 1). For aircraft where the cylinder assemblies already exceed 150 hours TTIS, arrange for a special flight permit "to ferry the aircraft to a maintenance base" (Compliance, Note 3). The AD does not specify the permit process; therefore contact CASA or your established regulatory liaison to obtain a ferry permit and confirm conditions.

Step 7 , Confirm document versions and keep records

• Use the exact references specified in the AD: SAP MSB B06-01 Revision E dated 24 January 2007; refer to FAA AD 2007-04-19R1 amendment 39-15005 dated 23 March 2007 for a comprehensive aircraft-model list if required (Applicability, Note 1; Requirement, Note 2). Ensure the MSB and FAA AD versions correspond to the AD’s citations.

Step 8 , Coordinate with maintenance provider and supply chain

• If removal is required, coordinate logistics, replacement parts ordering, and maintenance scheduling. Quarantine affected cylinder assemblies and ensure they are not re-entered into stock or sent for re-installation.

Step 9 , Monitor and apply amendment updates

• The AD’s Background notes Amendment 2 corrected the manufacturing date range based on the FAA AD Revision 1. Monitor for any further CASA amendments or updated MSB revisions. Apply the most recent, AD-specified versions for compliance.

Step 10 , Document compliance internally

• While the AD does not state record-keeping procedures in the text provided, maintain internal records that show P/N and S/N checks were performed in accordance with SAP MSB B06-01 Rev E, the date the removal action was taken, TTIS calculations, and any special flight permit obtained. Such records will be necessary to demonstrate compliance in the event of regulatory inquiry, insurance claims, or liability disputes.

Operational checklist for immediate action

• Obtain a copy of SAP MSB B06-01 Revision E dated 24 January 2007 and the FAA AD 2007-04-19R1 dated 23 March 2007.
• Audit the fleet to identify engines and installed cylinder assembly P/Ns that match the AD’s Applicability list.
• For matched P/Ns, perform S/N checks strictly per the MSB.
• Quarantine and remove any cylinders matching the MSB’s S/N list.
• Ensure replacement cylinders are not from the prohibited P/N/S/N combinations.
• If any cylinder is already beyond 150 TTIS, contact CASA regarding a special flight permit before attempting flight.
• Maintain a contemporaneous record of all checks and actions.

The AD’s effective date and timing

• The current Amendment in this document became effective on 7 June 2007 (Compliance). Apply the steps above with reference to that date and the document revisions cited.

Note on things not specified in the AD text

• The AD does not specify replacement availability, cost allocation, reporting obligations to CASA or SAP, or enforcement penalties. Operators may wish to coordinate with the manufacturer for supply and with CASA for administrative guidance on permits and documentation expectations. The MSB may contain additional procedural detail for removal, handling and reporting; therefore follow the MSB closely.

By following the above steps, and using the SAP MSB and FAA AD references as the AD directs, operators and maintenance providers will execute the actions the AD mandates: identify, check, remove where required, and avoid reinstallation, all within the 150-hour TTIS window unless a ferry permit is granted.