AD/ENG/4 Amdt 11 - Piston Engine Continuing Airworthiness Requirements

The instrument revolves around a small set of operational and technical concepts defined or implemented in the AD text and Appendix A. The principal concepts are applicability, maintenance actions (condition checks and overhauls), approved organisation/approved data, time‑between‑overhaul (TBO) hierarchies, and record keeping.

Applicability: The AD applies to piston engines and components necessary for engine operation installed in aeroplanes maintained under CAR 42B CASA Maintenance Schedule. Explicitly excluded are compression‑ignition piston engines using diesel, Jet A‑1, Avtur, aviation kerosene or similar fuels (Applicability). The categories of operations are defined by reference to existing CAR definitions: private operations (CAR 2(7)(d) and 2(7A)), aerial work (CAR 206(1)(a)), and charter operations (CAR 206(1)(b)). The AD therefore differentiates requirements by operational type.

Condition checks (Appendix A: Requirements A1-A4): These are the AD’s behavioural core. Requirement A1 requires an engine performance run to determine engine performance against approved data, with specified parameters to be recorded on CASA Form 728 (or equivalent). Requirement A2 mandates periodic cylinder leak checks in accordance with engine manufacturer procedures or CASA AAC 6‑32 where manufacturer data is unavailable. Requirement A3 covers oil change (A3(a)), oil filter and screen inspection for metallic debris (A3(b)), and recording and review of oil uplifts (A3(c)). Requirement A4 requires a review of the data produced under A1-A3 and corrective action as required.

Overhaul: For charter operations the AD requires engine overhaul and overhaul or replacement of components necessary for operation (Requirement 2.b-c). Overhaul is defined to require an organisation approved for the purpose and compliance with the engine and component manufacturer’s published overhaul procedures, or other approved data if manufacturer data is not available (Definitions). The AD also defines bulk strip as a partial disassembly requiring separation of the crankcase parting flange or removal of the crankshaft and requires that a bulk strip be carried out by an approved organisation in accordance with approved data, with reference to AWB 85‑005.

TBO hierarchy and tolerances: The AD imposes a priority order for component TBO intervals,aircraft manufacturer schedule first, then engine manufacturer, then component manufacturer (Compliance para 2.c.i-iii). It sets timing tolerances: cylinder leak checks must not exceed 100 hours with ±10 hours planning tolerance; oil change intervals are those published by the engine manufacturer with ±10% tolerance; some tasks are to be done at each aircraft periodic inspection (Requirements A1, A4).

Record keeping and data: The AD mandates use of CASA Form 728 or equivalent for engine performance runs and that these completed forms form part of the engine maintenance record (Appendix A A1). It allows, where maximum RPM cannot be reached stationary, an aircraft maintenance release entry by the pilot in command logging the maximum RPM during the last flight prior to inspection (Note A1 to Requirement A1).

Authority and cross‑references: The AD is issued under subregulation 39.001(1) of CASR 1998 and is stated to be in addition to Schedule 5 of the Civil Aviation Regulations. It cross‑references CASA publications AAC 6‑32 (cylinder leak check), AWB 85‑005 (bulk strip elements) and AWB 85‑4 (calendar time overhaul guidelines), as well as CAR 42ZC(4) and Schedule 8 for the circumstances in which a pilot may replace engine oil and filter between periodic inspections (Requirement A3(a)).

These concepts structure who must do what, how often and with what evidentiary record, and create a hierarchy of technical sources that an operator must consult to determine intervals when manufacturer and aircraft schedules differ.

The AD targets a defined set of actors in the general aviation maintenance and operation chain. Explicitly affected parties are owners and operators of aeroplanes with piston engines maintained under the CASA maintenance schedule (CAR 42B), maintenance organisations carrying out engine work, and pilots who perform limited maintenance tasks. The effect differs by type of operation.

Operators by operation type:

• Charter operations: Operators conducting charter (CAR 206(1)(b)) face the most onerous obligations. They must perform Appendix A condition checks, and additionally must overhaul the engine and overhaul or replace components necessary for engine operation. Overhaul must be performed by an organisation approved for the purpose and in accordance with engine/component manufacturer’s overhaul procedures or other approved data (Requirement 2.a-c; Definitions). Charter operators therefore bear the costs and operational planning consequences of mandated overhauls and component replacement where TBOs or calendar time dictate.
• Private operations and aerial work: Operators under private (CAR 2(7)(d) and 2(7A)) and aerial work operations (CAR 206(1)(a)) must carry out the Appendix A maintenance actions in addition to Schedule 5 requirements (Requirement 1). They are not required by this AD to overhaul engines solely on the basis of operation type, unless other TBO schedules apply by component or engine manufacturer instructions.

Maintenance organisations and approved organisations:

• The AD requires some actions to be performed by an organisation approved for the purpose and in accordance with approved data. A bulk strip must be carried out by an approved organisation; overhauls must be performed by an organisation approved for the purpose (Definitions). Maintenance organisations that hold approvals for engine overhaul, bulk strip and similar tasks will be principal service providers. Their availability, capacity and approved data will materially affect operator compliance cost and downtime.

Pilots:

• The AD allows a pilot (other than a student pilot) to replace engine oil and engine oil filter between periodic inspections (Requirement A3(a)), referencing CAR 42ZC(4) and Schedule 8. Where the oil change is done by a pilot, the requirement to inspect oil pressure filter, screens and suction screens for metallic particles is worded so that the inspection clause applies to all oil and filter replacements unless carried out by a pilot (Requirement A3(b)). Pilots also may provide an aircraft maintenance release entry logging maximum RPM during last flight when stationary maximum RPM cannot be safely attained (Note A1), thereby supplying acceptable evidence for A1 where run‑up limitations exist.

Component manufacturers and aircraft manufacturers:

• The AD creates an informational obligation on component and airframe manufacturers in practice. Operators must consult the aircraft manufacturer’s published TBO first for component overhaul intervals; if unavailable, they must consult the engine manufacturer; if still unavailable, they must consult the component manufacturer (Compliance para 2.c.i-iii). This establishes a chain of reliance on published TBO schedules across industry participants.

Regulator and CASA:

• CASA, through its delegate, issues the AD under subregulation 39.001(1) of CASR 1998. CASA will be the enforcement and oversight agency for these AD obligations and the custodian of referenced guidance material such as AAC 6‑32, AWB 85‑005 and AWB 85‑4.

Who is not affected:

• Compression‑ignition piston engines (diesel and similar fuels) are excluded from applicability (Applicability). Operators of those engines thus do not have obligations under this AD.

In summary, the parties that pay (operators, whether private/aerial work/charter), decide (approved maintenance organisations and pilots exercising limited maintenance tasks), and supply data (manufacturers) are explicitly defined. The AD changes the operational decisions for charter operators in particular by mandating overhauls and component overhaul/replacement; private and aerial work operators gain new condition‑check requirements and associated record‑keeping obligations that may shift maintenance timing and costs.

The AD sets discrete duties and limitedised rights related to performing inspections, overhauls, recording results and following a specified hierarchy of technical data. These duties are statutory obligations created by the AD; the AD does not articulate “rights” in the consumer or private law sense beyond permitted procedures (for example, pilot oil changes) and permitted tolerances.

Duties (explicitly stated in the AD and Appendix A):

• Conduct the Appendix A maintenance actions:
  • Requirement A1: Perform an engine performance run in accordance with approved data and record results on CASA Form 728 or equivalent; for turbocharged/supercharged engines adjust output parameters per manufacturer data; complete forms are to be part of the engine maintenance record. Where maximum RPM cannot be achieved with the aircraft stationary, an aircraft maintenance release entry by the pilot in command documenting maximum RPM during last flight suffices (Note A1).
  • Requirement A2: Carry out cylinder leak checks per engine manufacturer procedures or CASA AAC 6‑32 when manufacturer data is not available; record results in the engine logbook.
  • Requirement A3: Replace engine oil and oil filter at manufacturer‑published intervals with ±10% tolerance (A3(a)); inspect oil pressure filter, oil pressure screen and suction screen for metallic debris at each oil/filter replacement unless the replacement was carried out by a pilot (A3(b)); record oil uplifts and review records (A3(c)).
  • Requirement A4: Review all data from A1-A3 at each aircraft periodic inspection and take corrective action where required.
