AD/G1159/46 - State of Design Airworthiness Directives

The directive employs several key regulatory concepts that practitioners need to understand. First, an Airworthiness Directive is a legally enforceable regulatory instrument issued under the Civil Aviation Act 1988 that mandates corrective action on an aircraft type to address an unsafe condition. Noncompliance renders the aircraft unairworthy and unlawful to operate. Second, the directive uses the concept of a “State of Design” AD - a directive originating from the national aviation authority of the country that originally certified the aircraft type. For Gulfstream GIV-X, GV, and GV-SP series aeroplanes, the state of design is the United States, so the FAA is the source AD authority. CASA has adopted these FAA ADs by reference rather than rewriting them. Third, the term “one time actions” appears in the background: this means the FAA ADs require a single inspection, modification, or replacement, not repetitive ongoing maintenance. However, each FAA AD may have its own compliance time (for example, “within 90 days” or “before further flight”), and those times have already lapsed. The directive effectively resets the compliance requirement to now. Fourth, the applicability determination is a critical concept: not every aircraft in the fleet will be affected by every FAA AD. The directive says CASA appreciates that due to date of manufacture or aircraft configuration and modification status, not all ADs in Table 1 will apply to all aircraft. Therefore the operator must assess each aircraft individually against each FAA AD. This requires access to aircraft records, serial numbers, modification history, and the precise wording of each FAA AD. Fifth, the directive references a Certificate of Airworthiness: compliance is due before a CoA is issued, which means new imports or aircraft that have never held an Australian CoA must comply before entering service. Sixth, the directive contains a “Note” that gives a URL for accessing copies of the FAA ADs via the FAA’s Regulatory and Guidance Library. This note is important because the FAA ADs are not reproduced in the instrument; the operator must obtain them externally. Seventh, the compliance paragraph gives a binary deadline: within 30 days after the effective date of this directive (13 July 2007) or prior to the issue of a Certificate of Airworthiness, whichever occurs later. That means for aircraft already holding a CoA on 13 July 2007, the deadline is 30 days later - about 12 August 2007. For aircraft that receive a CoA after that date, compliance is due before the CoA issues. The directive does not allow extension beyond that.

The directive applies to the registered operators, owners, and maintenance organisations responsible for Gulfstream GIV-X, GV, and GV-SP series aeroplanes on the Australian civil aircraft register. The applicability field states: “Gulfstream GIV-X, GV and GV-SP series aeroplanes, as identified in the individual United States Federal Aviation Administration (FAA) Airworthiness Directives (AD) listed in Table 1.” Note that the directive header includes “Gulfstream (Grumman) G1159 and G-IV Series,” which could create confusion about scope, but the applicability paragraph is the controlling text. The G1159 and G-IV series are earlier models not covered by this directive unless they fall within the GIV-X, GV, or GV-SP designations. The directive affects a narrow and expensive fleet: Gulfstream business jets are high-value assets, and the required actions under the incorporated FAA ADs can involve significant labour, parts, and downtime. The seven FAA ADs cover a roll axis hardover prevention system (likely a flight control safety modification), wiring harness clearance checks, fire extinguisher bottle replacement or inspection, circuit breaker panel inspection, aileron inspections or modifications, landing gear dump valve checks, and crew oxygen bottle maintenance. Each of these actions imposes a direct cost on the operator, and because the ADs are overdue, the work must be done immediately. The directive also affects importers: an aircraft imported after 13 July 2007 cannot receive a CoA until it complies. This creates a potential barrier to entry for importing these aircraft from overseas, especially if the FAA ADs were not complied with in the previous jurisdiction. The directive does not distinguish between commercial operators and private owners; the compliance duty is the same. Maintainers and Licensed Aircraft Maintenance Engineers must be familiar with the FAA ADs and have the relevant service information. The directive also indirectly affects spare parts suppliers and Gulfstream service centres, because demand for the required parts and labour will spike in the 30-day window. There is no grace period for overseas operators temporarily operating in Australia; the directive applies to any aircraft on the Australian register.

