AD/PHZL/76 Amdt 2 - HC-C2YR-4CF Propeller Life Reduction

The AD is built on a small set of tightly defined concepts and operational rules drawn from the text.

• Applicability by part number and airframe/engine combination. The AD applies only to Hartzell propeller hubs P/N D‑6522‑1 or D‑2201‑16 and blades P/N FC8477A‑4 when they are installed on Sky International Inc. (Pitts) S‑2S and S‑2B aeroplanes with Textron Lycoming model AEIO‑540‑D4A5 engines. The AD does not purport to apply to other part numbers, airframes, or engines (Applicability).

• Service life expressed as Time Since New (TSN). The operational limit imposed is 2,000 flight hours TSN. The key installation prohibition activates at that TSN threshold: do not install any hub or blade that has accumulated 2,000 flight hours TSN (Requirement 2).

• Two trigger points for removal. The Compliance section sets out two distinct timelines: if the part has less than 2,000 flight hours TSN, removal must occur before it reaches 2,000 TSN; if it already exceeds 2,000 TSN, removal must occur before further flight (Compliance 1). This creates an immediate removal obligation in the case of unknown or exceeded TSN.

• Record‑based conservatism. Where the "details of the actual flight hours for a propeller hub or blade cannot be obtained," the AD requires treating the blade as if it exceeds 2,000 flight hours TSN (Compliance Note 3). That shifts the evidential burden onto the operator to show hours are below the threshold; absent that, the more restrictive treatment applies.

• Restrictions on re‑use between fleets. The AD prohibits cross‑installing a hub or blade removed from an applicable aeroplane onto any aeroplane not covered by the AD (Requirement 3). The AD allows satisfying that requirement by annotating the propeller logbook with the statement, "Do NOT install on an aircraft for which AD/PHZL/76 is not applicable" (Requirement Note 1). This is an administrative control intended to prevent reuse in other types.

• Alignment and international reference. The document explicitly references FAA AD 2003‑03‑20 Amendment 39‑13045 (Requirement Note 2) and notes that Amendment 1 aligned the compliance statement to the FAA AD (Background). The current amendment is said to correct an administrative omission and not to change technical content or the compliance schedule (Background).

• Safety rationale. The Background states that a re‑evaluation of propeller service life followed several engine failures and that exceeding the service life "could lead to failure of the hubs or blades resulting in subsequent loss of aeroplane control". The AD's actions are described as addressing that safety risk (Background).

These concepts combine operational limits (2,000 TSN), procedural steps (remove, do not install, logbook annotation), conservative record rules (assume >2,000 TSN if unknown), and cross‑jurisdictional alignment with an FAA AD.

The AD’s applicability clause defines a narrow set of parties directly obliged to comply. Owners, operators, maintenance organisations and inspectors of Sky International Inc. (Pitts) S‑2S and S‑2B aeroplanes powered by Textron Lycoming model AEIO‑540‑D4A5 engines and fitted with Hartzell propeller hubs P/N D‑6522‑1 or D‑2201‑16 and blades P/N FC8477A‑4 are the primary subjects (Applicability). That includes:

• Individual aircraft owners and commercial operators who operate the specific Pitts S‑2S or S‑2B with the specified engine and propeller parts. The Requirement mandates removal from service of those parts and sets installation prohibitions tied to TSN, which creates an obligation for operators to check and act.

• Maintenance organisations and certificated mechanics who hold propeller maintenance responsibility for those airframes and part numbers. They must effect removal in accordance with the compliance timing, record the action in logbooks, and can use the permitted logbook annotation to meet Requirement 3 (Requirement Note 1; Compliance).

• Registrars and maintenance record‑keepers. Because the AD treats unknown hours as in excess of 2,000 TSN (Compliance Note 3), accurate records are needed to claim an extended service life to 2,000 hours. Therefore parties who maintain logbooks or transfer parts must ensure traceability and appropriate annotation if parts are to be moved between aircraft.

• Parts managers and installers. The AD explicitly prohibits installing hubs or blades that have reached 2,000 flight hours TSN (Requirement 2) and forbids installing parts removed from an applicable aircraft onto non‑applicable aircraft (Requirement 3). Those who supply, store, or fit such parts must implement checks to prevent prohibited installations.

