AD/PW4000/13 - Fan Blade

The AD rests on a small set of concrete technical and administrative concepts drawn from the text. These are applicability, required action, method of compliance, compliance period, effective date, and the safety rationale that links a mechanical failure mode to an operational hazard.

Applicability, stated in the AD, is narrow but not strictly exclusive: it names "Pratt & Whitney (PW) PW4164 and PW4168 series turbofan engines installed on but not limited to Airbus Industrie A330 series aircraft" (Applicability). The formulation therefore identifies the principal affected engine models and recognises that those engines are commonly installed on A330s, but it leaves open the possibility that other aircraft types with those engines could fall within the scope. The AD does not list serial numbers, tail numbers, or specific airframes beyond the A330 reference, and it does not provide a definitive exclusion for engines on other airframes.

The required action is a hardware replacement, specifically the installation of "a new or a modified fan blade assembly" and the AD specifies the exact method of performing that installation by reference to PW SB No. PW4G-100-72-92 dated 24 April 1997 (Requirement). The AD thereby makes compliance conditional not merely on replacing parts but on following an identified service bulletin as to procedures, inspections, or configuration.

The compliance period is concrete and short: operators must comply "within 30 days after the effective date of this AD, unless previously accomplished" (Compliance). The effective date is explicitly stated as 24 September 2009, which fixes the outer bound of the compliance window to 24 October 2009 for operators who had not already complied prior to the effective date (Compliance; Effective date).

The safety rationale is summarised in the Background. The AD links a reported test event to an in-service risk: a fan blade, identified by part number in the Background as P/N 55A221, was intentionally released during a test, which led to a high N1 rotor imbalance and subsequent liberation of fan containment components. The AD asserts that in revenue service, fan blade failure near the root could be caused by metal fatigue, which could produce an equivalent hazard to the tested event, namely high rotor imbalance and release of the fan containment system and engine inlet cowl, creating an aircraft hazard (Background). The AD therefore treats the test outcome as a proxy for an in-service failure mode, and it prescribes replacement of the relevant fan blade assembly to remove or mitigate that failure risk.

A cross-reference is included to an FAA AD, specifically FAA AD 97-11-06 Amdt 39-10035 dated 11 June 1997, which the AD cites as relevant; the text includes the FAA AD reference as a Note under Requirement, and it identifies the Pratt & Whitney service bulletin as the procedural instrument for compliance (Requirement, Note).

Other administrative items appear in the AD text: the signature of James Coyne as Delegate of the Civil Aviation Safety Authority with a date of 12 August 2009, and a clear effective date for the AD (signature block; Effective date). There are duplicated headings and table entries in the supplied text, but they repeat the same core information.

The AD affects operators, maintainers, owners and other parties responsible for continued airworthiness of Pratt & Whitney PW4164 and PW4168 series turbofan engines. The Applicability clause identifies the affected hardware and typical aircraft installation: "Pratt & Whitney (PW) PW4164 and PW4168 series turbofan engines installed on but not limited to Airbus Industrie A330 series aircraft" (Applicability). That language focuses the directive at the engine-series level, and it therefore reaches any airframe type on which those engine models are fitted.

Who pays. The text does not specify who bears the cost of complying. The AD requires installation of a new or modified fan blade assembly in accordance with the Pratt & Whitney service bulletin (Requirement). Costs therefore fall to the economic actors who must carry out that installation, which will typically be the aircraft operator or owner, or their maintenance provider acting under contract. The AD itself does not allocate costs, provide funding, or note an exemption for certain kinds of operators.

Who decides. The AD sets the mandatory technical outcome and the method of compliance by reference to PW SB No. PW4G-100-72-92 dated 24 April 1997 (Requirement). It therefore leaves the technical details of how to meet the mandate to the content of the referenced service bulletin. The authority that issued and signed the AD is the Civil Aviation Safety Authority, represented by James Coyne as Delegate, and he certified the AD on 12 August 2009 (signature block). The AD thus imposes a binding instruction from the regulator and delegates the procedural detail to the manufacturer service bulletin.