• For Charter operations specifically:
  • Carry out Appendix A actions (Requirement 2.a).
  • Overhaul the engine at intervals in accordance with the engine manufacturer’s published TBO periods (Requirement 2.b).
  • Overhaul or replace components necessary for engine operation following the prioritised TBO schedule (Requirement 2.c).
• Follow the TBO hierarchy for component intervals: aircraft manufacturer’s published TBO first, then engine manufacturer, then component manufacturer (Compliance para 2.c.i-iii).
• Ensure bulk strip and engine overhaul tasks are carried out by organisations approved for that purpose and using approved data (Definitions: bulk strip, overhaul).

Rights, permissions and permitted variations explicitly allowed by the AD:

• Pilot oil change: A pilot (other than a student pilot) may perform oil and oil filter replacement between periodic inspections (A3(a)), subject to CAR 42ZC(4) and Schedule 8. The AD thereby allows limited self‑service maintenance by qualified pilots.
• Alternative acceptable data for A2: If the engine manufacturer’s leak‑check procedures are not available, operators may comply by following CASA AAC 6‑32 (A2).
• RPM evidence substitution: Note A1 expressly permits an aircraft maintenance release entry by the pilot in command as acceptable data where stationary maximum RPM cannot be safely obtained, subject to manufacturer constraints noted in approved maintenance data.
• Tolerances: The AD specifies permissible planning tolerances that operate as limited flexibility in scheduling (Requirement A2 ±10 hours; Requirement A3(a) ±10% on manufacturer intervals).

Conditionalities and procedural constraints:

• Overhaul and bulk strip actions must be performed by approved organisations and pursuant to approved data; therefore, the “right” to perform these tasks is conditional on having the required approvals and access to required data.
• The AD does not itself create a new definition of “airworthy” beyond referencing an existing definition that the aircraft must meet its type design or properly altered condition (Definitions: Airworthy). It therefore ties compliance to maintenance actions necessary to retain that state.

Documentary duties:

• Completed CASA Form 728 or equivalent performance reports must be retained as part of the engine maintenance record (Appendix A A1).
• Cylinder leak check results must be recorded in the engine logbook (A2).
• Oil uplift records must be recorded and reviewed (A3(c)).

The AD thereby creates a compliance structure of duties across operational types, establishes which tasks can be done by whom, and creates discrete document and inspection obligations. It grants limited practical permissions (pilot oil change, substituted RPM evidence, use of AAC 6‑32) but ties major invasive work to approved organisations and approved data, constraining who may lawfully perform overhaul and bulk strip activities.

The AD is issued under the statutory authority of subregulation 39.001(1) of CASR 1998, and the document itself states that it is issued by the CASA delegate who “requires that the action set out in the requirement section … be taken” (preamble). The AD establishes mandatory obligations; however, the AD text does not specify particular pecuniary fines or criminal offences in itself. The instrument should therefore be read as imposing regulatory obligations enforceable under the broader CASR/Civil Aviation regulatory framework rather than as setting standalone penalties within the AD text.

What the AD states about enforcement mechanics:

• The AD is made under subregulation 39.001(1) of CASR 1998 (introductory paragraph). That provision is the statutory basis for CASA delegates to issue ADs requiring action to correct unsafe conditions. The AD requires operators to take specified actions “in the circumstances mentioned” and “in accordance with the instructions set out in the requirement section” (preamble).
• The AD revokes AD/ENG/4 Amdt 10 and replaces it. Revocation and reissuing are enforcement tools to update mandatory regulatory obligations.

What the AD does not state:

• The AD does not itself list fixed penalty amounts, infringement notices or criminal penalties. It does not specify an administrative enforcement process in the text provided.
• The AD does not attach direct sanctions for non‑compliance in the instrument. There is no express “failure to comply is an offence punishable by …” clause in the text given.

Consequences and practical enforcement implications (grounded in what the AD does state):

• Non‑compliance will mean that engines and components will not meet the continuing-airworthiness standard required under the regulatory framework, with consequences in practice for the aircraft’s airworthiness status (the AD ties actions to maintaining airworthiness).
• Enforcement action for failure to comply with ADs is exercised under the powers conferred on CASA by CASR and related statutory provisions. Although the AD text does not state penalties, CASA has existing enforcement tools under CASR (inspections, grounding, notices, infringement notices, prosecutions) typically used in aviation regulatory regimes. The AD should therefore be treated as a mandatory regulatory instrument within that enforcement landscape.

Operational risk exposure:

• Operators who fail to conduct the Appendix A checks or to undertake required overhauls for charter operations will run compliance risk, increased regulatory exposure on inspection, and potential grounding or other regulatory action if CASA determines the aircraft is not airworthy. The AD requires documentation (CASA Form 728 and engine logbook entries) as demonstrable evidence of compliance; absence of such records increases exposure in any regulatory inspection or enforcement action.

Practical note for operators and maintenance organisations:

• Because the AD places surgical maintenance obligations on approved organisations and references approved data and manufacturer TBOs, records demonstrating the use of approved data and that approved organisations performed required work will be important in responding to any CASA compliance activity.

In sum, the AD establishes mandatory duties and sits inside CASR enforcement machinery; the instrument itself does not list specific penalties, but non‑compliance will be actionable by CASA under the regulatory powers referenced in the AD’s enabling clause.

The AD is tightly integrated with the Civil Aviation Regulations framework and CASA guidance material. The AD repeatedly cross‑references CAR/CASR provisions, CASA advisory and technical publications, and the CASA maintenance schedule. All references in the AD are explicit; interaction here is operational and normative rather than merely aspirational.

Primary statutory interactions:

• Issuing power: The AD is issued under subregulation 39.001(1) of CASR 1998 (preamble). That is the statutory hook that permits CASA to impose mandatory ADs requiring action to correct unsafe conditions. The AD therefore sits within and derives force from CASR.
• Maintenance schedule and Schedule 5: The AD applies to engines installed in aeroplanes maintained in accordance with CAR 42B CASA Maintenance Schedule and operates “in addition to the requirements of Schedule 5 of the Civil Aviation Regulations” (Requirement section). Therefore, Schedule 5 obligations remain in force and the AD layers on more specific engine condition checks and overhaul requirements.
• Operational definitions: The AD relies on CAR definitions to define operational categories: private operations (CAR 2(7)(d) and 2(7A)), aerial work operations (CAR 206(1)(a)) and charter operations (CAR 206(1)(b)). The legal classification of an operator under CAR determines which parts of the AD apply. That interdependence is operationally material.

Other regulatory and advisory documents referenced:

• CAR 42ZC(4) and Schedule 8: These are referenced in Requirement A3(a) as the legal basis for allowing a pilot (other than a student) to perform oil and filter replacement between periodic inspections. The AD therefore defers to other CAR provisions to set the boundaries on who may conduct certain maintenance tasks.
• CASA AAC 6‑32: Required for cylinder leak checks when manufacturer procedures are unavailable (Requirement A2). The AD thus integrates CASA technical advisory content into the AD’s acceptable means of compliance.
• AWB 85‑005: The AD directs that a bulk strip be carried out by an organisation approved for the purpose and in accordance with approved data and references AWB 85‑005 for elaboration where manufacturer instructions are not available (Definitions). AWB 85‑005 thus operates as a procedural backstop.
• AWB 85‑4: Note A2 to Requirement A4 points to AWB 85‑4 “Aircraft Piston Engine Calendar Time Overhaul” for guidelines on inspections related to calendar time overhaul.
• Manufacturer published data (aircraft, engine, component manufacturers): The AD gives primacy to aircraft manufacturer TBOs for components, then engine manufacturer TBOs, then component manufacturer TBOs (Compliance para 2.c.i-iii). This creates a structured interplay between regulatory mandatory actions and private technical publications.