• Regulators and compliance auditors. Civil Aviation Safety Authority (CASA) issued the AD (signature: James Coyne, Delegate of CASA) and set the effective date (2 August 2005). Inspectors and auditors enforcing airworthiness must verify removal, installation records, logbook annotation, and compliance with the TSN rule.

• Cross‑jurisdictional parties. The AD references FAA AD 2003‑03‑20 (Requirement Note 2). Aircraft or parts moving between jurisdictions where FAA ADs apply, or organisations that track compliance across fleets in multiple regulatory spaces, must reconcile the CASA AD with the FAA AD alignment noted in Amendment 1 (Background).

The AD does not purport to affect other aircraft types, other Hartzell part numbers, or other engines. It also creates obligations for those who would re‑use removed parts, because installing such parts on non‑applicable aircraft is prohibited unless prevented by the logbook annotation mechanism (Requirement 3 and Note 1).

The AD imposes specific duties and gives one procedural right to satisfy a recordkeeping requirement. Key duties:

• Removal duty: Remove from service the specified Hartzell propeller hubs P/N D‑6522‑1 or D‑2201‑16 and blades P/N FC8477A‑4 when they are installed on the applicable Pitts S‑2S and S‑2B with Lycoming AEIO‑540‑D4A5 engines (Requirement 1). This is a positive obligation on operators or maintainers.

• Installation prohibition by TSN: Do not install any hub or blade of the specified part numbers that have accumulated 2,000 flight hours TSN (Requirement 2). This is an absolute TSN‑triggered prohibition on installation.

• Prohibition on cross‑installation: Do not install a propeller hub or blade removed from an applicable aircraft on an aircraft for which the AD is not applicable (Requirement 3). That prevents recycling these parts into other types of aeroplanes not covered by the AD.

• Conservative assumption for missing records: Where the details of actual flight hours cannot be obtained, the blades are to be assumed to be in excess of 2,000 flight hours TSN (Compliance Note 3). This shifts the evidential burden to the operator to prove hours are less than 2,000 if they wish to retain the part in service up to that limit.

• Time‑based removal deadlines: For parts with less than 2,000 flight hours TSN, removal must occur before 2,000 flight hours TSN; for parts with more than 2,000 flight hours TSN, removal must occur before further flight (Compliance 1). The AD therefore imposes immediate removal for any part already beyond the TSN limit.

One explicit procedural right is provided:

• Logbook annotation alternative: The intent of Requirement 3 (preventing installation on non‑applicable aircraft) may be met by annotating the propeller logbook with the statement, "Do NOT install on an aircraft for which AD/PHZL/76 is not applicable" (Requirement Note 1). That annotation is an accepted administrative control to satisfy the prohibition on cross‑installation.

Other operational or legal rights, penalties or enforcement mechanisms are not specified in the AD text supplied. The document also references FAA AD 2003‑03‑20 Amendment 39‑13045 (Requirement Note 2), and records that Amendment 1 aligned the compliance statement to that FAA AD (Background). The current Amendment is described as correcting an administrative omission with no change in technical content or compliance schedule (Background).

Practically, these duties require operators to check TSN records, remove or ground aircraft until the propeller parts are removed if TSN is unknown or exceeded, and ensure logbooks contain the stated annotation where parts are to be retained but restricted from re‑use on other aircraft.

The AD text supplied does not set out statutory penalties, monetary fines, or criminal sanctions. The document is an instrument issued by the Civil Aviation Safety Authority (CASA) and its header and signature indicate it is an enforceable airworthiness directive. The AD states an effective date and specific mandatory actions, which generates enforceable compliance obligations for the operators and maintainers within its applicability.

What the AD does provide that is relevant to enforcement:

• Effective date and issuer. The AD states "This Amendment becomes effective on 2 August 2005" and is signed by James Coyne, Delegate of the Civil Aviation Safety Authority (effective date row and signature block). That identifies the issuing authority and the date from which the removal/installation prohibitions are mandatory.

• Mandatory actions and timings. The AD prescribes immediate removal before further flight for parts with TSN in excess of 2,000 hours and before reaching 2,000 hours for parts below that threshold (Compliance 1). These clear binary timings are the operational basis upon which compliance checks and enforcement would occur.

• Record presumptions that affect compliance status. The AD requires assuming a part has more than 2,000 TSN if flight hours cannot be established (Compliance Note 3). That creates a standard auditors can apply when investigating records or alleged non‑compliance.

