AD/RAD/81 Amdt 1 - Garmin Mode S Transponders

The directive rests on a short chain of technical causes and regulatory responses stated within the text. Key concepts in the instrument are:

• Applicability: the directive names the specific Garmin Mode S transponder models GTX 33, GTX 33D, GTX 330 and GTX 330D. It then enumerates an extensive set of aircraft manufacturers and models on which those transponders may be installed, from Aermacchi and Cessna to Pilatus, Raytheon and many others. That list functions as the practical scope for operators checking whether their aircraft falls within the AD’s reach.

• Software versioning as the regulatory trigger: the directive treats the transponder software revision as the compliance determinant. Transponders running software versions 3.00, 3.01, 3.02, 3.04 or 3.05 are explicitly required to be upgraded to at least 3.06. Transponders already on 3.03 are identified as requiring no action. The directive incorporates Garmin Mandatory Software Service Bulletin No. 0409 dated 19 July 2004 as the procedural means to perform the upgrade.

• Safety deficiency described in operational terms: the root problem is the transponder’s handling of the S1 suppression interrogating pulse when it is below the Minimum Trigger Level (MTL). The directive records that certain software versions permitted suppression behaviour that caused a transponder to fail to reply when it should have done so. The risk outlined is inaccurate replies being provided to interrogating aircraft, which the AD links to potential reduced vertical separation or unsafe TCAS (Traffic Collision Avoidance System) resolution advisories.

• Regulatory hierarchy and cross-reference: the directive references an FAA airworthiness directive (FAA AD 2005-01-19 Amdt 39-13944) and a Garmin mandatory service bulletin. The AD itself is an administrative regulatory instrument issued by CASA via a delegate, James Coyne, effective on a stated date and with a compliance deadline.

• Temporal and administrative effects: the amendment updates and supersedes elements of an earlier directive. The AD records that the original directive became effective on 5 August 2004 and that the amendment increases applicability and changes the required software level to 3.06. The compliance date and effective date create timelines within which the mandated technical action must be taken.

Those concepts combine technical failure mode description with a software-fix mandate and a directed administrative deadline. The AD treats the manufacturer's service bulletin as the mandated method of implementation and identifies the set of aircraft potentially affected by the requirement through an extensive make/model list.

The directive explicitly affects operators, owners, maintenance organisations and any person responsible for the continued airworthiness of aeroplanes fitted with Garmin GTX 33, GTX 33D, GTX 330 or GTX 330D Mode S transponders that have the enumerated software versions. The text lists dozens of aircraft manufacturers and a very large number of individual model designations on which the subject transponders may be installed, including but not limited to Aermacchi S.p.A, Aerostar, Cessna Aircraft Company, de Havilland (DHC) models, Diamond Aircraft, Embraer EMB-110, Pilatus PC-12/PC-6 families, Raytheon models, Piper, Piaggio, Mooney, and many others. That list functions as the practical pointer for which aircraft types should check equipment fit.

Who pays: the directive imposes the upgrade obligation on the operator or owner of the affected aircraft. The document does not set out cost recovery or subsidies; it simply requires the software upgrade to at least version 3.06 in accordance with the Garmin Mandatory Software Service Bulletin. Absent any statement in the text to the contrary, the cost of parts, labour and aircraft downtime for the upgrade will fall to the aircraft owner or operator and to any maintenance organisation performing the work.

Who decides: CASA, acting through its delegate (the directive is signed by James Coyne, Delegate of CASA), decides the requirement. The AD itself is the instrument imposing the duty; it also points to Garmin’s Mandatory Service Bulletin and to the FAA AD as cross-references. There is no express administrative appeal procedure, exemption clause or alternative method of compliance described in the document.

Operational effects on behaviour: affected operators must identify whether a GTX 33/33D/330/330D is installed on their aeroplane, determine the current installed software version, and if the transponder runs versions 3.00, 3.01, 3.02, 3.04 or 3.05, arrange for upgrade to at least 3.06 in accordance with Garmin SB No. 0409. Operators already at 3.03 are recorded as requiring no further action, but Note 2 also states 3.03 is no longer available from Garmin, which affects the practical availability of that version for reinstallation or replacement.