Regulatory layering and precedence:

• The AD expressly operates “in addition to” Schedule 5. Operators must therefore reconcile Schedule 5 periodic inspection requirements with the Appendix A condition checks and with any manufacturer TBOs applicable to engines and components.
• When manufacturer data is missing or silent, the AD directs operators to CASA AACs and AWBs as acceptable alternative data. That is an interaction where non‑statutory advisory instruments are elevated into the compliance chain as fallback sources.

Practical interactions to note:

• The AD’s differentials between charter and private/aerial work operations mean that an operator’s legal classification under CAR affects maintenance obligations. This can interact with licensing, commercial operations certificates and regulatory oversight under CAR 206 definitions.
• The AD’s requirement that bulk strip and overhaul be done by an approved organisation interacts with approvals and certification regimes under CASR/CAR for maintenance organisations. Availability of approvals and capacity constraints may thus be a limiting factor in compliance scheduling.

What the AD does not do:

• It does not amend CAR text itself; it references and builds on CAR/CASR requirements. It also does not replace manufacturer data; rather, it establishes a compliance hierarchy that gives precedence to aircraft manufacturer TBOs, then engine, then component manufacturer schedules.

Overall, the AD is embedded in the existing CASA regulatory architecture: it prescribes mandatory tasks under the AD regime, defers to CAR/CASR for operational definitions and pilot maintenance permissions, and incorporates specific CASA advisory material as acceptable fallback technical data.

The AD incorporates and summarises prior amendments in its background section. The document explicitly states the history of prior amendments and the effective date of the current amendment. The AD itself (Amdt 11) revokes Amendment 10 and becomes effective 15 January 2009, with the delegate’s signature dated 28 November 2008.

Recorded amendment timeline in the AD Background:

• Amendment 11 (current): Becomes effective 15 January 2009 and is the document the AD text represents. It clarifies TBO requirements for engine components and includes editorial changes where appropriate (Background).
• Amendment 10: Excluded compression‑ignition engines from the applicability list and became effective on 26 October 2006 (Background). Amendment 11 revokes Amendment 10 as part of its issuance.
• Amendment 9: Became effective on 22 January 2004 (Background).
• Amendment 8: Became effective on 26 December 2001 (Background).
• Amendment 7: Became effective on 8 October 1998 (Background).
• Amendment 6: Was rescinded prior to its effective date (Background).
• Amendment 5: Became effective on 30 March 1995 (Background).
• The original issue of this Airworthiness Directive superseded Air Navigation Order 108.5.2.1 (Background).

Observations grounded in the text:

• The AD’s background states that Amendment 10 excluded compression‑ignition engines from applicability; Amendment 11’s text retains that exclusion (Applicability). The amendment history therefore documents an earlier substantive narrowing of scope and shows a continuing refinement of the AD’s scope and technical content.
• Amendment 11 clarifies the requirement for TBO for engine components and makes editorial changes where appropriate (Background). The clarity on component TBOs manifests in Compliance para 2.c where the three‑tier priority order for component TBO schedules is specified.

Practical implications of the history:

• The multiple past amendments indicate that the AD has been iteratively updated over more than a decade (original, Amdt 5-11). This historical sequence suggests that CASA has used the AD mechanism to respond to changing operational realities and to incorporate clarifications, exclusions and procedural guidance over time.
• The revocation of Amendment 10 by Amendment 11 reflects the standard AD lifecycle where prior ADs are superseded and replaced to consolidate current expectations.

What the AD does not provide:

• The AD text does not include the full text of prior amendments in situ; rather, it summarises their effective dates and a short description (Background). For the precise content of prior amendments, reference to CASA archives or the superseded ADs would be required.

In short, the AD contains a short but explicit amendment history: Amendment 11 effective 15 January 2009 replaces Amdt 10 and forms the current regulatory instrument, building upon a series of prior amendments dating back to at least the mid‑1990s.

