AD/MAKILA/9 Amdt 1 - Engine Control Unit - Comparator/Selection Board

The AD rests on a small number of technical and administrative concepts, stated in the instrument and its background text. These concepts define the risk addressed, the mechanical remedy, the procedural requirements, and the transition rules.

• Backup control law (TU203). The Directive states that "Modification TU203, applicable to Makila 1A and Makila 1A1 engines, introduced a control system backup law that fixes N1 (gas generator speed) at 65% when at least two of the three N2 (power turbine speed) signals are lost." This is the safety mechanism whose behaviour under certain failure modes is the impetus for the AD. The concept identifies the condition that the ECU will enter a fixed N1 backup (65%) when it detects a loss of sufficient N2 inputs.

• Unexplained activations and suspected signal corruption. The AD records that "Recent occurrences of 65% N1 backup activation remain unexplained despite detailed investigation" and that "it is postulated that the events may have been due to corruption of the engine N2 speed signals by short perturbations, for example by EMI." The instrument therefore treats transient or spurious corruption of N2 signals as a plausible, though unproven, operational cause. The AD frames the risk in terms of the potential for both engines on the same helicopter to be affected simultaneously.

• Hardware modification to the Selector-Comparator board (TU250). The directive requires replacement of the Selector-Comparator board with one incorporating Turbomeca modification TU250. The stated functional effect is that TU250 "allows recovery from the 65% backup mode if the loss of N2 speed signals is determined to be temporary." Mechanically, the remedy is a hardware board substitution within the ECU.

• Mandatory Service Bulletin as method of compliance. The AD does not provide a step‑by‑step technical procedure in its own text; it mandates performance "in accordance with Turbomeca Mandatory Service Bulletin 298 73 0250 dated 23 March 2007 or later revision approved by the European Aviation Safety Agency (EASA)." The Service Bulletin thus provides the operative technical and administrative steps and is incorporated by reference for compliance.

• Compliance certificates and manufacturer records. The AD requires "replacement of the Selector-Comparator board and return of the Modification Compliance Certificate to Turbomeca," placing a record‑keeping and notification obligation on the maintainer/operator to the manufacturer.

• Applicability and transition windows. The AD is limited (by this Amendment) to civil helicopters. It sets a staged compliance: Requirement 2 (at least one engine per helicopter fitted with TU250) must be carried out "after 30 November 2008," while the total replacement of the Selector-Comparator boards (Requirement 1) must be done "not later than 30 November 2009." Note 2 permits mixed installation of pre‑TU250 and post‑TU250 ECUs within the same helicopter until 30 November 2009.

• Reference to external regulator. The AD explicitly references EASA AD 2007‑0144R1 and requires EASA approval for later revisions of the Turbomeca Service Bulletin. The Directive therefore relies on EASA's role for approving later technical revisions and for cross‑referencing similar regulatory action.

These main concepts define the action logic: a hardware fix is mandated to address an identified risk of spurious transition to a fixed N1 backup mode, compliance follows a manufacturer bulletin approved by an external regulator, and the operator must evidence compliance by returning a certificate to the manufacturer. The AD uses transitional dates to allow stepwise implementation and allows mixed equipment temporarily.

The AD identifies and therefore binds a defined set of actors and assets. The immediate technical applicability is to "Makila 1A and Makila 1A1 turbo‑shaft engines" (Applicability). The AD adds a note that these engines are "known to be installed in, but not limited to, Eurocopter AS 332 C, C1, L and L1 helicopters" (Note 1). The Amendment further "limits the applicability to civil helicopters" (Background), which narrows the covered aircraft to civil operations where those engines are installed; the text thus excludes non‑civil (for example military) helicopter operations from the amendment's scope as stated.

Directly affected parties and roles named or implied in the AD:

• Operators/Owners of helicopters with Makila 1A or 1A1 engines. They bear the primary responsibility to ensure compliance with the AD by arranging and paying for the hardware change, coordinating maintenance, and assuring that at least one engine per helicopter has the TU250-modified Selector‑Comparator board after the stated date.

• Maintenance organisations and engineers who will execute the replacement. They must carry out the replacement "in accordance with Turbomeca Mandatory Service Bulletin 298 73 0250 dated 23 March 2007 or later revision approved by EASA," and must generate and transmit the Modification Compliance Certificate to Turbomeca as required.