Geographic and regulatory interaction: the AD is issued by CASA for Australian-regulated aircraft. The instrument references FAA AD 2005-01-19, indicating technical alignment or commonality of safety concern with actions taken by the United States regulator. Maintenance and operators who operate internationally should be aware that the same or parallel FAA directive is relevant.

Duties imposed by the AD are concrete and narrowly defined. The primary duty is the software upgrade: transponders listed with software versions 3.00, 3.01, 3.02, 3.04 or 3.05 must be upgraded to at least version 3.06 in accordance with Garmin Mandatory Software Service Bulletin No. 0409 dated 19 July 2004. The compliance timeframe is set: the upgrade must be completed before 30 September 2005. The AD establishes GTX 33/33D/330/330D as the covered equipment and provides an aircraft applicability list identifying where those transponders may be installed.

Rights or definitional carve-outs in the text are limited. The AD explicitly states that transponders with software version 3.03 already installed require no further action. That is the only explicit exemption or "no-action-required" class mentioned. Note 2 however records that version 3.03 is no longer available from Garmin, which has operational implications: the AD still recognises 3.03 as acceptable but acknowledges it cannot be sourced from the manufacturer.

The AD does not set out any administrative procedural rights such as an express process for seeking an alternative method of compliance, request for exemption, or appeal. The document likewise does not include a clause authorising deferred compliance on safety grounds, special flight permits, or ferry flights while awaiting the upgrade. Those sorts of administrative mechanisms are common in airworthiness practice, but they are not specified in the text supplied.

Compliance mechanics in the directive do not explicitly address record-keeping, maintenance log entries, or certificate-of-compliance issuance; they do however mandate compliance "in accordance with Garmin Mandatory Software Service Bulletin No. 0409 dated 19 July 2004", thereby invoking the manufacturer’s procedural detail as the required method. That effectively binds the operator to follow the steps and documentation identified in the Garmin service bulletin as the means to achieve compliance.

The AD gives no express warranty, indemnity or cost allocation between manufacturer, maintenance organisation and operator. The wording that versions 3.04 and 3.05 "inadvertently removed the correction" is a statement of fact as reported by Garmin and by reference to the FAA; it does not, within this document, create a remedial obligation on Garmin to cover costs. The AD also does not expressly direct maintenance organisations to perform the upgrade; rather, it imposes an operator obligation to have the work done in accordance with the specified service bulletin.

The directive itself prescribes a mandatory operational requirement and a compliance deadline, but it does not, within the text provided, state specific monetary penalties, criminal offences, or administrative sanctions for non-compliance. The document records the upgrade requirement, the compliance date of before 30 September 2005, and the effective date of the amendment as 14 April 2005. It is signed by a CASA delegate. Those features are typical of airworthiness directives, which operate as regulatory instruments within the broader aviation safety regime.

Because the AD document supplied does not specify enforcement mechanisms, the instrument should be read against CASA’s broader statutory powers as the issuing regulator. The AD itself functions as a mandatory direction to ensure airworthiness and safe operation and is typically enforced through the regulatory framework that governs continuing airworthiness, operating certificates and maintenance approvals. The AD cross-references FAA AD 2005-01-19; that cross-reference signals technical alignment with a parallel regulator, but it does not itself set out enforcement rules.

Operationally, enforcement risks for non-compliance can include grounding of the aircraft, refusal of maintenance release for continued operation, or administrative regulatory action concerning the operator’s approvals. The supplied text does not enumerate those outcomes, and it contains no penalty table, infringement notice, or criminal sanction. Therefore, anyone concerned about enforcement should consult CASA’s statutory powers and enforcement policies that sit outside this AD to determine the precise legal consequences for failing to undertake the required upgrade by the compliance date.

The AD does make a safety rationale explicit: inaccurate replies from the affected transponders could result in reduced vertical separation or unsafe TCAS resolution advisories. That safety articulation is the basis for treating the directive as a compulsory corrective measure. The AD does not, in its text, provide a compliance extension mechanism, an alternative method of compliance, or a contact point for enforcement waivers. Those matters are ordinarily handled by the regulator through separate processes, but they are not recorded in the supplied instrument.