• Administrative compliance route. The AD permits a specific logbook annotation to meet Requirement 3 (Note 1). That creates an identifiable administrative control that enforcement officers can inspect.

The AD references FAA AD 2003‑03‑20 Amendment 39‑13045 (Requirement Note 2) and notes that Amendment 1 aligned the compliance statement to the FAA AD (Background). Enforcement in practice will often involve cross‑checking compliance against that FAA AD where international maintenance or parts movement is relevant, but the AD text does not itself set out an enforcement regime beyond the mandatory actions and effective date.

Because the supplied text does not include sanctions or procedures for action in the event of non‑compliance, readers must rely on the established enforcement mechanisms applicable to CASA airworthiness directives (outside the text provided) for details on penalties, suspensions, or rectification notices. The AD itself supplies the substantive obligations and a clear effective date for regulatory compliance.

The AD explicitly references and aligns with an FAA action, and it fits within the broader regulatory practice of airworthiness directives. The interactions appearing in the text are limited and specific:

• Reference to FAA AD. Requirement Note 2 states: "FAA AD 2003‑03‑20 Amendment 39‑13045 refers." The Background further notes that Amendment 1 of this AD aligned the compliance statement to the FAA AD and became effective on 01 August 2005 (Requirement Note 2; Background). That indicates deliberate harmonisation of the CASA AD’s compliance timing and instructions with an FAA AD, rather than a divergent set of requirements.

• Administrative alignment, not technical change. The Background states the current Amendment addresses "an administrative omission in the earlier Amendment, with no change in technical content or the compliance schedule." That signals that the AD’s amendments are intended to align wording and administrative detail with prior documents (including the FAA AD) rather than to alter the substantive regulatory standard.

• Logbook and recordkeeping implications. The AD’s requirement that unknown flight hours be treated as in excess of 2,000 TSN (Compliance Note 3) interacts with statutory and regulatory recordkeeping duties that govern aircraft maintenance records. While the AD does not quote those recordkeeping statutes, it imposes an evidential rule that will interact with any legal obligations to maintain accurate logbooks and parts traceability when establishing compliance.

• Installation constraints across fleets. Requirement 3 forbids installing a propeller hub or blade removed from an applicable aircraft on an aircraft for which the AD is not applicable. That restriction interacts with contractual or commercial practices around parts pooling, sale, and transfer; recipients of such parts must observe the AD’s constraint, which may overlap with other regulatory obligations in different jurisdictions.

• Effective dates and prior ADs. The Background records the original issue of the AD became effective on 11 March 2003. Amendment 1 aligned a compliance statement and became effective on 01 August 2005, while this Amendment became effective on 2 August 2005 (Background; effective date row). Those chronological links indicate that the AD should be read in the context of earlier AD issuances and the referenced FAA AD, which may contain complementary or explanatory material.

The AD text does not mention other specific Australian statutes, civil aviation regulations, or penalty provisions. Therefore the explicit interactions it records are limited to alignment and reference to the FAA AD and the administrative sequencing of amendments. Operators and maintainers will need to ensure that compliance with the AD is carried out in a manner consistent with any general recordkeeping, maintenance certification, and regulatory enforcement frameworks that govern their operations, but those frameworks are not specified in the text provided.

The AD text contains a concise amendment history captured in the Background and effective date entries. The timeline and nature of each change as recorded are:

• Original issue effective 11 March 2003. The Background states "The original issue of this AD became effective on 11 March 2003." That is the starting point for the AD’s lifecycle as recorded in this document.

• Amendment 1 effective 01 August 2005. The Background states "Amendment 1 of this AD aligned the compliance statement to the FAA AD and became effective on 01 August 2005." That indicates the first amendment was primarily an alignment of the compliance statement with the FAA AD (FAA AD 2003‑03‑20 Amendment 39‑13045 is referenced in Requirement Note 2).

• Current Amendment (Amdt 2) effective 2 August 2005. The AD is presented as "AD/PHZL/76 Amdt 2" with an effective date entry stating, "This Amendment becomes effective on 2 August 2005" and with the printed date and signature block dated 1 August 2005 (effective date row and signature). The Background specifies that this current Amendment "addresses an administrative omission in the earlier Amendment, with no change in technical content or the compliance schedule." That indicates the second amendment was administrative rather than substantive.