• Turbomeca (the manufacturer). Turbomeca supplies the TU250-modified board, issues the Mandatory Service Bulletin that prescribes the corrective action, and receives the Modification Compliance Certificate following the work. The AD makes Turbomeca the repository for compliance confirmations and the author of the technical method to be followed.

• Civil Aviation Safety Authority (CASA) or its delegate. The AD is issued under CASA authority; it is dated and signed by "James Coyne, Delegate of the Civil Aviation Safety Authority" (13 June 2008). CASA determines the legal force of the Directive in the Australian civil aviation domain and sets its effective date (20 June 2008).

• European Aviation Safety Agency (EASA). EASA's role is to approve later revisions of the Turbomeca Service Bulletin; the AD also references EASA AD 2007‑0144R1. While the AD is an Australian instrument, it explicitly relies on EASA for approval and cross‑reference.

• Helicopter airframes that incorporate these engines. Although the AD's technical requirement is engine‑centric, operators must coordinate with airframe maintenance schedules and potentially with the airframe manufacturer where system interfaces exist.

Who pays: The AD does not state cost allocations or funding arrangements. Practically, the replacement of hardware and associated labour will be a cost to the owner/operator and their maintenance provider. The AD requires return of a Modification Compliance Certificate to Turbomeca, which imposes an administrative burden and a manufacturer record obligation on the maintainer/operator.

The AD does not identify any exemptions, waivers, or alternative methods of compliance within its text. It allows mixed installation of pre‑ and post‑TU250 ECUs temporarily (Note 2), and it specifies that later revisions of the service bulletin are acceptable only when approved by EASA.

The AD sets out specific duties and a small set of permissive allowances relevant to operators and maintainers. The duties are prescriptive and time‑bounded; rights or allowed alternatives are limited and specifically stated.

Key duties

• Replace Selector‑Comparator board incorporating TU250. Requirement 1 states: "Replace the Engine Control Unit (ECU) Selector-Comparator board with one incorporating Turbomeca modification TU250." The duty is to install the TU250-modified board in place of the existing Selector‑Comparator board.

• Follow the prescribed Service Bulletin. Requirement 1 further specifies that "Replacement of the Selector-Comparator board and return of the Modification Compliance Certificate to Turbomeca must be performed in accordance with Turbomeca Mandatory Service Bulletin 298 73 0250 dated 23 March 2007 or later revision approved by the European Aviation Safety Agency (EASA)." The duty therefore includes adherence to the procedural, installation, and certification steps in that Service Bulletin or its EASA‑approved successor.

• Return a Modification Compliance Certificate to Turbomeca. Completion of the work entails administrative action: returning the Modification Compliance Certificate to the manufacturer as evidence of compliance.

• Install TU250 on at least one engine per helicopter. Requirement 2 requires that "An ECU Selector-Comparator board incorporating Turbomeca modification TU250 must be installed on at least one engine of each helicopter." This creates a minimum per‑aircraft installation requirement to be met by the date specified.

• Meet the stated compliance windows. The AD fixes dates: Requirement 1 must be completed "not later than 30 November 2009"; Requirement 2 is to be completed "after 30 November 2008." The Amendment itself "becomes effective on 20 June 2008." The AD thus imposes a staged duty schedule and sets a final deadline for complete compliance.

Permissive allowances (rights)

• Transitional mixed installation. Note 2 grants a temporary allowance: "A post‑TU250 ECU and a pre‑TU250 ECU can be installed in the same helicopter until 30 November 2009." This permits operators to defer full dual‑engine modification up to the stated date, provided that at least one engine has the TU250 board after 30 November 2008.

• Use of later EASA‑approved Service Bulletin revisions. The AD allows "later revision[s] approved by the European Aviation Safety Agency (EASA)" of the referenced Turbomeca Mandatory Service Bulletin, subject to EASA approval. That provides procedural flexibility if Turbomeca issues an updated bulletin and EASA approves it.

Duties implied by the AD text