The AD references and interacts with two principal categories of external instruments within its own text: the manufacturer’s mandatory service bulletin and a corresponding FAA airworthiness directive. The directive explicitly requires compliance "in accordance with Garmin Mandatory Software Service Bulletin No. 0409 dated 19 July 2004" and refers to "FAA AD 2005-01-19 Amdt 39-13944". Those cross-references are the only external legal or quasi-legal instruments cited in the document.

The interaction with the Garmin service bulletin is functional. By incorporating the service bulletin as the procedural means of compliance, the AD makes the manufacturer's technical directions the operative method by which an operator satisfies the AD. That alignment means the manufacturer’s specified processes, likely including installation steps and documentation, are elevated to regulatory effect for the purposes of this AD. The AD does not state whether alternative methods of compliance approved by Garmin or CASA are acceptable; it simply directs compliance "in accordance with" the service bulletin.

The reference to the FAA AD indicates cross-jurisdictional technical harmonisation. The AD records that FAA AD 2005-01-19 is referred to, and that the amendment resulted from Garmin advising the FAA regarding inadvertent removal of the correction in versions 3.04 and 3.05. That shows the Australian directive is reacting to the same technical information that prompted the FAA action. For Australian operators who also operate under foreign registries or have international operations, the FAA AD may present a parallel compliance obligation in other jurisdictions, while the CASA AD creates the national requirement for Australian-registered aircraft.

The supplied AD does not explicitly mention any other statutory provisions, civil aviation regulations, or standards that would govern enforcement, certification or continuing airworthiness procedures. It does not cite the specific CASA statutory provision authorising issuance of ADs. Those are elements that, while likely existing in the broader legislative framework, are not set out in the text provided.

Practically, the AD positions the Garmin service bulletin and the FAA AD as the immediate instruments to consult. The AD thereby creates an operational intersection between manufacturer-issued mandatory maintenance direction and the regulator-issued airworthiness directive. For operators, that means satisfying the service bulletin will directly address the regulatory duty in the AD, while failing to follow the service bulletin would leave them non-compliant with the AD.

The supplied document is itself an amendment to an earlier airworthiness directive. The AD is titled AD/RAD/81 Amdt 1 and is dated 4/2005. The text records that "The original issue of this Directive became effective on 5 August 2004." The amendment increases applicability to include GTX 33 and GTX 33D transponders and modifies the required software fix to require installation of software version 3.06. The background narrative states that the original issue required installation of GTX 330/330D Software Upgrade Version 3.03, 3.04 or 3.05. The amendment was issued after Garmin advised the FAA that versions 3.04 and 3.05 inadvertently removed the correction that had been intended to ensure transponders reply even when S1 pulses are below the Minimum Trigger Level.

Chronology provided by the AD text:

• Original directive effective 5 August 2004. The original directive required GTX 330/330D Software Upgrade Version 3.03, 3.04 or 3.05.

• Garmin issued a Mandatory Software Service Bulletin No. 0409 dated 19 July 2004, which is the procedural document referenced in the AD for performing the software upgrade.

• Garmin advised the FAA that software versions 3.04 and 3.05 inadvertently removed a prior correction. This prompted further action.

• The FAA issued AD 2005-01-19 Amdt 39-13944. The AD supplied to us notes that FAA AD 2005-01-19 is referred.

• CASA issued AD/RAD/81 Amdt 1, effective 14 April 2005, signed 2 March 2005 by James Coyne as Delegate of CASA, with a compliance deadline of before 30 September 2005. The amendment expands applicability to cover GTX 33 and GTX 33D transponders and mandates installation of software version 3.06 where applicable.

The amendment therefore reflects an iterative regulatory response to a technical issue and to evolving manufacturer and FAA information. The document records both the original position and the subsequent change in required software version. The AD contains specific notes, including Note 2 which states that version 3.03 is no longer available from Garmin, and Note 3 which states FAA AD 2005-01-19 Amdt 39-13944 refers.