Who must schedule work. Operators of aircraft fitted with the identified engines must schedule and perform the installation within 30 days of the effective date (Compliance). That scheduling includes availability of replacement parts, maintenance personnel authorised to perform the installation, and necessary aircraft downtime. The AD provides no exemption for aircraft in storage, nor does it state any deferred compliance allowance beyond the 30-day window, and it does not state alternative methods of compliance or requests for exemptions. The only caveat is "unless previously accomplished," which means operators who already performed the replacement before the effective date meet the requirement without further action (Compliance).

Who inspects and verifies. The AD ties the installation to Pratt & Whitney's service bulletin, which is the document that will contain instructions, acceptance criteria and likely inspection steps; the AD therefore implicitly makes the maintenance provider responsible for following and documenting the SB's procedures. The AD text itself does not specify recordkeeping, nor does it set out a verification or certification process beyond compliance with the SB. The AD does include a Note citing FAA AD 97-11-06, which may be informative to maintainers referencing parallel requirements, but the AD does not itself require consultation of that FAA AD beyond the Note (Requirement, Note).

In short, the parties affected are those who operate or maintain PW4164 and PW4168 engines; they must implement a specified hardware replacement within a short timeframe, using the manufacturer service bulletin's procedures as the compliance standard. The AD identifies the regulator as the issuer, but the AD leaves the operational execution, cost, scheduling and documentation to the contractual relationships among operators, owners and maintenance organisations.

The AD creates a single, clear mandatory duty, and it frames that duty with a reference to a manufacturer service bulletin. The primary duty is: within 30 days after the AD's effective date, install a new or modified fan blade assembly in accordance with PW SB No. PW4G-100-72-92 dated 24 April 1997, unless the action has already been accomplished before the effective date (Requirement; Compliance). The effective date fixed by the AD is 24 September 2009; therefore, the duty to complete the installation applies to the period up to 30 days thereafter, meaning up to 24 October 2009 for those who had not already complied (Compliance; Effective date).

Duties, specified elements. The AD prescribes three linked elements: (1) that a new or modified fan blade assembly be installed; (2) that the installation follows the requirements of the named Pratt & Whitney service bulletin; and (3) that the work be done within the 30-day window. The AD therefore requires not only replacement but method-specific compliance, because the SB is explicitly referenced as the procedural standard (Requirement).

Rights and procedural protections. The AD text does not specify any rights of appeal, alternative means of compliance, or processes to seek an extension or exemption. The document does not set out any administrative review path, or any form of interim relief. It does, however, include a Note referencing FAA AD 97-11-06 Amdt 39-10035 dated 11 June 1997, which may be useful for operators seeking contextual information, but the Note does not create a right or an obligation by itself (Requirement, Note).

Interaction with manufacturer guidance. By making compliance "in accordance with" a specific Pratt & Whitney service bulletin, the AD effectively requires adherence to the manufacturer's procedural and technical requirements. The AD therefore converts the SB from advisory guidance into a regulatorily binding compliance standard for the purposes of this directive. The AD does not incorporate the SB text into the AD verbatim; rather, it references the SB by number and date, thereby delegating the detailed technical steps, torque values, inspection items and acceptance standards to the SB.

Limitations in the duty. The AD applies to "PW4164 and PW4168 series turbofan engines installed on but not limited to Airbus Industrie A330 series aircraft" (Applicability). The phrasing means the duty is tied to those engine series regardless of the airframe, although the AD foregrounds the A330 as a common installation. The AD does not provide a list of serial numbers, tail numbers, or maintenance histories that would limit the duty to a subset of engines of those models.

Recordkeeping and verification duties are not articulated. The AD does not specify any logging, certification, or reporting duties connected to the installation. The AD therefore creates the substantive installation duty but it does not lay down procedural obligations on maintainers to record or report compliance in the text provided.

In short, the key duty is a time-bound hardware replacement performed according to a named service bulletin. The AD does not enumerate remedial rights, alternative compliance procedures, extensions, or reporting obligations in the supplied text.

