AD/CFE 738/1 - High Pressure Rotor Components

The AD deploys three core regulatory concepts: applicability, prescriptive life limits, and mandatory compliance timing. Applicability is narrowly framed to a single engine model, the CFE738-1-1B: the AD begins with "Applicability: CFE Company Model CFE738-1-1B turbofan engines" and adds a note that these engines are installed on, but not limited to, Dassault Falcon 2000 series aircraft (Applicability; Note 1). This establishes the population of machines and operators to whom the rule speaks.

Prescriptive life limits are the central substantive element. The AD lists specific part numbers and assigns each a new cyclic life limit in cycles since new (CSN). The form of prescription is non-probabilistic and hard-edged: an absolute numeric CSN threshold (for example 6,700 CSN for P/N 6079T74P08). The AD requires removal "prior to exceeding" the stated CSN and replacement with "serviceable parts" (Requirement 1). The directive thereby converts a technical reassessment of service life into a clear operational constraint that suppliers, maintenance organisations, and operators must observe.

Timing and legal effect are explicit: the AD gives an effective date, "This Airworthiness Directive becomes effective on 16 March 2006." The background provides the causal trigger: "a reduction in the calculated service life of certain compressor rotor rotating parts to values below currently approved service lives" and a risk statement that failure could be uncontained and damage the aeroplane. The AD also links to an external regulatory instrument by reference, stating "FAA AD 2000-23-12 Amdt 39-11982 refers" (Note 2). That indicates cross-referencing to another regulator's prior action.

Operational compliance is framed in the ordinary maintenance vocabulary: removal from service, replacement with serviceable parts, and monitoring of cycles since new. The directive does not itself define "serviceable parts" or supply a procedure for counting cycles in this text; it assumes existing maintenance tracking and parts standards will be used to implement the removal/replacement action.

Finally, the AD is issued under the authority of the Civil Aviation Safety Authority, evidenced by the signature block: "James Coyne, Delegate of the Civil Aviation Safety Authority" and dated 1 February 2006. The document therefore functions as a binding technical requirement introduced by the airworthiness regulator and tied to aviation safety objectives stated in the background section.

The AD explicitly affects owners and operators of CFE Company Model CFE738-1-1B turbofan engines, which the AD notes are installed on, but not limited to, Dassault Falcon 2000 series aeroplanes (Applicability; Note 1). That group includes commercial operators, corporate operators, aircraft maintenance organisations that carry out engine maintenance, parts suppliers, and any third party that maintains cycle records for affected engines.

Maintenance organisations are affected because the AD requires removal and replacement of specified parts when they approach or reach the listed CSN thresholds. That obligation will require shops to schedule checks, perform removals, and certify the replacement parts as serviceable in accordance with their usual maintenance standards. The AD uses the maintenance mandate "remove from service ... and replace with serviceable parts" (Requirement 1), which places material and labour tasks squarely on the maintenance chain.

Parts suppliers and inventories are affected because the AD introduces demand for serviceable replacement parts of the specified P/Ns. Operators reaching the listed CSN limits will need replacement components that meet serviceability criteria. The AD does not specify supply arrangements, prices, or approved alternative parts; suppliers will respond to the resulting procurement demand within market constraints.

Aircraft owners are affected through scheduling and availability of their airframes. Where the engines are installed on aeroplanes such as the Falcon 2000 series (Note 1), the AD's life limits on HPC rotor components can force out-of-service periods to carry out replacements, and may affect fleet availability and dispatch reliability.

Regulators and inspectors are indirectly affected; the AD becomes an enforcement reference (it "becomes effective on 16 March 2006") and can be used in oversight and surveillance. The AD also references FAA AD 2000-23-12 Amdt 39-11982 (Note 2), so international operators or maintenance organisations that follow both jurisdictions must reconcile scheduling, record-keeping, and compliance across both instruments.

The AD does not identify exemptions, credits, or compensatory measures. It also does not specify who bears the financial cost. The text requires removal and replacement and sets deadlines by CSN, but it does not allocate costs between manufacturers, operators, or insurers. The AD likewise does not define dispute or appeal mechanisms in the text provided.

Duties:

• Remove specified components before they exceed the new CSN limits. The AD's operative instruction is to "remove from service certain stage 4 and 5 blisks and impeller aft shafts prior to exceeding the new cyclic life limits as follows, and replace with serviceable parts" (Requirement 1). The duty is expressed as a firm preventative action tied to specific numerical thresholds.
• Replace removed components with serviceable parts. The AD pairs the removal duty with an explicit replacement obligation: removed items must be substituted by parts meeting serviceability standards (Requirement 1).

The AD sets precise numeric thresholds for when the duty arises. The parts, part numbers and CSN limits are listed in the AD's table and repeated under Requirement 1. These numeric triggers define the compliance point for each individual component instance.

Rights and definitional limits in the text:

• The AD identifies applicability narrowly to the CFE738-1-1B model. That limits the duty-bearing population; engines of other models are not listed in this directive (Applicability).
• The AD does not define "serviceable parts" within the text. That term typically has an industry meaning, but the AD text itself leaves the operational definition to existing maintenance and airworthiness practice. Consequently, implementers must rely on their established procedures, certification standards, and approved parts lists to satisfy the replacement obligation.

Operationally implied duties:

• Monitoring and record-keeping duties follow from the requirement to act "prior to exceeding" CSN limits. Operators must track cycles since new for the specified parts to know when they approach the thresholds. The AD does not provide a counting method but the duty implies that reliable CSN records are necessary to comply.

Absences in the text that shape duties and rights:

• The AD does not set out a process to obtain alternative compliance or to apply for a deviation. It provides no text on exemptions, approved life-extension procedures, or on credits for parts already inspected or modified. It also does not articulate procedures for marking or segregating parts removed for exceeding the CSN limit.
• The AD does not allocate costs, nor does it specify administrative steps such as notifying CASA on completion, submitting compliance reports, or records retention standards as part of the directive text provided.

In sum, the principal duty is technical and time-bound: remove the enumerated parts from service before the stated CSN and replace them with serviceable parts. Rights and procedural specifications beyond that core are not articulated in the AD text supplied.

The AD text supplies a clear effective date and compliance requirement, but it does not itself state any criminal, civil or administrative penalties, nor does it set out enforcement procedures in the document provided. The AD states "This Airworthiness Directive becomes effective on 16 March 2006" and specifies the required actions and part limits (Compliance; Requirement 1). The text does not include language in this extract about sanctions for non-compliance, reporting obligations to the regulator on completion of work, or the inspection protocol that a regulator would follow to verify compliance.

Because the AD explicitly prescribes safety-critical maintenance actions and an effective date, it functions in practice as a regulatory requirement that relevant regulators and oversight bodies may enforce. However, the AD as supplied stops short of spelling out enforcement mechanisms or penalty scales. The document does not, for example, mention suspension of certificates, fines, or the administrative steps that CASA would take to verify and enforce compliance. The signature block identifies the issuer: "James Coyne, Delegate of the Civil Aviation Safety Authority" (1 February 2006), which signals the issuing authority but contains no enforcement text.

The absence of stated penalties in this extract has concrete implications. Operators and maintenance organisations must treat the AD as a mandatory safety requirement because it prescribes actions and an effective date, but they will need to consult CASA's wider regulatory framework, licence and certification rules, and enforcement policies to understand the consequences of non-compliance and the mechanics of oversight. The AD does not, within its own text, instruct operators to report compliance status or provide a compliance form; consequently, compliance monitoring will rely on the regulator's usual surveillance and audit mechanisms, which are not reproduced here.

The AD references FAA AD 2000-23-12 Amdt 39-11982 (Note 2). That cross-reference may be relevant to international enforcement or to harmonised compliance records for operators that must satisfy multiple jurisdictions, but the AD itself does not translate that reference into specific enforcement consequences in Australia. Parties seeking to understand penalties, enforcement steps, or remedial options must therefore look beyond this AD text to the broader statutory and regulatory instruments administered by CASA and to any procedural guidance CASA issues in relation to AD compliance and enforcement.

The AD explicitly cross-references a foreign regulator's instrument, stating "FAA AD 2000-23-12 Amdt 39-11982 refers" (Note 2). That reference indicates that the CASA directive aligns or is informed by a prior FAA airworthiness directive addressing related HPC rotor component life limits. The AD does not reproduce the FAA AD's content, nor does it explain legal primacy; it simply cites the FAA instrument as relevant. This creates an operational interface where operators and maintenance organisations that operate across jurisdictions or use FAA-derived procedures may need to reconcile CASA's requirements with FAA guidance.