The text of AD/ENG/4 Amdt 11 contains no reference to litigation or judicial review related to this AD or its predecessors. The Background and other sections list previous amendments, effective dates and the administrative actions taken (revocation/supersession), but they do not cite any court cases, tribunal decisions or legal challenges.

What the source explicitly provides:

• The AD shows the administrative genealogy of the instrument (original, Amendments 5-11) and indicates that Amendment 6 was rescinded prior to its effective date (Background). This is an administrative history, not a litigation history.
• There are no named cases, judgments, or references to litigation affecting the content or enforceability of the AD in the provided text.

Implication for practitioners:

• Because the AD itself does not report any dispute history, practitioners should not assume settled judicial interpretation of ambiguous provisions in the AD based on this document alone. If a practitioner requires authoritative judicial interpretation on points such as the scope of “approved data,” the legal effect of the TBO hierarchy, or the proper application of pilot maintenance permissions under CAR 42ZC(4), a separate search of judicial databases and tribunal decisions will be necessary; none are supplied or referenced in the AD text.
• Absence of litigation references in the AD does not mean disputes have not arisen in practice; it simply reflects that the instrument does not disclose litigation history. For matters where legal risk is an issue (for example, disputes over whether a particular action qualifies as an overhaul, or whether an organisation is sufficiently “approved”), operators and maintenance organisations should not rely solely on the AD text as resolving such disputes.

Recommended practical step (grounded in the AD’s silence on litigation):

• If a party anticipates contested enforcement action or needs legal certainty beyond the AD’s text (for instance, regarding the sufficiency of an approved organisation’s data), seek specific legal advice and consider administrative remedies or clarification requests to CASA. The AD itself is silent on any past litigation outcomes or authoritative interpretations that could be binding precedent.

To restate: the AD contains no litigation history; it is an administrative regulatory instrument that documents amendments and technical requirements but does not discuss any judicial or tribunal proceedings.

The AD contains several provisions and cross‑references that can produce compliance surprises if operators, maintenance organisations, pilots or auditors do not read the instrument carefully. The following are concrete operational “gotchas” identified from the text that practitioners should note.

1. Differential obligations by operation type

• Charter operations must not only carry out Appendix A maintenance actions, they must overhaul the engine and overhaul or replace components necessary for engine operation (Requirement 2.a-c). Private and aerial work operations are not required by this AD to perform engine overhauls purely because of operation type. Failure to appreciate this difference can result in under‑maintenance (for charter) or unnecessary overhaul (if misapplied).

2. Compression‑ignition engines excluded

• Compression‑ignition piston engines (diesel, Jet A‑1, Avtur, aviation kerosene or similar fuels) are excluded from applicability (Applicability). Treating such engines as in scope could produce wasted maintenance cost and unnecessary regulatory record creation; conversely, misclassification of fuel type or engine type by an operator may lead to erroneous compliance positions.

3. Chain of precedence for component TBOs

• The AD requires operators to use the aircraft manufacturer’s published TBO for a component first; if none, then the engine manufacturer’s TBO; if none, then the component manufacturer’s TBO (Compliance para 2.c.i-iii). Operators who apply component manufacturer TBOs without checking for aircraft or engine manufacturer schedules will be out of compliance. The AD effectively elevates aircraft manufacturer schedules above component manufacturer instructions for component overhaul intervals.

4. Approved organisation requirement for bulk strip and overhaul

• Bulk strip and overhaul must be performed by an organisation approved for the purpose and in accordance with approved data (Definitions). Operators who attempt to perform bulk strip or overhaul in‑house without the appropriate approvals risk non‑compliance. AWB 85‑005 is referenced for bulk strip guidance; absence of manufacturer instructions must be supplemented with approved data.

5. Tolerances are specific and different by requirement