The AD text supplied does not specify penalties, sanctions, or an enforcement regime within its own provisions. The document sets a mandatory technical requirement and an effective date, but it does not list fines, suspension mechanisms, criminal penalties, or administrative enforcement steps. The AD's signature block identifies James Coyne as Delegate of the Civil Aviation Safety Authority and shows a signing date of 12 August 2009, and the AD states an effective date of 24 September 2009; however, the AD text does not itself describe any enforcement sanctions for non-compliance (signature block; Effective date).

Because the AD does not promulgate express penalty provisions, parties reviewing the AD must rely on the AD as setting a mandatory compliance obligation but cannot find within the AD text any provision describing enforcement powers, inspection authority, compulsory reporting, or specific penalties for non-compliance. The AD also does not specify any administrative process for monitoring compliance, or a schedule of inspections by the issuer. No conditions for revocation, suspension or modification of the AD are set out.

The AD does include a Note referencing FAA AD 97-11-06 Amdt 39-10035 dated 11 June 1997, and it mandates compliance with a Pratt & Whitney service bulletin. Those cross-references do not themselves create penalties within the AD text supplied here, because the AD does not incorporate external penalty provisions by citation. The AD therefore creates a binding safety requirement, but the enforcement mechanisms and penalties, if any, are not contained within the text supplied.

The absence of specified penalties in the AD text supplied has practical implications. Operators and maintainers cannot rely on this document alone to identify enforcement consequences or enforcement processes. Any enforcement action, inspection regime, or penalty would need to be located in other regulatory instruments, contractual arrangements, or statutory provisions outside this AD. The AD itself is an instrument that sets a mandatory action and a deadline, but it does not say what follows if the action is not taken within the timeframe.

Because the AD does not set out enforcement modalities or sanctions, parties required to comply will need to consult their regulators, their oversight documents, and any relevant statutory frameworks outside of this AD to determine the consequences of non-compliance. The AD text supplied should be read as creating a duty to act, with the particulars of enforcement unspecified in the AD itself.

The AD expressly references an FAA airworthiness directive and a Pratt & Whitney service bulletin, and it binds compliance to the content of the manufacturer bulletin; beyond those two documents, the AD text contains no other express references to external laws, regulations, or statutory instruments.

First, interaction with manufacturer material. The AD requires installation "in accordance with the requirements of PW SB No. PW4G-100-72-92, dated 24 April 1997" (Requirement). That language makes the service bulletin the operative technical standard for compliance. The AD thus interacts directly with manufacturer guidance by elevating the SB's procedures to a mandatory compliance standard for the purposes of this AD. The AD does not reproduce the SB content; it incorporates the SB by reference as the required method. Any substantive provisions or acceptance criteria relevant to the replacement, which would ordinarily be in the service bulletin, become the technical basis for compliance with this AD.

Second, interaction with FAA material. The AD includes a Note that states "FAA AD 97-11-06 Amdt 39-10035 dated 11 June 1997 refers" (Requirement, Note). This Note links the AD to an earlier FAA directive addressing a related issue. The presence of that FAA AD reference suggests the AD draws on or aligns with previous regulatory determinations made by the FAA, but the supplied AD text does not describe the FAA AD's content nor does it adopt the FAA AD's procedures or penalties directly. The AD therefore creates an informational cross-reference to a relevant FAA action. The AD does not state whether compliance with the FAA AD would be sufficient or necessary for compliance with this AD; instead, it prescribes compliance with the Pratt & Whitney service bulletin.

Third, the AD does not explicitly address interplay with other Commonwealth laws, international obligations, airworthiness regulations, operator manuals, or maintenance provider obligations. The AD is an instrument that sets a required action for particular engines, and it does not on its face amend or displace other regulatory requirements. The AD does not set out whether compliance with the SB will satisfy broader airworthiness certification requirements, nor does it state that operators must amend their maintenance programmes or manuals. The AD also does not say whether the AD should be recorded as part of an approved maintenance program or whether it triggers other regulatory reporting duties.

Fourth, the AD's silence on enforcement implies that any enforcement action would have to rely on other legal or regulatory provisions outside the AD text. Because no penalties or enforcement mechanisms are included, the relationship between this AD and any enforcement or punitive statutory regime is not established within the AD itself. Parties seeking to understand the full legal effect of failing to comply should therefore look beyond this AD to statutory rules, civil aviation regulations, or administrative enforcement instruments which are not included in the supplied text.