The AD is an instrument issued by the Civil Aviation Safety Authority, signed by its delegate (James Coyne). As supplied, the AD does not reproduce the statutory delegation or the enabling Act, and it does not identify subordinate regulations that provide penalties or enforcement mechanisms. Therefore the AD should be read within the broader statutory matrix that authorises CASA to issue airworthiness directives and to supervise compliance. Those authorising texts and enforcement provisions are not included in this AD extract, so the AD does not itself set out how it nests into the broader legal framework.

Operational compatibility concerns arise because the AD prescribes new service life limits that are "below currently approved service lives" according to the background. That suggests the AD amends previously accepted or approved maintenance/service life arrangements for affected parts. Where prior approvals, type certificates, maintenance programmes or manuals listed different life limits, operators will need to treat this AD's limits as the operative constraints for the parts and reconcile maintenance manuals, continuing airworthiness management documents, and type-specific maintenance programme entries. The AD text itself does not provide transitional instructions for reconciling conflicting prior approvals or for record-keeping retrofits.

The AD's narrow applicability to the CFE738-1-1B engine model means its interaction with other laws or directives will be limited to those instruments that govern the same engines or the airframes on which they are installed. The AD notes installation on Dassault Falcon 2000 series aeroplanes but does not purport to amend or displace any airframe-specific airworthiness requirements; it focuses on engine components. Accordingly, it interacts with other laws and rules at the operational layer: maintenance scheduling, release-to-service certification, and any cross-jurisdictional certification that depends on component life limits. Operators that must satisfy multiple regulators should treat the AD's reference to the FAA AD as an indicator to check consistency across jurisdictions.

Finally, the AD does not state any coordination mechanism or precedence rule between different airworthiness directives. It neither grants equivalence for alternative compliance methods nor refers to a process for approving modifications that would alter the life limits listed. Those interactions therefore require consultation of CASA's broader administrative and regulatory provisions, as they are not specified in the AD text itself.

The document supplied is an amendment styled "AD/CFE 738/1" dated 1 February 2006 and effective 16 March 2006. The AD header includes repeated elements "AD/CFE 738/1", "High Pressure Rotor Components", and "3/2006", indicating the chronology and identifier assigned to this particular directive. The AD states in its background that "This amendment is prompted by a reduction in the calculated service life of certain compressor rotor rotating parts to values below currently approved service lives." That language frames the AD as an amendment to existing approved service life parameters rather than as an initial life-limit-setting action.

The AD makes an explicit reference to FAA AD 2000-23-12 Amdt 39-11982 (Note 2), which signals a prior foreign regulatory action on related parts. The supplied text does not include a chronology of earlier CASA ADs for the same parts or models, nor does it include any prior Australian AD numbers that this instrument supersedes. The only amendment-specific language contained in the supplied extract is the phrase "This amendment is prompted by..." in the background paragraph, which explains the technical trigger for changing the limits.

There is no conditional language about transitional provisions or grandfathering of parts already beyond certain cycles: instead the AD prescribes removal "prior to exceeding the new cyclic life limits" (Requirement 1). Because the AD does not include an explicit retrospective grace period or credits, the effective date is the operative reset point for enforcement logic.

The AD's formal metadata in the header , the AD number, title "High Pressure Rotor Components", and the date code "3/2006" , indicate its place within the regulator's indexing system for ADs. The signature block records James Coyne as the CASA delegate issuing the directive on 1 February 2006. The effective date given is 16 March 2006. No subsequent amendments, revocations, or updates appear in the supplied text; the document itself is the amendment action described in the background sentence.

If a reader requires a complete amendment history for the engine model or for the affected part numbers, the supplied extract does not provide it. The AD's reference to the FAA AD provides a pointer to at least one related prior action, but the AD does not catalogue prior Australian ADs or subsequent corrective amendments. For historical sequencing, stakeholders must consult CASA's AD registry and any FAA or other foreign regulator records for the full set of predecessor or successor instruments.