• Identify applicability. Operators must determine quickly whether their helicopters fall within the AD's scope, i.e., have Makila 1A or 1A1 engines, and whether they operate as civil helicopters (the Amendment limits the applicability to civil helicopters). The AD’s Note 1 signals that the engines are installed in certain Eurocopter models but are not limited to them, so duty holders must check engine type rather than rely solely on airframe model.

• Interface with manufacturer and regulator. Compliance requires coordinating with Turbomeca for parts and compliance certificates and compliance with EASA‑approved procedures when revising the SB. The AD thus imposes an administrative duty across parties.

No statements of rights to alternative means of compliance, exemptions, or appeals are contained in the AD text. The AD does not specify enforcement mechanisms or penalties for non‑compliance within its text.

The AD text itself does not set out specific penalties, fines, or enforcement procedures. It is an instrument issued by the Civil Aviation Safety Authority delegate and carries prescriptive compliance deadlines and technical obligations, but the document does not include a sanctions schedule, civil penalties, criminal offences, or explicit enforcement steps in its own language.

What the AD does include relevant to enforcement

• Effective dates and compliance deadlines. The AD "becomes effective on 20 June 2008" and sets deadlines for the Requirements: Requirement 1 "Not later than 30 November 2009" and Requirement 2 "After 30 November 2008." These fixed dates function as enforceable time limits for compliance under the instrument.

• Signature by CASA delegate. The AD is signed by "James Coyne, Delegate of the Civil Aviation Safety Authority" (13 June 2008). This identifies the issuing authority and gives the AD formal regulatory provenance.

What the text does not contain

• No penalties described. The document does not describe the consequences of failing to comply in terms of fines, suspensions, grounding notices, or other administrative actions.

• No enforcement process described. The AD does not set out how CASA will monitor compliance, what evidence is satisfactory beyond the required Modification Compliance Certificate to Turbomeca, whether CASA will audit operator or maintenance records, or whether non‑compliance will result in further regulatory action.

Implications from the presence and absence of enforcement language

• The AD’s obligations are framed as mandatory airworthiness directives with explicit compliance dates and a requirement to follow a specified Service Bulletin and return a Modification Compliance Certificate. Enforcement is therefore implied: the AD imposes a legal duty within CASA’s regulatory remit. However, because the AD text does not specify enforcement procedures or penalties, practitioners seeking to understand enforcement should not rely solely on this AD text. They will need to consult CASA’s broader regulatory framework, enforcement policy, and any relevant Civil Aviation Regulations or administrative practice for how CASA enforces airworthiness directives and how non‑compliance is handled.

• The requirement to return a Modification Compliance Certificate to Turbomeca creates a manufacturer record that can be used by regulators, insurers, and purchasers to evidence compliance. This administrative step may function de facto as part of the enforcement infrastructure, since absence of such certificates will make it straightforward to identify non‑compliant aircraft.

Recommended practical steps for compliance monitoring (grounded in the AD, not prescriptive of CASA practice)

• Maintain documentary evidence of the Service Bulletin work and the returned Modification Compliance Certificate to Turbomeca as primary evidentiary material that demonstrates compliance with the AD.

• Monitor EASA approvals of later Service Bulletin revisions if electing to use a later revision, since the AD requires EASA approval for later revisions to be acceptable.

In sum, the AD imposes mandatory technical and administrative duties with specific deadlines, but the document itself does not set out enforcement or penalty mechanisms; those are likely governed by CASA’s broader regulatory instruments and practices which are not reproduced in the AD text.

The AD expressly cross‑references one external regulatory instrument and incorporates a manufacturer Service Bulletin by reference; it also places conditions on the acceptability of later revisions through EASA. The AD therefore operates in an interlocking regulatory and technical network.

Explicit cross-references in the AD

• EASA AD 2007‑0144R1. The AD states "Note 3: EASA AD 2007-0144R1 refers." This indicates that there is an EASA regulatory action of related content and that the Australian AD acknowledges it as relevant. The AD also makes EASA the approving authority for later revisions of the Turbomeca Service Bulletin: later Service Bulletin revisions are acceptable only when "approved by the European Aviation Safety Agency (EASA)." Thus the AD does not operate alone; it leans on EASA for approval of technical revisions and aligns itself with an EASA AD.

