This AD contains several practical specifics that can cause non-obvious operational or compliance issues if overlooked. The following points are drawn directly from the source and describe mechanics that can be easy to miss:
Applicability depends on both serial number and documented maintenance history
- The Applicability section conditions coverage in the first serial-number block on whether hose kit 390-5805-0001 was installed during compliance with Hawker Beechcraft Mandatory SB 29-3800 dated May 2007. That means simply being within the RB-4 to RB-209 serial-number range does not automatically create an obligation unless the hose kit installation history matches. Operators must check maintenance records to determine whether the specific hose kit was installed during the specified SB compliance (Applicability). This record-based gate means maintenance records need to be accessible and accurate; absent documentation the operator may need to treat the aircraft as applicable until records confirm otherwise.
The identity check is tag-based and references Table 1 in SB 29-3897
- Requirement 1 instructs the operator to identify suspect hose assemblies by examining identification tags for work order numbers and manufacturing dates listed in Table 1 of SB 29-3897. The AD therefore requires operators to rely on tag information and on a specified table in the SB. If tags are missing, illegible, or inconsistent with the table, the AD does not specify an alternative method in the supplied text, which could create uncertainty about whether the hose is “affected” (Requirement 1). Operators should be mindful that the AD ties identification to the SB’s Table 1.
Short initial inspection window and frequent repetition
- The initial inspection for identity and for leakage (if affected hoses are present) must be done within 10 hours TIS after the effective date (Compliance: For Requirement 1 and For Requirement 2). If an affected hose is installed, the AD requires repetitive leakage inspections at intervals not to exceed 10 hours TIS until either 40 hours total TIS is accumulated or the hose is replaced. This creates a period of high-frequency inspection obligations, which can be operationally disruptive if an aircraft is in frequent service.
Replacement timing complexity
- Replacement is required “before further flight” after any inspection that finds leakage. Separately, replacement must occur “within the next 200 hours TIS after the effective date of this AD or within the next 6 months after the effective date of this AD whichever occurs first” (Compliance: For Requirement 3). Practically, operators must track both the immediate trigger of leakage-related replacement and the broader scheduled replacement deadline. The phrase “whichever occurs first” in the scheduled replacement clause creates a calendar/TIS interplay that requires tracking both metrics.
Service bulletin incorporation, not reproduction
- The AD does not reproduce the inspection or replacement procedures; it requires that work be done “in accordance with Hawker Beechcraft Mandatory SB 29-3897.” Therefore the operator must obtain and follow the SB for the procedural steps. Failure to follow the SB exactly is not addressed in the AD text, which is silent on whether deviations are permitted or how they are to be approved (Requirement 1, Requirement 2).
No enforcement or record-keeping detail in the AD text
- The AD does not provide specific directions about how to document compliance, how to present proof to CASA, or what records must be retained. The supplied text does not state whether operators must submit compliance reports. This omission can create operational uncertainty about audit and oversight expectations.
Cross-reference to an FAA AD
- The AD contains a note referring to FAA AD 2008-22-11. The CASA AD does not explain whether compliance with the FAA AD would satisfy the CASA AD or vice versa. Operators who are dual-registered or operate internationally may find the relationship between the instruments unclear based on the text alone.
Effective date post-dating signature
- The AD is signed on 28 October 2008 and becomes effective on 3 November 2008. Operators must ensure initial inspections occur within 10 hours TIS after the effective date, not the signature date. The time lag between signature and effective date could be overlooked.
In short, the AD’s reliance on service-bulletin tables and tags, its record-conditioned applicability, its short inspection intervals, and absence of procedural enforcement detail are all operational points that can generate compliance risk if not actively managed.