The AD provided contains no litigation history, references to judicial decisions, or mention of disputes or appeals. The text is a technical directive that sets life limits and an effective date; it does not record any court challenges or administrative appeals. The only named instruments are this AD itself and the reference to FAA AD 2000-23-12 Amdt 39-11982 (Note 2). The signature block names "James Coyne, Delegate of the Civil Aviation Safety Authority" but there is no indication within the supplied text of any legal proceedings that led to the AD or that have followed it.

Given the absence of litigation material in the AD, any information about subsequent legal challenges, judicial interpretation, or administrative review would need to be sought from external records: court databases, administrative tribunal records, regulatory enforcement files, or CASA's public records. The AD text provides no pointers to a legal contestation process specific to this directive.

In practice, airworthiness directives can be the subject of disputes concerning procedural fairness, the technical basis for the directive, cost allocation, or the scope of regulatory authority. None of those matters appear in the supplied AD text. The AD itself presents a technical justification in the background ("a reduction in the calculated service life ...") and identifies the safety risk to be addressed ("prevent failure ... which could result in an uncontained engine failure and damage to the aeroplane"), but it does not set out procedural steps that would indicate prior adjudication or a contested rulemaking record.

Therefore, as far as the supplied material shows, there is no litigation history to report. Any party needing to know whether the AD was litigated, appealed, or otherwise legally contested would need to examine external legal archives or CASA administrative records, because the AD itself is silent on that subject.

1. Narrow applicability but broad operational footprint. The AD applies specifically to "CFE Company Model CFE738-1-1B turbofan engines" yet notes those engines are installed on, but not limited to, Dassault Falcon 2000 series aeroplanes (Applicability; Note 1). Operators who do not fly Falcon 2000s but who operate other airframes with the CFE738-1-1B must still observe the AD. Failure to check engine serialisation and installation records could lead to missed compliance.

2. Numeric thresholds are part-specific and non-uniform. The CSN limits vary by part number; for example P/N 6079T80P05 is limited to 2,160 CSN whereas P/N 6079T80P06 and P/N 6079T80P07 are limited to 7,100 CSN. Misidentifying the exact part number during inventory or maintenance could cause premature removal or, conversely, inadvertent overrun. The AD gives precise P/N-CSN pairings that must be matched to the installed part.

3. The AD requires action "prior to exceeding" CSN limits but does not detail counting methodology. Operators must be able to demonstrate cycles since new for each affected component. The AD text does not prescribe how to calculate or reconcile cycles where engines have changed platforms, undergone component exchanges, or had cycles logged inconsistently. The AD's silence on counting methodology can complicate borderline cases where accumulated cycles are disputed or records are incomplete.

4. "Serviceable parts" are required but not defined in the AD. The replacement obligation is to fit "serviceable parts" but the AD does not state whether overhauled components with documented restoration to serviceability are acceptable, or whether only new OEM parts qualify. Operators must rely on existing maintenance standards, type certificates, and approvals to interpret "serviceable." The lack of explicit definition can lead to enforcement uncertainty.

5. No transitional or grandfathering language is provided. The AD sets new life limits "prior to exceeding the new cyclic life limits" without specifying whether any previously installed parts that have already exceeded those limits are treated differently, or whether retrospective action is required. The effective date is set, but absence of transitional relief can create immediate operational impacts for engines near the thresholds.

6. The AD references FAA AD 2000-23-12 but does not import its content. Operators who are subject to multiple regulators must examine both documents; the CASA AD does not explain whether compliance with the FAA AD alone satisfies the CASA AD. The cross-reference is informative but not explanatory.

7. No enforcement mechanism, penalties or reporting obligations in the text. The AD contains no explicit enforcement or reporting steps. That absence means operators cannot rely on the AD text alone to determine post-action reporting, inspection certificates, or the procedural consequences of non-compliance. They must consult CASA's broader enforcement and oversight rules.

8. Scope of parts listed is limited to named P/Ns. If an operator's part has a different P/N, or if a modification has re-marked a part or used an alternate part, the AD text does not indicate whether such variants are captured. Operators with modified parts must verify applicability carefully.

9. Operational cost and availability risk. The AD creates a demand for replacement "serviceable parts" but does not address supply. For rare components, lead times or procurement constraints could cause extended downtime, a point not addressed in the AD.