• Turbomeca Mandatory Service Bulletin 298 73 0250 dated 23 March 2007 (or later EASA‑approved revision). The AD requires compliance with a Turbomeca Service Bulletin and, by doing so, incorporates procedural steps and technical instructions from a manufacturer document into the regulatory obligation. That Service Bulletin is therefore a functional part of the regulatory rule, and later revisions are acceptable only with EASA approval.

Implications for regulatory interplay

• Delegation of technical detail to manufacturer bulletin. The AD delegates technical specification to the Turbomeca Service Bulletin. This is a common regulatory pattern where the regulator mandates compliance to a manufacturer‑developed fix and binds operators to the Service Bulletin's technical and documentation requirements. Practically, this means that the Service Bulletin's contents , including parts lists, installation procedure, testing and inspection steps, and certification forms , become the operative compliance requirements.

• Reliance on EASA for revision approval and cross‑jurisdictional alignment. By requiring EASA approval for later Service Bulletin revisions and referencing an EASA AD, the Australian Directive aligns its technical standard with EASA's determinations. Operators and maintainers must therefore monitor EASA decisions and approvals to ensure that any later bulletin revisions used for compliance are acceptable for this AD.

• Interface with airworthiness regimes and operator obligations. Although the AD itself is limited to an aviation technical requirement, its compliance obligations will intersect with operators' continuing airworthiness responsibilities, maintenance organisation approvals, and maintenance release procedures. For example, installation of the TU250 board will be recorded in aircraft/engine logbooks and maintenance records; returning the Modification Compliance Certificate to Turbomeca is an additional manufacturer‑level record. The AD does not reference specific Civil Aviation Regulations or maintenance release authorities, but these operational interfaces will be present in practice.

• Applicability limited to civil helicopters. The Amendment "limits the applicability to civil helicopters" and therefore removes military or other non‑civil operators from the AD’s required scope. Practitioners should note the demarcation: the AD engages the civil aviation legal regime specifically.

What the AD does not reference

• The AD does not reference Australian Civil Aviation Regulations, Civil Aviation Orders, or CASA enforcement policies within its text. It does not identify how compliance with the AD affects operating certificates, airworthiness certificates, or pilot/crew obligations. Those interfaces exist in the broader regulatory environment but are not stated in the AD document.

• The AD does not specify alternative methods of compliance (AMOCs) or provide an administrative process for seeking permission to use an alternative mitigation. It does permit later EASA‑approved revisions of the Service Bulletin, which functions as a limited pathway for alternative technical processes, but it does not set out the process for any other alternative compliance measures.

Practical takeaway: The Directive operates by cross‑reference to a manufacturer Service Bulletin and to EASA approvals and an EASA AD. Operators and maintainers must reconcile the AD's requirements with existing maintenance release procedures, recordkeeping, and any other civil aviation regulatory obligations applicable to their operations, while noting that the AD itself limits its scope to civil helicopters and does not set out enforcement mechanics or AMOC processes.

The AD document itself contains a short amendment history and references to earlier action. The record in the AD provides the following timeline and status points.

• Original Directive. The AD notes: "The original issue of this Directive became effective on 5 July 2007." The AD describes the original issue as having "required a hardware modification to the ECU that allows recovery from the 65% backup mode if the loss of N2 speed signals is determined to be temporary" and specifies that the modification applies to the Selector‑Comparator board in the ECU. The original Directive therefore issued in 2007 and imposed the substantive technical fix (TU250) at that time.

• Amendment Amdt 1. The present document is titled "AD/MAKILA/9 Amdt 1" and displays the annotation "8/2008 DM." The AD states "This Amendment becomes effective on 20 June 2008" and is signed and dated 13 June 2008 by a CASA delegate. The Amendment "limits the applicability to civil helicopters and continues the requirement for ECU Selector‑Comparator board to be modified, extending the compliance until 30 November 2009 for both engines." It also "requires that at least one engine of each helicopter has a modified ECU Selector-Comparator board installed after 30 November 2008."

• Staged compliance and extension. The Amendment extends the compliance window to 30 November 2009 for replacement of the Selector‑Comparator boards on both engines. It also imposes an intermediate requirement that at least one engine per helicopter must have the TU250 modification installed after 30 November 2008. Note 2 in the document allows a mixed installation of post‑TU250 and pre‑TU250 ECUs in the same helicopter until 30 November 2009.