The directive imposes two principal duties. Duty 1: “Determine the applicability of the FAA ADs listed in Table 1.” This is an analytical obligation. The operator must obtain each FAA AD, read its applicability paragraph, and compare it against the aircraft’s type, serial number, modification status, and configuration. This may require consulting maintenance records, logbooks, engineering drawings, or the aircraft’s history. If the FAA AD states it does not apply to aircraft with certain modifications already incorporated, the operator must verify that those modifications are indeed present. Duty 2: “If it is determined that an AD listed in Table 1 is applicable and has not been previously accomplished, perform the actions required by that AD.” This is an operational and maintenance obligation. The operator must carry out whatever the FAA AD mandates: inspection, replacement, adjustment, modification, or test. The directive does not specify the level of detail; the FAA ADs themselves contain the instructions and may reference service bulletins, maintenance manuals, or other documents. The compliance deadline for both duties is the same: within 30 days after 13 July 2007 or before the issue of a CoA, whichever is later. The rights of the operator are limited. The directive does not include a mechanism for applying for an extension or alternative means of compliance; however, under the broader CASR framework, an operator could apply to CASA for an AMOC under regulation 39.007 or seek an exemption under the Civil Aviation Act. Nothing in this directive expressly bars that, but the short compliance window makes it impractical. The operator also has the right to rely on previous compliance records: if the FAA AD action was already accomplished before the effective date, the operator does not need to repeat it. But the operator must have documentary proof. The directive does not provide for CASA to confirm compliance; it is the operator’s responsibility. There is an implied right to access the FAA ADs for free via the provided URL, though network access and interpretation still cost time. The operator also has the right to delegate the work to an appropriately approved maintenance organisation, but the registered operator retains legal liability for compliance.

Noncompliance with an Airworthiness Directive is a serious regulatory offence under the Civil Aviation Act 1988. Section 20A makes it an offence to operate an aircraft that does not comply with an applicable airworthiness directive. The maximum penalty can be substantial - for an individual, up to 50 penalty units (currently $8,250) for a strict liability offence, or higher if prosecuted as an indictable offence. For a body corporate, the penalty can be up to five times that. Additionally, the aircraft’s Certificate of Airworthiness may be suspended or revoked, which grounds the aircraft until compliance is achieved and CASA reissues the certificate. The directive itself is enforceable by CASA inspectors and authorised persons. During a ramp inspection or maintenance audit, an inspector can request evidence that AD/G1159/46 has been complied with. If the operator cannot demonstrate compliance within the required timeframe, enforcement action can range from a notice of intended action to civil penalty proceedings or criminal prosecution. The source document does not mention fines or penalties, but the underlying legislation does. The practical consequence is that an operator who fails to comply within the 30-day window is operating unlawfully from day 31. Insurance policies may also be voided if the aircraft is not maintained in accordance with ADs. The directive does not provide for self-reporting, voluntary disclosure, or leniency; it is a strict requirement. There is no mention of defence of reasonable steps or due diligence in the directive itself, though such defences may exist under general criminal law principles. The background states that CASA issued the directive “to ensure all State of Design ADs are complied with.” That indicates a zero-tolerance approach: CASA considers compliance with overseas ADs a necessary condition of airworthiness. Enforcement is likely to be rigorous, especially because the ADs address safety-critical systems (flight controls, landing gear, fire suppression). The costs of enforcement - both direct penalties and indirect costs of grounded aircraft, lost revenue, and reputational harm - are entirely borne by the operator.

AD/G1159/46 sits at the intersection of Australian and United States aviation regulatory frameworks. The primary Australian legislation is the Civil Aviation Act 1988, under which the CASA delegate has the power to issue airworthiness directives. The directive also operates within the Civil Aviation Safety Regulations 1998 (CASR), particularly Part 39 (Airworthiness Directives) and Part 42 (Continuing Airworthiness). Part 39 sets out the legal effect of ADs, the process for issuing them, and obligations on operators. This directive is a “State of design” AD, meaning CASA has adopted standards from the country that designed the aircraft, consistent with the Bilateral Aviation Safety Agreement between Australia and the United States. The directive does not replace or modify the FAA ADs; it enforces them from an Australian legal perspective. If there is a conflict between the FAA AD and CASR, this directive resolves it by mandating compliance with the FAA AD as written, subject to the compliance timeframe in the CASA directive. The directive also interacts with the maintenance regulations: the work required must be performed by a Part 145 approved maintenance organisation, and the actions must be recorded in the maintenance release and aircraft logbooks. The directive may also interact with the Airworthiness Approved Maintenance Schedule (AAMS) for the aircraft type; the FAA AD actions become additional mandatory items that override the schedule. There is no mention of state or territory laws; the directive is exclusively federal. However, if the FAA AD requires replacing parts that are subject to export controls or customs duties, those other laws may affect the cost and timing of compliance. The directive does not mention interaction with international law, but under the Chicago Convention, Australia is obliged to give effect to ADs from the state of design. Practically, an operator cannot comply with this directive without also complying with the underlying FAA ADs. The directive also implicitly gives legal effect to FAA service information referenced in those ADs. This creates a cascading incorporation of foreign technical standards that the operator must follow. There is no mutual recognition provision: if a Gulfstream aircraft holds a valid airworthiness review certificate from another jurisdiction, that does not exempt it from this directive when it enters the Australian register.