10. Record-keeping and certification implications are implied, not expressed. The AD's intervention requires precise life-count tracking and maintenance documentation, yet the AD does not prescribe documentation formats or retention periods. This creates administrative risk during audits and surveillance.

Each of these "gotchas" arises from what the AD requires and from what the AD leaves unspecified. Operators must therefore combine the AD's prescriptions with their own maintenance procedures and with CASA's general regulatory framework to translate the AD into an auditable compliance programme.

Core compliance steps drawn directly from the AD:

1. Identify affected engines. Confirm whether the engine model is CFE Company Model CFE738-1-1B, the only model named in the AD's Applicability section. Also verify airframe installations; the AD notes Falcon 2000 series as an example (Applicability; Note 1).

2. Inventory and part identification. For each affected engine, locate and positively identify the installed stage 4 and 5 blisks and impeller aft shafts by part number. The AD lists the relevant part numbers: 6079T74P08 (stage 4 and 5 blisk), and impeller aft shaft numbers 6079T80P04, 6079T80P05, 6079T80P06, 6079T80P07. Accurate P/N matching is essential because CSN thresholds differ by P/N.

3. Establish CSN for each listed part. The AD triggers the removal obligation "prior to exceeding" the stated CSN. Operators must therefore compile cycles since new records for each listed part to determine current CSN and to plan replacements before the limits are reached.

4. Schedule removal before thresholds are reached. Based on CSN, schedule maintenance windows to remove listed parts before they exceed the listed CSN: e.g., remove P/N 6079T74P08 before 6,700 CSN; remove P/N 6079T80P05 before 2,160 CSN; and so on. The AD requires replacement with "serviceable parts," so plan for both removal and replacement during the work scope.

5. Procure serviceable replacement parts. The AD requires that removed parts be "replace[d] with serviceable parts" (Requirement 1). Determine whether acceptable replacements are new OEM parts, overhauled parts approved to the operator's standards, or other approved items. Because the AD text does not define "serviceable," use the operator's approved maintenance organisation procedures or approved parts lists to ensure replacements meet airworthiness criteria.

6. Maintain documentary evidence. Keep maintenance records that show part identification, CSN at removal, dates of removal and replacement, and certification that replacements were "serviceable." Although the AD does not state reporting obligations, such records will be the primary proof of compliance during regulatory inspections.

7. Reconcile with existing maintenance programmes and manuals. Update relevant maintenance planning documents, life-limited parts lists, and continuing airworthiness management records to reflect the new CSN limits for the specified P/Ns. Because the AD reduces previously approved service lives (background), maintenance programmes must be amended to incorporate the new thresholds.

8. Consider supply-chain lead times. The AD creates a need for replacement parts potentially on short notice as parts approach CSN limits. Factor procurement lead times into maintenance scheduling to avoid forced overruns.

9. Check cross-jurisdictional requirements. The AD references FAA AD 2000-23-12 (Note 2). If the operator is subject to multiple regulatory regimes, ensure compliance actions satisfy all applicable directives and reconcile any differences. Where doubt arises, seek regulatory guidance from CASA and, if necessary, the foreign regulator.

10. Seek further guidance from CASA where required. The AD itself provides the technical limits and replacement duty but does not define reporting formats, alternative compliance procedures, or enforcement consequences. If an operator needs clarity,for example, on acceptable definitions of "serviceable parts," record formats, or seeking alternative means of compliance,contact CASA or consult the regulator's published guidance for airworthiness directives.

Practical implementation notes anchored to the AD text:

• All actions must be completed in a timeframe that ensures parts are removed prior to exceeding the CSN thresholds given in the AD's table.
• The AD does not provide a grace period beyond the effective date or a list of approved modifications that would alter the life limits; absent such text, the safe course is to treat the AD's CSN limits as the controlling requirement for continued operation of the affected parts.
• Maintain a conservative approach to cycles counting; because the AD requires removal "prior to exceeding" the CSN, schedule replacement with margin to ensure compliance, accounting for recorder inaccuracies, transfer of engines between airframes, and any uncertainty in cycle accounting.

Following these steps translates the AD's prescriptive numeric limits and replacement mandate into an auditable maintenance plan that aligns with the AD's effective date and the stated safety objective.