No further amendments or subsequent revisions are recorded in the supplied text. The supplied amendment text itself serves as the historical record within the document for the sequence of events and the rationale for the change in direction from 3.03/3.04/3.05 to the now-required 3.06 software baseline.

The AD document supplied contains no record of litigation, court proceedings, judicial decisions, or named cases. The instrument is an administrative directive issued by CASA and the text does not reference any legal proceedings, appeals, or case law. It records only regulatory actions, manufacturer communications and a cross-reference to an FAA airworthiness directive.

Because the supplied material is silent about litigation, there is no case law or litigation history to report from this document. The AD does identify the safety deficiency, the manufacturer’s remedial measures (the service bulletin), and the FAA’s parallel action, but it does not indicate that the directive has been the subject of judicial review or other court challenge.

Operators, maintenance organisations and legal practitioners should therefore treat the AD as an administrative regulatory instrument with no litigation history recorded in the issuing text. If a reader requires information about any subsequent legal challenges, enforcement actions, or case law arising from this AD, that would require searching judicial and regulatory enforcement records outside the scope of the supplied document.

Absent litigation recorded in the AD itself, the practical legal points to note from the instrument are: it is an explicit directive issued by the regulator; it sets a clear compliance obligation and deadline; and it makes use of a manufacturer’s mandatory service bulletin. None of those facts in the AD text indicate any legal dispute or contested administrative decision within the contained record. If disputes were to arise in practice,over costs, timing, or alternative methods of compliance,those would likely emerge in administrative correspondence or separate legal proceedings, none of which are reflected in the AD text provided.

Several practical "gotchas" and traps for the unwary are embedded in the text and its structure. These are matters that operators and maintainers should look for when applying the AD:

• Version identification is decisive. The AD makes compliance turn on the transponder software version. Operators must identify the exact installed software revision. Versions 3.00, 3.01, 3.02, 3.04, 3.05 are specifically required to be upgraded to at least 3.06; version 3.03 is recorded as requiring no action. An operator who misidentifies the installed version can either (a) perform unnecessary work or (b) fail to comply. The AD also records that 3.03 is no longer available from Garmin. That creates an unusual status where a version that is acceptable for compliance cannot be sourced, potentially complicating maintenance strategies in the event of hardware replacement or reinstallation needs.

• Version 3.04 and 3.05 removed the prior correction. The AD states (as advised by Garmin) that versions 3.04 and 3.05 inadvertently removed the correction that was intended to prevent suppression of replies to S1 pulses below the Minimum Trigger Level. That means that simply having upgraded in the past to a 3.04 or 3.05 release could place an aircraft in the non-compliant category unless further upgraded to 3.06. Operators who recall having upgraded in 2004 may mistakenly assume that the upgrade addressed the issue, yet the AD makes clear that certain mid-era upgrades reintroduced the problem.

• Extensive applicability list. The directive contains a very long list of aircraft makes and models on which the subject transponders may be installed. The list contains repeated model entries and a range of legacy types. The practical effect is that operators must check equipment fit and not infer exemption based on aircraft age or manufacturer alone. The listing is comprehensive and includes types many operators may not immediately think are affected.

• Manufacturer service bulletin is mandatory method. The AD requires compliance "in accordance with Garmin Mandatory Software Service Bulletin No. 0409 dated 19 July 2004." If the service bulletin specifies particular procedures, tools, or authorisations, those become regulatory steps for compliance. Operators should not assume any alternative maintenance procedure is compliant without regulatory approval.

• Cross-reference to FAA AD: a parallel FAA AD is referred to by the text, which could create confusion about whether the FAA or CASA text governs for a given operation. For Australian-registered aircraft, the CASA AD is the controlling instrument, but the inter-reference means operators should read both instruments for completeness.

• No enforcement details in the AD. The AD does not set out penalties or an administrative enforcement mechanism within its own text. That silence can produce uncertainty about the precise consequences of non-compliance and about processes for obtaining an extension or an alternative method of compliance. Operators needing that certainty must consult CASA’s regulatory framework outside of the AD text.

• Compliance deadline is fixed and historical. The AD sets a deadline of before 30 September 2005. While that date is now historical, the presence of a fixed deadline means that this AD was intended for prompt action and that any aircraft that had not been upgraded by that date would have been non-compliant. Practitioners reviewing this AD now should check whether subsequent directives, supersessions or records indicate completion or later changes.