The source document is the original issuance of AD/G1159/46, signed on 21 June 2007, effective 13 July 2007. The document does not show any preceding amendments or versions. The Table 1 heading lists FAA ADs with effective dates ranging from 5 May 1998 (FAA AD 98-09-01) to a presumably erroneous date of “91 November 2004” for AD 2004-22-16 (almost certainly a typo for 1 November 2004). The instrument itself has not been amended in the text provided. The directive appears to be a single issuance intended to capture a batch of FAA ADs that had already taken effect years earlier. It is possible that later CASA ADs superseded or amended this one, but no such information is in the source. The effective date of the directive itself is unambiguous: 13 July 2007. The compliance paragraph references that date. There is no mention of any transitional provisions or staggered compliance. The directive does not have a sunset clause or expiration date. From the structure, it is a standing AD: it remains in force until individually rescinded or superseded. Anyone researching the current status would need to check later CASA AD listings and the current consolidated AD database. The amendment history, if any, would be recorded on CASA’s AD register. Because the underlying FAA ADs themselves may have been amended or superseded over time, the operator must determine whether the FAA AD listed in Table 1 is still the current requirement or whether a later FAA AD applies. The CASA directive does not incorporate FAA amendments after 2007. This is a potentially significant gap: an operator might comply with FAA AD 2001-21-06 as listed, but if the FAA later superseded it with a more stringent requirement, the operator may still be required by Australian law to do only the old AD unless another CASA AD covers the update. Conversely, if the FAA later withdrew an AD, the CASA directive would still mandate the old requirement unless CASA also amended it. This highlights a risk of regulatory divergence and the need for the operator to seek clarity.

The source document contains no information about litigation history. Airworthiness directives are rarely the subject of direct litigation in Australia, but that does not mean challenges are impossible. An operator could seek judicial review of the decision to issue the AD under the Administrative Decisions (Judicial Review) Act 1977, but only on grounds of jurisdictional error, procedural fairness, or unreasonableness. Because this AD adopts FAA standards by reference, it would be difficult to argue that CASA exceeded its power. The threshold for review is high. There are no reported cases mentioned in the source, and I cannot invent any. In practice, operators who dispute an AD typically apply for an alternative means of compliance or an exemption rather than go to court, because litigation is expensive and slow and the AD will ground the aircraft in the interim. The Background paragraph notes that the FAA ADs “require one time actions for which the compliance date and/or period has passed.” This suggests that the directive is retrospective in effect: it imposes a requirement that was technically overdue. That might raise administrative law questions about retrospectivity, but CASA likely considered that the aircraft can be made compliant now, and the directive does not penalise past noncompliance. It is prospective in its enforcement. No case law is known that specifically addresses this CASA AD. The directive was issued in 2007, and if it has been complied with and possibly superseded, any litigation would have been historical. For a deep dive, the absence of litigation history is itself informative: it suggests that the regulated community accepted the directive and complied, or that enforcement actions were resolved administratively. The directive is a relatively mundane technical instrument unlikely to generate controversy. However, an operator who faced an enforcement action for noncompliance could still contest the penalty in the Administrative Appeals Tribunal or a court, but such cases are not on the public record in this source.