In sum, the AD interacts directly with Pratt & Whitney's service bulletin by mandating it as the method of compliance, and it references an FAA AD as related background. The AD does not otherwise specify interactions with other laws or regulatory instruments in the supplied text.

The AD text supplies several dates and cross-references which form the document's immediate amendment and chronological context. The effective date of the AD is expressly given: "This Airworthiness Directive becomes effective on 24 September 2009" (Effective date). The AD's compliance clause requires action "within 30 days after the effective date of this AD, unless previously accomplished," which fixes the compliance window relative to that effective date (Compliance).

The AD references Pratt & Whitney Service Bulletin No. PW4G-100-72-92, described with its date: "dated 24 April 1997" (Requirement). That service bulletin date shows that the manufacturer's mitigation action predates the AD by several years. The AD also contains a Note that cites FAA AD 97-11-06 Amdt 39-10035 dated 11 June 1997 (Requirement, Note). The presence of these 1997 dates indicates prior regulatory and manufacturer activity on the subject of PW4000 series fan blade safety.

The AD itself bears a signature block showing the issuer and the date of signature: "James Coyne, Delegate of the Civil Aviation Safety Authority, 12 August 2009" (signature block). The signature date precedes the effective date by just over a month, which is consistent with an administrative lead time between signing and the AD taking legal effect (signature block; Effective date).

The AD label and table indicate its identifier and issue month: "AD/PW4000/13 Fan Blade 10/2009" and the header shows "AD/PW4000/13 | Fan Blade | 10/2009" (title/table). These entries mark the AD as the thirteenth PW4000-series fan blade AD in the numbering used by the issuer, and they place the AD in October 2009 as an identifier, but the effective date is 24 September 2009 as stated in the body text. The table and duplicated headings repeat the AD number and date information, which creates some redundancy but no substantive amendment history beyond the single documented issuance.

No amendments to the AD text are recorded within the supplied document. The AD does not include a section titled "Amendments" or list prior versions of the AD or later revisions. The AD therefore appears as a single, discrete issuance in the supplied text, effective 24 September 2009, signed 12 August 2009, and cross-referencing earlier manufacturer and FAA material from 1997.

Because no subsequent amendment history is provided in the supplied material, the AD as presented should be treated as a standalone directive with the dates and cross-references noted above. Any later amendments or withdrawals of the AD are not present in this text, and cannot be inferred from it.

The supplied AD text contains no information about litigation, disputes, judicial review, or administrative appeals related to the directive. The document does not mention any court cases, administrative proceedings, appeals, or contested enforcement actions. The only external document referenced by name is FAA AD 97-11-06 Amdt 39-10035 dated 11 June 1997, and the Pratt & Whitney service bulletin PW4G-100-72-92 dated 24 April 1997; neither of those references in the AD text is linked to litigation within the supplied material (Requirement; Note).

Because the AD text is silent on any litigation history or legal challenges, the supplied record does not evidence, record or summarise any disputes about the AD's validity, the technical basis for the action, or the regulator's decision-making process. The supplied material does include a Background section that recounts an FAA-reported test event and links it to an in-service risk from metal fatigue, but the Background contains no description of contested facts, contested expert opinions, or adjudicative review.

Absent any litigation data in the AD text, readers cannot determine from this document whether the AD has been litigated, whether parties sought review of the regulator's choice to issue the AD, or whether any judicial interpretation affects its application. The AD does not identify an administrative appeals process in its wording, nor does it document any prior or subsequent legal challenges.

For a practitioner seeking litigation history, the AD text supplied is therefore uninformative; it contains no case names, no citations to decisions, and no references to judicial or tribunal outcomes. Any inquiry into litigation or legal challenges related to this AD would need to proceed to sources outside this document, because the AD itself does not disclose or discuss litigation matters.

This AD contains several features and textual formulations that merit attention because they create potential uncertainty or operational sharp edges for affected parties.