• Cross‑jurisdictional reference. The Amendment includes "Note 3: EASA AD 2007-0144R1 refers," indicating a contemporaneous or prior EASA directive of relevance and suggesting harmonisation with EASA action.

• Procedure reference. From the outset the Directive has tied compliance to a manufacturer Service Bulletin: Turbomeca Mandatory Service Bulletin 298 73 0250 dated 23 March 2007. The Amendment continues this linkage and allows later revisions provided they are approved by EASA.

The document does not include any other numbered amendments, historical notes about prior amendments beyond the original issue and this Amendment, or references to earlier AD numbers except the title AD/MAKILA/9 and the EASA AD reference. There is no schedule of prior revisions, and the Amendment does not indicate whether other national authorities have issued parallel directives beyond the EASA reference.

Administrative dates recorded

• 23 March 2007: date of the Turbomeca Mandatory Service Bulletin 298 73 0250 that the AD mandates as the method of compliance, as cited in the AD.

• 5 July 2007: effective date of the original issue of the Directive.

• 13 June 2008: signature date , "James Coyne, Delegate of the Civil Aviation Safety Authority."

• 20 June 2008: effective date of this Amendment (AD/MAKILA/9 Amdt 1).

• 30 November 2008: date after which each helicopter must have at least one engine fitted with TU250 (Requirement 2 timeframe).

• 30 November 2009: final deadline "not later than" which the replacement of Selector‑Comparator boards with TU250 must be completed (Requirement 1 timeframe), and the date until which mixed installations are permitted.

The Amendment history in the AD is narrowly specified and focused on the change in applicability (civil helicopters), extension of compliance deadlines, and imposition of an intermediate per‑aircraft minimum installation requirement. The AD does not annex an explicit log of amendments or provide a consolidated text showing what changed line by line; it instead summarises the change in the Background and in the compliance/requirement fields.

The AD document contains no litigation history, judicial decisions, or references to litigation associated with the Directive. It names no cases, does not refer to court challenges, and records no legal proceedings. The AD is an administrative regulatory instrument issued by the Civil Aviation Safety Authority delegate and contains technical, procedural, and timing requirements, but it does not report any disputes, enforcement actions, or litigation outcomes.

What the absence of litigation references implies in the context of this AD

• The AD does not document any legal challenges or court proceedings in respect of the directive or the underlying technical measure. The text records only background technical events (unexplained activations of the backup mode and an investigation) and states the regulatory response in terms of a mandated hardware modification.

• Practitioners seeking litigation history must look beyond this instrument. If any judicial or administrative proceedings arise in relation to compliance, enforcement, or the AD’s validity, those would not be recorded in the AD text itself. The AD therefore provides no material evidence of contested legal interpretation, enforcement litigation, or precedent.

• No named cases. The developer instruction prohibits inventing case law. The AD contains no cases. Users requiring litigation history must consult external databases or regulatory enforcement records outside the AD document.

Practical note for researchers and practitioners

• The AD’s absence of litigation references is not an affirmative statement about whether enforcement or litigation may have occurred elsewhere. It simply means the AD text does not include, or purport to summarise, any legal challenges. For a full picture of any litigation, enforcement actions, or disputes, one must consult CASA enforcement records, court databases, or industry advisories , none of which are included in the AD text.

This AD contains several technical, procedural and timing features that can catch operators and maintenance organisations if overlooked. The following points are grounded directly in the AD’s wording and notes.

Mixed equipment allowance is time‑limited. Note 2 states: "A post‑TU250 ECU and a pre‑TU250 ECU can be installed in the same helicopter until 30 November 2009." The allowance to mix modified and unmodified ECUs within a single helicopter is explicitly temporary. After 30 November 2009, operators cannot rely on a mixed installation to satisfy the AD; the AD’s Requirement 1 sets a hard completion date for the specified replacement action "not later than 30 November 2009." Relying on the temporary mixing allowance beyond the stated date would not be consistent with the AD.

Different deadlines for different obligations. The AD sets two distinct temporal obligations: Requirement 2 (at least one engine fitted with TU250) is to be implemented "after 30 November 2008" while Requirement 1 (replace Selector‑Comparator board with TU250 and return the Modification Compliance Certificate) must be completed "not later than 30 November 2009." Practitioners must track both dates; confusing the two or treating them as interchangeable could lead to non‑compliance.