Several traps await the unwary operator or practitioner. First, the compliance timeframe is deceptively tight. The directive says “Within 30 days after the effective date of this Directive or prior to the issue of a Certificate of Airworthiness, whichever occurs later.” For an aircraft already holding a CoA, that gives 30 days from 13 July 2007 - effectively until 12 August 2007. But the operator must first determine applicability of seven FAA ADs, obtain each FAA AD (some may be difficult to find online), interpret them, ascertain the aircraft’s modification status, and then schedule and perform the required actions. For some ADs the actions may require parts that are not immediately available, special tooling, or downtime of several weeks. The directive does not allow any extension based on parts availability. The operator is trapped: if parts are backordered, the aircraft will be grounded on day 31 and remain grounded until the work is done. Second, the directive is ambiguous about whether the compliance timeframe applies to the determination step (step 1) or also to the performance step (step 2). The text places both requirements under the same compliance paragraph. That means the operator must not only determine applicability but also complete the actions within the same 30-day window. There is no provision for doing only the determination within 30 days and scheduling the work later. Third, the FAA ADs themselves may have their own compliance times that are different. For example, FAA AD 98-09-01 (Roll Axis Hardover Prevention System) may have required compliance within 60 days of its 1998 effective date. The CASA directive could be interpreted to override that and require compliance within 30 days. That is a punitive acceleration. Fourth, the directive lists “Gulfstream GIV-X, GV and GV-SP series aeroplanes” but the header includes “Gulfstream (Grumman) G1159 and G-IV Series.” An operator of a G-IV (not GIV-X) might wrongly believe the AD applies, or a GIV-X operator might overlook the AD because the header is broader. The controlling text is the applicability field, but the inconsistency creates confusion and potential for error. Fifth, the effective date of FAA AD 2004-22-16 is given as “91 November 2004,” which is obviously a typographic error. November has 30 days; “91 November” does not exist. This could cause a dispute over the precise FAA AD version or compliance time. The correct date from FAA records is likely 1 November 2004. The practitioner should verify directly from the FAA source. Sixth, the directive says “Determine the applicability of the FAA ADs listed in Table 1.” It does not require the operator to record that determination in writing, but without a record, it will be impossible to prove compliance to CASA. The prudent operator will create a compliance matrix for each aircraft. Seventh, the directive covers “GIV-X, GV and GV-SP”, but the generic type certificate holder’s name is “Gulfstream (Grumman) G1159 and G-IV Series”. There may be aircraft with older type certificates that have been modified to GIV-X standard; the directive’s applicability language requires reference to the individual FAA ADs, which may have different applicability criteria. That introduces a layer of cross-referencing complexity.

Compliance with AD/G1159/46 involves a structured process that should be documented thoroughly. Step 1: locate the current text of each FAA AD listed in Table 1. The note provides a URL to the FAA Regulatory and Guidance Library. The operator should download and save the official PDF of each AD and verify that the amendment level matches the CASA reference. Step 2: for each aircraft in the fleet, establish a compliance status matrix. The matrix should list each FAA AD, the aircraft registration, serial number, date of manufacture, and current modification status. Step 3: for each FAA AD, read its “Applicability” paragraph. The FAA AD will define applicability by aircraft model, serial number range, or modification status. For example, a given AD may only apply to GIV-X aeroplanes with certain cockpit configurations. If the aircraft is outside the specified parameters, record that it is not applicable and the basis for the determination. Step 4: if the FAA AD is applicable, check the aircraft’s maintenance records to determine whether the required action has already been accomplished. The action must match exactly what the FAA AD requires, including compliance with any service bulletins referenced. If it was accomplished, document the date, reference, and signature. Step 5: for applicable actions not previously accomplished, schedule the maintenance with an appropriately approved Part 145 maintenance organisation. The FAA AD will specify the required work, which may involve inspection, modification, or replacement. The maintenance organisation must have access to the relevant service information and parts. Step 6: complete the work and issue a maintenance release in accordance with CASR Part 42. The release must reference AD/G1159/46 and the specific FAA AD satisfied. Step 7: update the aircraft’s continuing airworthiness records and include a copy of the FAA AD or a summary. Step 8: if the work cannot be completed within the 30-day compliance period, the operator must either remove the aircraft from service until compliance is achieved or seek an alternative means of compliance from CASA under regulation 39.007. This requires submitting a detailed engineering argument and proposed alternative actions. There is no guarantee it will be granted, and the process takes time, so it should be initiated immediately. Step 9: for aircraft that do not yet hold an Australian Certificate of Airworthiness, ensure compliance is accomplished before the CoA application is made. The maintenance organisation must confirm in writing that all applicable FAA ADs are satisfied. Step 10: keep all records for the life of the aircraft plus any statutory retention period. The operator should also monitor any subsequent FAA actions, because the FAA may supersede or revise the ADs in Table 1. If that happens, the operator should check whether CASA has issued a superseding AD or whether the existing AD/G1159/46 remains the applicable Australian requirement. The compliance costs include labour, parts, downtime, and administrative effort. There is no explicit cost offset in the directive. The operator should budget for these as mandatory operational costs.