• Note that 3.03 is acceptable but unobtainable. The very practical issue that an acceptable version is "no longer available" from the manufacturer is a gotcha for maintenance planning, particularly when considering traded-in, overhauled or replacement transponders which may not be available in the exempt version.

• Typographical and list redundancies. The aircraft listing contains duplicated entries and long sequences that may be difficult to parse. Users must exercise care when matching their aircraft type to the list; failure to detect a matching model because of a typographical irregularity would not excuse non-compliance.

The AD prescribes the procedure for compliance in a concise manner and points to the manufacturer’s document as the required method. Practical steps drawn from the AD text are as follows:

1. Identify equipment and version: Determine whether the affected aircraft has a Garmin GTX 33, GTX 33D, GTX 330 or GTX 330D Mode S transponder installed. Check the installed software version number. The AD specifies the exact versions that trigger mandatory upgrade: 3.00, 3.01, 3.02, 3.04 and 3.05. If the unit is on version 3.03, the AD states no further action is required.

2. Consult the mandated procedure: If the installed version is in the list requiring upgrade, obtain and follow Garmin Mandatory Software Service Bulletin No. 0409 dated 19 July 2004. The AD makes the service bulletin the required method for performing the software upgrade, so the operator must follow the bulletin’s steps, use the tools and processes it specifies, and ensure any required maintenance release or test is completed in accordance with that bulletin.

3. Schedule maintenance and minimising downtime: Arrange for a qualified avionics maintenance organisation to perform the software upgrade before the compliance deadline. The AD fixed the deadline as before 30 September 2005 for this amendment; while that date is historical, the practical step is to perform the upgrade promptly upon identification of affected versions. Ensure the maintenance organisation documents the work in the aircraft maintenance records and issues the appropriate release to service.

4. Documentation: Retain all records evidencing the software version prior to upgrade, the Garmin service bulletin reference, the date of upgrade, the identity of the maintenance organisation and the maintenance release to service. The AD invokes the manufacturer’s service bulletin and, in airworthiness practice, documentary evidence demonstrating compliance is the primary record relied upon by regulators and auditors.

5. Cross-check with FAA AD: Because the AD refers to FAA AD 2005-01-19, obtain and review the FAA AD to confirm technical alignment and any additional steps or reporting the FAA may require. For aircraft that operate internationally or under multiple jurisdictions, satisfying both CASA’s AD and the FAA AD may be necessary.

6. Post-upgrade verification and continued airworthiness: After the software upgrade to at least 3.06, perform any post-installation tests specified by Garmin SB No. 0409 to verify reply performance, especially with respect to S1 pulse response and TCAS interaction. Keep the results with the maintenance documentation.

7. If uncertainty or an alternative method is needed: The AD text contains no alternate method of compliance or appeal process. If an operator believes an alternative method should be accepted, they must contact CASA directly to obtain an approved Alternative Method of Compliance or a formal ruling. The AD itself does not set out the process; practitioners should use CASA’s standard channels for AD queries and for seeking exemptions or alternate compliance mechanisms.

8. Inform operational and flight crew where relevant: If the transponder upgrade affects dispatchability or requires immediate grounding until the upgrade is completed, ensure operational procedures and flight crew are informed. The AD ties the upgrade to safety concerns that affect TCAS advisories and vertical separation; accordingly, inform relevant safety and operations personnel.

9. Maintain awareness of manufacturer availability and parts: Note that the AD states version 3.03 is no longer available from Garmin. If an operator’s maintenance plan contemplated reverting to 3.03, that will not be feasible. Coordinate with Garmin or an authorised Garmin service facility for access to version 3.06 and confirm any necessary licences or authentication steps for software installation.

Following the steps above aligns an operator with the directive’s requirements: identify equipment, upgrade per Garmin SB No. 0409 where required, record and retain evidence, and consult CASA where alternative compliance is needed. The AD binds the operator to the service bulletin as the method of compliance, so adherence to the manufacturer’s installation and test procedures is essential.