Method of compliance is prescribed and regulator‑tied. Requirement 1 mandates that replacement and the return of the Modification Compliance Certificate be "performed in accordance with Turbomeca Mandatory Service Bulletin 298 73 0250 dated 23 March 2007 or later revision approved by the European Aviation Safety Agency (EASA)." Using a later Service Bulletin revision is acceptable only if EASA approves it. Operators who adopt an updated Turbomeca procedure without verifying EASA approval would not meet the AD’s condition.

Administrative return to manufacturer is mandatory. The AD requires the "return of the Modification Compliance Certificate to Turbomeca." Failure to return that certificate may leave the operator without the manufacturer‑facing evidence of compliance required under the AD. The AD does not spell out whether CASA will accept other documentary proofs in lieu of the Turbomeca certificate; consequently, operators should ensure the required certificate is completed and returned to Turbomeca per the Service Bulletin.

Applicability narrowed to civil helicopters. The Amendment "limits the applicability to civil helicopters." If an operator has mixed civil and non‑civil registrations or operating statuses for similar airframes or engines, the AD’s applicability must be checked carefully. For example, engines installed on non‑civil aircraft would fall outside this Amendment’s scope as stated; assuming universal applicability across all registries would be an error.

Broad statement of engine installation. Note 1 states that Makila 1A and 1A1 engines are "known to be installed in, but not limited to, Eurocopter AS 332 C, C1, L and L1 helicopters." The "not limited to" language means that the AD’s applicability rests on engine model rather than airframe model list; practitioners should check engine serial numbers and model data rather than rely solely on the list of airframes.

Underlying failure mechanism only postulated. The background states that recent activations "remain unexplained despite detailed investigation" and that it is "postulated" the cause may be corruption of N2 signals by short perturbations such as EMI. The AD therefore addresses a risk that, per the document, is plausible but not substantiated. Consequently, operators should not interpret the AD as asserting an established causal chain; it is a regulatory precaution aimed at preventing a hazardous condition arising from the described symptom.

No enforcement specifics in the AD. The AD does not list penalties or describe CASA enforcement actions. Assuming the AD self‑contained the full enforcement regime would be a mistake; practitioners must consult CASA’s wider enforcement framework for details about sanctions or oversight procedures.

EASA linkage for later revisions. The Acceptability of later Service Bulletin revisions is conditional on EASA approval. Practitioners outside of the EASA framework must be alert to the added administrative step of ensuring EASA approval before relying on a later Turbomeca revision.

Recordkeeping, maintenance scheduling and possible aircraft downtime. The AD’s requirements will necessitate parts procurement, scheduling maintenance, and completing administrative compliance. While the AD does not quantify downtime or costs, failure to plan for aircraft availability may result in practical operational disruption. The AD’s staging allows some phasing, but operators must manage the schedule to avoid exceeding the hard deadline.

In short, the main "gotchas" are the temporary mixing allowance, the two‑stage deadlines, the conditional acceptance of later Service Bulletin revisions, the mandatory return of the Modification Compliance Certificate to Turbomeca, and the Amendment’s restriction to civil helicopters. Each of these is explicitly stated in the AD text and can affect compliance planning and operations if overlooked.

The AD prescribes a clear compliance path bound to Turbomeca’s Service Bulletin and EASA approvals. The following stepwise checklist is grounded in the AD’s text and is intended as an operational reading of the Directive’s explicit requirements. It does not substitute for the Service Bulletin; rather, it organises the AD’s mandates into practical steps.

1. Confirm applicability to your aircraft/engines. The AD applies to "Makila 1A and Makila 1A1 turbo‑shaft engines." Verify engine model and serial numbers on each helicopter. Note 1 observes that these engines are "known to be installed in, but not limited to, Eurocopter AS 332 C, C1, L and L1 helicopters." Also confirm that the helicopter is a civil aircraft, since the Amendment "limits the applicability to civil helicopters."