1. Applicability phrasing is imprecise. The AD states applicability as "Pratt & Whitney (PW) PW4164 and PW4168 series turbofan engines installed on but not limited to Airbus Industrie A330 series aircraft" (Applicability). The clause names engine series and then appends a non-exhaustive airframe example, which can create ambiguity for engines of the same series installed on other airframes. Operators of non-A330 aircraft with PW4164 or PW4168 engines will need to interpret whether the AD covers their engines; the AD text itself does not include an exclusion or a list of covered airframes.

2. Compliance is tied to an external document. The AD requires installation "in accordance with the requirements of PW SB No. PW4G-100-72-92, dated 24 April 1997" (Requirement). The AD does not reproduce the SB, and it does not state whether any later revisions of the SB are acceptable. Operators must obtain the exact SB identified in the AD and ensure that the work follows its requirements. There may be practical issues where a later revision of the SB exists; the AD does not specify whether the later revision is acceptable, or whether the version dated 24 April 1997 is mandatory.

3. Short compliance window. The AD requires compliance "within 30 days after the effective date" (Compliance). With an effective date of 24 September 2009, the outer compliance deadline is 24 October 2009 for those not already compliant. A 30-day window for procuring parts, scheduling a shop visit, and conducting the replacement may be operationally challenging. The AD text provides no phased compliance or deferment mechanism.

4. No enforcement or penalty details. The AD does not describe penalties, enforcement processes, or reporting requirements. Operators cannot rely on the AD alone to determine the consequences of non-compliance or the process by which compliance will be verified. This gap requires operators to consult other regulatory materials to understand enforcement risk.

5. No recordkeeping or reporting obligations. The AD does not instruct operators to record the replacement in maintenance logs, to notify the regulator, or to file compliance reports. The absence of such procedural requirements does not mean that logbook or regulatory reporting obligations are unnecessary; it means the AD itself is silent and operators must check other obligations outside the AD.

6. Reliance on test scenario as basis for action. The Background links the AD to a fan blade out test where a specific blade P/N 55A221 was intentionally released, and attributes a potential in-service failure to metal fatigue; the AD requires replacement pre-emptively on that basis (Background). The AD does not supply test data, fatigue analyses, or quantitative risk assessments in the supplied text. Parties who seek to contest the technical basis will find the AD itself provides only a narrative linkage between the test event and the in-service risk.

7. Cross-reference to FAA AD. The AD includes a Note referencing FAA AD 97-11-06 Amdt 39-10035 dated 11 June 1997 (Requirement, Note). The AD does not explain how the FAA AD interacts operationally with this AD, nor whether compliance with the FAA AD satisfies this AD, or vice versa.

8. Part number identified in Background but not in Requirement. The Background mentions fan blade Part Number 55A221 as the blade intentionally released in the test (Background). The Requirement, however, does not explicitly identify which P/Ns must be replaced, instead requiring installation of a new or modified assembly per the service bulletin. Operators must reconcile the P/N details in the SB with the P/N mentioned in the Background to determine exact parts scope.

9. Redundancies and formatting in the supplied text. The provided document repeats headings and the AD identifier multiple times (the supplied text includes repeated lines such as "AD/PW4000/13" and repeated headings). While these repetitions do not change substance, they could complicate automated processing or indexing if systems expect a single canonical appearance.

10. No mention of alternative methods of compliance. The AD does not provide an explicit process or contact for seeking an alternative method of compliance or approval of different hardware. If an operator wishes to propose an alternative technical fix, the AD does not specify the route to seek acceptance.

Each of these points arises from the AD's own wording; operators and advisers should be alert to these potential pitfalls when planning compliance, and should consult the referenced service bulletin and any broader regulatory materials to resolve ambiguities not addressed inside the AD.

The AD prescribes a single route to compliance, and the steps below set out the concrete actions that follow from the AD text. The AD states the required action and the compliance period: install a new or modified fan blade assembly in accordance with PW SB No. PW4G-100-72-92 dated 24 April 1997, within 30 days after the effective date of the AD, unless previously accomplished (Requirement; Compliance). The effective date is 24 September 2009 (Effective date). The following procedural checklist follows directly from those provisions.