• Requirement A2 (cylinder leak check) is required at intervals not exceeding 100 hours with a planning tolerance of ±10 hours. Requirement A3(a) (oil change) uses the engine manufacturer’s interval with ±10% tolerance. These are distinct scheduling rules; treating them interchangeably (for example, using ±10% for A2) is incorrect.

6. Pilot oil change is permitted but inspection obligations differ

• A pilot (other than a student pilot) may replace engine oil and oil filter between periodic inspections (A3(a)), but the inspection requirement for oil pressure filter, oil screen and suction screen for metallic particles applies to all oil and filter replacements unless carried out by a pilot (A3(b)). This creates a situation where a pilot‑performed oil change may not trigger the inspection duty, but oil changes performed by maintenance staff do. Practically, this can lead to inconsistent inspection coverage unless operators set clear internal procedures.

7. Documentary substitution for engine run‑up

• Note A1 permits an aircraft maintenance release entry by the pilot in command of the maximum RPM during the last flight to substitute for a stationary maximum RPM run when the aircraft cannot safely attain it stationary or manufacturer data requires run during take‑off/climb. Operators relying on this substitution must ensure the maintenance release is correctly completed and retained as part of the maintenance record (Appendix A A1).

8. Record retention and form specificity

• The AD mandates use of CASA Form 728 or an equivalent form for engine performance reporting and requires that completed forms become part of the engine maintenance record (Appendix A A1). Failure to retain properly completed forms will expose operators under any CASA inspection.

9. Overhaul defined to require published manufacturer procedures or “other approved data”

• Overhaul must follow manufacturer published overhaul procedures, and where manufacturer data is unavailable, other approved data may be used (Definitions). Determining what qualifies as “other approved data” requires documented approval or demonstrated equivalence. Relying on internally generated procedures without approval may be non‑compliant.

10. Multiple referenced documents create compliance complexity

• The AD cross‑references CAR/CASR provisions (CAR 42B, CAR 206, CAR 2, CAR 42ZC(4), Schedule 5, Schedule 8), CASA advisory material (AAC 6‑32, AWB 85‑005, AWB 85‑4) and manufacturer data. Operators must track and reconcile all these materials to determine precise duties. Missing a reference or misreading the sequence (for example, failing to check aircraft manufacturer TBO first) is a common operational pitfall.

11. Effective date and retrospective compliance

• Amendment 11 becomes effective 15 January 2009. Any actions taken prior to that date may be under prior amendments; operators should ensure historical records demonstrate compliance as of the effective date for audits and inspections.

These “gotchas” are concrete interpretation and implementation hazards contained in the AD’s language and cross‑references. Practitioners should build checklists and compliance workflows that explicitly reference each AD clause and the associated referenced documents to avoid misapplication.

Compliance with AD/ENG/4 Amdt 11 requires a combination of procedural changes, record‑keeping, scheduling, organisational approvals and access to approved technical data. The following is a practical, structured compliance path grounded in the AD’s provisions.

1. Legal classification and applicability check

• Confirm whether your aeroplane’s engine(s) are piston engines and not compression‑ignition piston engines using diesel/Jet A‑1/Avtur/aviation kerosene etc. (Applicability). If the engine type is excluded, the AD does not apply.
• Determine the operational category of the aircraft under CAR definitions (private CAR 2(7)(d) and 2(7A); aerial work CAR 206(1)(a); charter CAR 206(1)(b)). This classification dictates whether engine overhaul obligations apply in addition to Appendix A.

2. Establish and document approved organisations and data

• For any overhaul or bulk strip work, ensure you have access to an organisation “approved for the purpose” to perform those tasks and that work will be performed in accordance with engine and component manufacturer’s published overhaul procedures or other approved data where manufacturer data is not available (Definitions). Maintain approval documents on file.
• If manufacturer overhaul procedures are unavailable, obtain and document “other approved data” or seek CASA advice/acceptance. Log the source and approval reference.

3. Create an inspection schedule aligned to the AD and TBO hierarchy