• Relation to FAA AD. Requirement Note 2 explicitly references FAA AD 2003‑03‑20 Amendment 39‑13045, and Amendment 1 is said to have aligned the compliance statement to that FAA AD (Requirement Note 2; Background). Thus, the amendment history involves both domestic administrative corrections and harmonisation with an FAA directive.

• No technical change declared in the latest amendment. The Background emphasises that the current Amendment corrects an administrative omission but does not change technical content or the compliance schedule. Therefore the substantive operational obligations,the 2,000 TSN threshold, removal and installation prohibitions, and the record presumptions,are represented as unchanged since at least the prior amendment.

These are the only amendment history details contained in the supplied text. The AD shows a short sequence of issuance, alignment with an FAA AD, and a subsequent administrative correction. There are no later amendments, revocations, or dates beyond 2 August 2005 recorded in the text provided.

The AD text contains no litigation history, court decisions, or adjudicative outcomes. It references FAA AD 2003‑03‑20 Amendment 39‑13045 (Requirement Note 2) and records the administrative amendments and effective dates (Background and effective date row), but it does not name any legal cases, appeals, or judicial reviews arising from this AD.

Because the supplied instrument is an administrative airworthiness directive and the text includes no record of disputes or litigation, readers should note that any litigation history, challenges, or enforcement proceedings,if they exist,are not contained in this document. The AD itself records only the issuance, amendments, effective dates and the rationale for the service life reduction (a re‑evaluation following engine failures leading to the conclusion that the propeller service life needed to be reduced).

Accordingly, for purposes of legal research or litigation preparedness, the AD provides the substantive regulatory obligations and administrative timeline, but it does not furnish information about subsequent litigation, legal interpretations, or contested enforcement actions. Any such material would need to be sought in external legal databases, court records, or CASA enforcement records beyond the AD’s text.

The AD contains several concrete features that can trip up operators, maintainers and parts managers if not treated carefully. These are drawn directly from the wording and notes in the AD.

• Narrow applicability, but absolute obligations within it. The AD applies only to hubs P/N D‑6522‑1 or D‑2201‑16 and blades P/N FC8477A‑4 installed on Pitts S‑2S and S‑2B aeroplanes with Lycoming AEIO‑540‑D4A5 engines (Applicability). Operators outside that narrow set are not covered, but any part that does meet those criteria is subject to mandatory removal and installation rules.

• Two different removal deadlines depending on recorded TSN. If the part has less than 2,000 flight hours TSN, removal is required before reaching 2,000 TSN. If it already exceeds 2,000 TSN, removal is required before further flight (Compliance 1). Failure to correctly interpret which category applies can lead to immediate non‑compliance.

• Unknown hours default is punitive. Where flight hours cannot be obtained, the AD requires assuming the blade has in excess of 2,000 flight hours TSN (Compliance Note 3). In practice this means missing or incomplete records convert a potentially future compliance task into an immediate removal requirement.

• Cross‑installation prohibition and the logbook annotation catch. Requirement 3 forbids installing a removed hub or blade on an aircraft not covered by the AD. The AD allows meeting that requirement by annotating the propeller logbook with a prescribed statement (Note 1). If parts are transferred without the annotation, the receiver may inadvertently breach the AD if they install the part on an aircraft outside the AD applicability.

• Alignment with an FAA AD may create multi‑jurisdictional obligations. The AD says Amendment 1 aligned the compliance statement with FAA AD 2003‑03‑20 (Background; Requirement Note 2). Operators that move parts or aircraft between jurisdictions need to manage compliance with both directive texts as applicable. The AD does not provide further cross‑jurisdictional implementation detail.

• Administrative amendment versus technical change. The current Amendment is described as correcting an administrative omission without changing technical content or the compliance schedule (Background). Practitioners faced with multiple document versions should check that the action items are technically identical across amendments, despite revised wording or effective dates.

• Immediate effective date for some parts. The AD became effective on 2 August 2005 (effective date row). For parts already beyond the TSN threshold, compliance was required "before further flight" from that effective date (Compliance 1). Records, operational schedules and maintenance slots must have been rearranged quickly in affected fleets.