1. Identify affected engines. Determine whether any aircraft in your fleet have Pratt & Whitney PW4164 or PW4168 series engines installed. The AD wording is "installed on but not limited to Airbus Industrie A330 series aircraft" (Applicability). If your fleet includes A330s with those engines, they are expressly within scope; if the engines are installed on other airframes, treat them as potentially within scope and include them in your assessment.

2. Check whether the replacement has already been accomplished. The AD exempts aircraft where the action has been "previously accomplished" before the effective date (Compliance). For any engine where the fan blade assembly has already been replaced with a configuration that satisfies the Pratt & Whitney service bulletin requirements prior to 24 September 2009, no further action under this AD is required. Verify maintenance records and parts logbooks for completion evidence.

3. Obtain the exact service bulletin. Acquire Pratt & Whitney Service Bulletin No. PW4G-100-72-92 dated 24 April 1997, which the AD specifically references as the method of compliance (Requirement). The AD requires work "in accordance with" that SB; therefore, you must follow the SB's procedural steps, inspection points, and acceptance criteria. Do not substitute a different SB version or a different document without documented confirmation that it meets the AD's requirement.

4. Review the SB content and scope. The SB will specify the components, part numbers, inspection procedures, access panels, torque settings, and any dimensional or non-destructive testing required to install a new or modified fan blade assembly. Confirm the specific parts that the SB targets, including whether the SB expressly addresses P/N 55A221 mentioned in the AD Background, and ensure the SB's configuration meets the AD's mandate.

5. Schedule maintenance within the 30-day window. The compliance requirement is "within 30 days after the effective date of this AD" (Compliance). With an effective date of 24 September 2009, arrange for the replacement within 30 days, unless the replacement has already been performed. Coordinate parts procurement, maintenance slot allocation, ferry flights if necessary, and availability of authorised maintenance personnel so the work can be completed in the timeframe.

6. Procure parts and tools. Obtain the new or modified fan blade assemblies specified or permitted by the SB. The AD does not describe whether the replacement parts are supplied at cost, under warranty, or otherwise; the operator is responsible for arranging parts. Ensure any special tooling or test equipment required by the SB is available and certified for use.

7. Perform the installation per the SB. Execute the replacement work in accordance with the SB instructions. Follow all detailed steps in the SB, including preparatory inspections, removal procedures, installation torques, balancing requirements and any post-installation checks specified. The AD makes compliance contingent on following the SB's requirements; therefore, adherence to the SB is essential to meet the AD.

8. Inspect and test as required by the SB. The SB may require functional checks, rotor balance verification, or ground run tests after installation. Carry out all such tests and verify that the equipment meets the acceptance criteria set out in the SB.

9. Document completion. The AD itself does not lay down recordkeeping procedures, but standard aviation practice requires updating aircraft and engine logbooks and maintenance records to show the change. Record the SB reference, the date of completion, parts installed, serial numbers, and the identity of the maintenance organisation and certifying personnel. Retain evidence that the replacement was completed within the 30-day AD window.

10. Coordinate with regulators where doubt exists. The AD does not set out reporting obligations or enforcement specifics; if there is uncertainty about whether the SB used meets the AD's requirements, or if an alternative means of compliance is proposed, contact the Civil Aviation Safety Authority or the appropriate regulatory delegate identified in the AD. The AD shows the issuer and the date signed, but does not include a contact point; operators should use established regulatory channels to seek formal acceptance of any alternative compliance proposal.

11. Reconcile part number references. The AD Background mentions fan blade P/N 55A221 as an example of a blade that was intentionally released during testing (Background). Ensure the parts referred to in your engines and in the SB are reconciled, and that any replacement parts are appropriate for the engine serial numbers in question.

12. Retain evidence of prior compliance. If the replacement was "previously accomplished" before 24 September 2009, gather documentary evidence showing the installation date, the SB followed, and parts used, so that the AD obligation is demonstrably satisfied.

This compliance pathway follows strictly from the AD text. The AD places primary compliance content in the combination of its Requirement and the referenced service bulletin; effective compliance therefore requires adherence to both the AD's deadline and the SB's technical instructions. Because the AD does not specify reporting, enforcement, or alternative compliance mechanisms, operators should document compliance thoroughly and consult the regulator when in doubt.