• For engines in charter operations: schedule engine overhauls in accordance with the engine manufacturer’s published TBO (Compliance 2.b). Document the source TBO and the scheduled overhaul date.
• For component overhaul/replacement scheduling: implement the AD’s priority order,check aircraft manufacturer published TBO first; if none, check engine manufacturer; if none, check component manufacturer (Compliance 2.c). Maintain a component TBO register annotating which source was used and when.
• For Appendix A items:
  • Requirement A1: schedule an engine performance run to coincide with each aircraft periodic inspection (Appendix A A1 and Compliance A1). Ensure runs follow approved data and, for turbocharged/supercharged engines, adjust parameters per manufacturer data.
  • Requirement A2: schedule cylinder leak checks at intervals not exceeding 100 hours with ±10 hours planning tolerance. Document each check in the engine logbook per A2.
  • Requirement A3(a): schedule oil change and filter replacement at engine manufacturer published intervals with ±10% tolerance. If pilot oil changes are relied upon, ensure CAR 42ZC(4) authorises the pilot action and document the pilot’s identity.
  • Requirement A3(b): at each oil/filter replacement (unless carried out by a pilot), inspect oil pressure filter, pressure screen and suction screen for metallic particles; document findings and corrective actions.
  • Requirement A3(c): record each oil uplift and conduct periodic reviews of oil uplift records; document any corrective actions taken.

4. Performance run protocol and records

• Adopt or adapt an engine performance run procedure consistent with approved data. Use CASA Form 728 or an equivalent form for recording engine and aircraft details and measured parameters. Keep completed forms as part of the engine maintenance record (Appendix A A1).
• If the aircraft cannot safely attain maximum RPM with the aircraft stationary and manufacturer data requires a take‑off/climb run, ensure the pilot in command records the maximum RPM during the last flight on the aircraft maintenance release and retain that release as acceptable data (Note A1).

5. Cylinder leak check procedure

• Where the engine manufacturer provides leak‑check procedures, use those. If manufacturer procedures are not available, use CASA AAC 6‑32 as the acceptable method (Appendix A A2).
• Record the results in the engine logbook. Where leaks exceed acceptable limits, take corrective action and record repairs.

6. Oil system inspection and oil uplift management

• Put in place a standard practice for oil and oil filter replacements and inspection of oil pressure filter, pressure screen and suction screen for metallic particles at each replacement (unless carried out by a pilot). Record all oil uplifts and a responsible person must periodically review the records for trends (Appendix A A3(b) and A3(c)).
• If pilots perform oil changes, maintain a signed record and ensure the pilot is not a student pilot as specified (Appendix A A3(a)).

7. Corrective action and review process

• At each aircraft periodic inspection, perform Requirement A4: review the performance run, leak check and oil inspection/uplift records and take corrective action as necessary. Document the review findings and any corrective actions and place documentation in the engine maintenance record (Appendix A A4).

8. Documentation and audit trail

• Maintain CASA Form 728 (or equivalent), engine logbook entries for leak checks, oil change and uplift records, maintenance releases for RPM evidence where applicable, overhaul and bulk strip certificates from approved organisations and any approvals for the use of “other approved data”.
• Ensure records clearly identify which TBO source was used for each component (aircraft, engine or component manufacturer) and that tolerances used for scheduling are recorded (e.g. ±10 hours, ±10% where applicable).

9. Internal controls and supplier management

• Verify that any maintenance organisation used holds the necessary approvals for bulk strip and overhaul work. Where an internal maintenance organisation is used, confirm it holds the required CASA approvals and that its procedures are approved data.
• Establish procedures for periodic review of compliance status and readiness for CASA inspection, including sample audits of CASA Form 728 completeness and engine logbook entries.

10. Seek clarification where necessary

• Where the AD references “other approved data” or where manufacturer instructions are silent, obtain written clarity from CASA or the approving authority for your maintenance organisation to avoid disputes over sufficiency of data. Document any CASA responses as part of the maintenance record.

By following the structured steps above and keeping documentary evidence for each decision (TBO source, approval, inspection record, repair action), an operator or maintenance organisation will create an auditable compliance trail that aligns with the AD’s explicit requirements.