• No penalties specified in the text. The AD sets mandatory obligations and an effective date but does not include penalty detail in the supplied text. Parties must therefore look to CASA enforcement instruments or general aviation regulatory sanctions outside the AD text for enforcement consequences.

• Potential for chain‑of‑custody confusion. The logbook annotation solution is administrative but may not be sufficient if parts change hands and annotations are not carried with the part. The AD’s strict prohibition on installing removed parts on non‑applicable aircraft means parties handling removed parts must implement clear tagging and record transfer practices.

Each of these gotchas flows directly from the AD wording: the strict TSN triggers, the record presumption for missing hours, the prohibition on cross‑installation and the permitted logbook annotation to meet that prohibition, the effective dates, and the explicit administrative nature of the latest amendment.

The AD provides a concise set of compliance steps. Below is a practical, source‑anchored checklist an operator or maintainer should follow to meet the AD requirements.

1. Identify affected parts and airframes (Applicability).

   • Confirm whether propeller hubs on the aircraft are P/N D‑6522‑1 or D‑2201‑16 and blades are P/N FC8477A‑4.
   • Confirm the aircraft model is Sky International Inc. (Pitts) S‑2S or S‑2B and the engine model is Textron Lycoming AEIO‑540‑D4A5. Only if all those conditions are met does the AD apply.

2. Determine Time Since New (TSN) for each affected hub and blade (Compliance).

   • Inspect propeller and aircraft logbooks to determine TSN.
   • If TSN is less than 2,000 flight hours, plan removals so that each hub or blade is removed before it reaches 2,000 flight hours TSN (Compliance 1.a).
   • If TSN is already more than 2,000 flight hours, remove the part from service before further flight (Compliance 1.b).

3. Treat unknown or missing TSN as >2,000 TSN (Compliance Note 3).

   • If records are incomplete or actual flight hours cannot be obtained, assume the blades are in excess of 2,000 flight hours TSN and remove them before further flight. This is an explicit presumption in the AD and not a discretionary enforcement policy.

4. Do not install parts that have reached 2,000 flight hours TSN (Requirement 2).

   • When receiving, storing or installing parts, check the TSN and ensure no installation of hubs or blades with 2,000 flight hours TSN or more.

5. Do not install parts removed from applicable aircraft onto non‑applicable aircraft (Requirement 3).

   • If a part removed from an aircraft covered by this AD is to be retained, either physically tag it so it is not fitted to other aircraft types or annotate the propeller logbook as permitted.

6. Use the permitted logbook annotation to meet Requirement 3 if preferred (Requirement Note 1).

   • The AD allows meeting the intent of Requirement 3 by annotating the propeller logbook with: "Do NOT install on an aircraft for which AD/PHZL/76 is not applicable".
   • Ensure that this annotation is permanent in the logbook entry associated with the propeller unit and that any documentation accompanying parts transfers records this annotation.

7. Schedule maintenance and replacements promptly relative to the effective date (effective date row; Compliance).

   • The AD became effective on 2 August 2005. For any part already beyond the TSN threshold at that date, removal was required before further flight. For parts below the threshold, set a removal plan that ensures removal before reaching 2,000 TSN.

8. Record and retain evidence of compliance.

   • Log the removal action, TSN at removal, and any logbook annotations used to meet Requirement 3. The AD’s presumption for missing records means that demonstrable records showing TSN below the threshold will be material to compliance status.

9. Where relevant, consult FAA AD 2003‑03‑20 Amendment 39‑13045 for alignment and background (Requirement Note 2; Background).

   • The AD references that FAA AD. While this AD provides the domestic requirements, the FAA AD is referenced as a related instrument and Amendment 1 aligned the compliance statement to it.

10. Where uncertainty exists about applicability or installation rules, seek clarification from CASA or a certificated engineer.

    • The AD defines a specific combination of part numbers, aircraft make/model and engine model. If there is any doubt about whether a particular part configuration is covered, obtain authoritative clarification before acting or installing parts.

Each of these compliance steps maps to explicit AD text: identification and applicability (Applicability), TSN thresholds and removal timing (Requirement 1; Requirement 2; Compliance 1), presumptions for missing records (Compliance Note 3), logbook annotation (Requirement Note 1), and the effective date (effective date row). Following that sequence will meet the AD’s stated mandatory actions and the administrative route for preventing cross‑installation.