2. Review the governing technical document. Obtain Turbomeca Mandatory Service Bulletin 298 73 0250 dated 23 March 2007. The AD requires that replacement and the return of the Modification Compliance Certificate be "performed in accordance with" that Service Bulletin or "later revision approved by the European Aviation Safety Agency (EASA)." If Turbomeca has issued a later revision, verify that EASA has approved it before using it for compliance.

3. Plan the phased compliance schedule. The AD requires two timing elements:

   • After 30 November 2008, each helicopter must have at least one engine with a Selector‑Comparator board incorporating TU250 installed (Requirement 2).
   • Not later than 30 November 2009, replace Selector‑Comparator boards as set out in Requirement 1 (Requirement 1 final deadline). Use these dates to schedule parts procurement, maintenance slots, and any required validation or testing. Note 2 permits mixed installation of post‑TU250 and pre‑TU250 ECUs in the same helicopter until 30 November 2009; plan accordingly if taking advantage of the transitional allowance.

4. Procure TU250‑incorporating Selector‑Comparator boards and authorised parts. Coordinate with Turbomeca or approved suppliers to source the TU250‑modified board and any ancillary parts or special tools identified in the Service Bulletin. Ensure parts are genuine and that installation will be carried out per the Service Bulletin instructions.

5. Execute the replacement per the Service Bulletin. Carry out the hardware change and any required bench testing, rigging, calibration, or functional checks exactly as specified in Turbomeca Mandatory Service Bulletin 298 73 0250 (or EASA‑approved later revision). The AD makes compliance conditional on performing the work in accordance with the Service Bulletin.

6. Complete required certification paperwork. The AD requires "return of the Modification Compliance Certificate to Turbomeca." Ensure that the Maintenance Organisation fills out the Modification Compliance Certificate form exactly as required, obtains any necessary signatures, and returns the certificate to Turbomeca promptly. Retain copies in the aircraft maintenance records and engine logbooks as evidence of compliance.

7. Maintain records and logbook entries. Record the part replacement, Service Bulletin reference and revision, serial numbers of replaced and installed Selector‑Comparator boards, and the date the Modification Compliance Certificate was returned to Turbomeca. These records serve as primary evidence for auditors, insurers, purchasers and regulators.

8. Monitor EASA approvals and EASA AD references. Since the AD references EASA AD 2007‑0144R1 and conditions later Service Bulletin revisions on EASA approval, maintain awareness of EASA communications and approvals that may affect the permitted methods of compliance.

9. Coordinate with operators’ safety/continuing airworthiness processes. Integrate the TU250 modification into the operator’s continuing airworthiness programme. Update maintenance programmes, scheduling, reliability monitoring and any emergency procedures that may be influenced by changes to the ECU behaviour.

10. Verify completion against AD deadlines. Ensure Requirement 2 (one engine per helicopter fitted with TU250) is met after 30 November 2008 and that the full replacement and return of the Modification Compliance Certificate (Requirement 1) are completed no later than 30 November 2009. Confirm that any mixed installations do not persist beyond 30 November 2009.

11. If uncertain, seek clarification from CASA or Turbomeca. The AD does not set out enforcement mechanisms or alternatives. If there is uncertainty about the acceptability of particular procedures, whether a given Service Bulletin revision is EASA‑approved, or about recordkeeping requirements, consult the Civil Aviation Safety Authority or Turbomeca for authoritative guidance.

Notes and cautions grounded in the AD

• Use only EASA‑approved later revisions of the Service Bulletin where applicable. The AD conditions later revisions on EASA approval.

• Ensure the Modification Compliance Certificate is properly completed and returned to Turbomeca. The AD requires that the replacement be done "and return of the Modification Compliance Certificate to Turbomeca." Failing to submit the certificate could leave a compliance gap.

• Be mindful of the civil‑only limitation. The Amendment "limits the applicability to civil helicopters." Military or other non‑civil operators should not assume this AD applies to their operations as written.

• Schedule to avoid exceeding the 30 November 2009 deadline for full compliance. Although the AD provides a transition window, the final date is binding in the AD text.

Following these steps will address the explicit obligations in the AD text. The Turbomeca Service Bulletin contains the detailed technical procedures and documentation forms the AD requires; compliance rests on performing the work in accordance with that Service Bulletin and returning the Modification Compliance Certificate to Turbomeca by the stated deadlines.