AD/RAD/64 Amdt 1 - Skywatch SKY497

The Directive operates through a small set of technical and procedural mechanisms. First, it identifies a hardware failure mode: internal component failure within the Skywatch SKY497 can cause the system to present left/right reversed bearing information because the antenna configuration has effectively changed from top- to bottom-mounted. The operational hazard is misinterpretation of traffic relative bearing on the SKY497 display, creating an increased risk to situational awareness and collision avoidance. The background statement in the Directive explicitly links numerous reports of internal component failure to the potential hazard and to the operational symptom of target indications appearing on the incorrect side of the aeroplane.

Second, the Directive prescribes a human procedure, the “power-up procedures”, as an interim mitigant. By adding the FAA AD Appendix or the BFGoodrich Alert Service Bulletin into the Flight Manual’s limitations section, the regulator makes that power-up verification an official operating limitation, thereby transferring to the pilot the immediate duty to check antenna orientation whenever the system is powered. The Directive explicitly states that the power-up verification is required each time the system is powered up (Note 2). The procedure is therefore a repetitive, low-technology control aimed at capturing the failure condition before flight operations continue.

Third, the Directive sets a binary operational consequence: discovery of an incorrect antenna configuration during the power-up check triggers mandatory removal of the SKY497 from service until rectified (Requirement 2). This creates an enforcement mechanism that converts a detection of a safety-critical condition into an immediate grounding of that avionics unit and potentially the aircraft, until maintenance action has returned the system to conformity.

Fourth, the Directive recognises a technical fix path. It notes that the introduction of specific software versions , described in the Directive as version 16, 1.7 or 1.8 , implements an automatic verification at power-up which provides an “equivalent level of safety” to the Flight Manual limitation, allowing the Flight Manual statement to be removed. The Directive thus creates two compliance pathways: manual procedural verification enforced through Flight Manual limitations as an immediate mitigant, and a software-based automated verification that, once installed, obviates the manual limitation.

Finally, the Directive incorporates cross-jurisdictional material, by requiring insertion into the Flight Manual of a US FAA Airworthiness Directive appendix or a manufacturer service bulletin, and by explicitly referencing FAA AD 98-25-02 Amdt 39-10924. The Directive thereby treats foreign regulatory and manufacturer documents as the prescriptive content for the Flight Manual limitation.

These concepts establish a layered approach: immediate pilot check, mandatory removal if failed, and an engineering/software solution as the longer-term mitigation. The Directive is framed as an amendment to an existing AD first effective 24 February 1999, with the 2006 amendment introducing the software verification alternative while preserving the immediate operational limitation and removal requirement.

Directly affected parties are operators and owners of aircraft equipped with BFGoodrich Skywatch SKY497 units that have top-mounted antennas, and specifically the aircraft types identified in the Directive’s applicability table. The table lists manufacturers and series including Raytheon (Beech 90, 100, 200, 300), Cessna (172, 182, 206, 208, 210, 300, 400, 500 series), Piper (PA-23, PA-31-360, PA-31T, PA-32, PA-34, PA-42, PA-46), Hawker (HS-700, HS-800), Mitsubishi (MU-2), Dassault (F10), Mooney (M20), Bombardier/de Havilland (DHC-6), Westwind 1124, Bell 407, Eurocopter SA365, Socata TBM700. The Directive notes these models as known installations and explicitly states “applicability: BFGoodrich Avionics Systems Inc Skywatch SKY497 traffic advisory system installations with a top-mounted antenna”.

Operationally, the Directive imposes duties on pilots of affected aircraft, who must perform the antenna configuration verification at each power-up per the Flight Manual limitation (Note 2). Maintenance organisations and avionics technicians are affected because they will be responsible for adding the prescribed documentation to the Flight Manual as required by Requirement 1, and for installing any software upgrade versions that provide the automated verification. The Directive also affects operators’ flight operations and maintenance planning because discovering an incorrect antenna configuration requires immediate removal of the SKY497 from service (Requirement 2), which will likely involve maintenance downtime, troubleshooting and possibly replacement of the unit or antenna assembly.

Regulatory actors are implicitly implicated. The Directive was issued by a CASA delegate (James Coyne), which signals that CASA considers the matter to fall within Australian airworthiness oversight; CASA will be the regulator enforcing continuing airworthiness obligations that include compliance with Airworthiness Directives. The Directive also references FAA material and a BFGoodrich service bulletin, so foreign regulatory and manufacturer channels are engaged as sources of prescriptive content.

Indirectly affected parties include pilots’ training organisations and operators’ safety management systems, which will need to incorporate the new Flight Manual limitation and the repeated power-up check into recurrent training and standard operating procedures. Insurers and legal advisers to operators could be affected in that non-compliance with an AD is a relevant fact for risk allocation, but the Directive itself does not specify insurance consequences.

Finally, the Directive places a de facto economic burden on operators who choose not to adopt the software update path. Those operators must ensure pilots carry out the extra check every power-up and accept the risk of unscheduled removal of the unit from service. Operators choosing the software path will face costs to obtain and install the relevant software versions and to document the change, but the Directive explicitly recognises that installing the specified software versions provides an equivalent level of safety and permits removal of the Flight Manual limitation.

Duties created or restated by the Directive are compact and procedural. The immediate duty is to amend the Flight Manual limitations section to include a prescribed power-up procedure document, either the FAA AD 98-25-02 Appendix or BFGoodrich Alert Service Bulletin SB #78A dated 21 October 1998 (Requirement 1). The document states that insertion of a copy of either document into the limitations section of the Flight Manual accomplishes the task. This duty carries a specified compliance time, namely within 25 hours time in service from the effective date of the original Directive.

A continuing operational duty flows from the Flight Manual limitation: the pilot must verify the antenna configuration of the SKY497 at each power-up of the system (Note 2). This is framed as an operating limitation, which in aviation regulatory practice creates a mandatory operating constraint that must be observed as part of the aircraft’s approved Flight Manual. The Directive therefore converts a manufacturer/FAA power-up procedure into an Australian regulatory limitation.

A consequential duty is set out in Requirement 2: if the power-up check uncovers an incorrect antenna configuration, the SKY497 must be removed from service. The compliance requirement for this is “Prior to further flight”. The Directive thereby imposes a lock-step remedy: detection leads to cessation of use, and the unit is not to be used again until the incorrect configuration has been addressed.

The Directive also recognises an alternative compliance route. It states that certain software versions “provide an equivalent level of safety to this requirement and the statement may be removed form the flight manual.” The text identifies these software versions as 16, 1.7 or 1.8. Mechanically, this is a conditional right for operators: install the stated software, and the operator may remove the Flight Manual limitation because the software performs the verification automatically at power-up. The Directive thus creates two compliance pathways , a human-procedure pathway and a software-automated pathway , and grants operators the right to substitute the software solution for the manual limitation.

The Directive does not, in its text, set out enforcement penalties, specific approval or acceptance procedures for software installation beyond the statement of equivalence, or a requirement to notify CASA when the software is installed. It also does not specify who must perform the software update, or any certification paperwork for the installed software. The Directive does, however, set explicit timing and procedural requirements that are cast as mandatory: Flight Manual amendment within the compliance window, pilot verification at each power-up, and removal of a misconfigured unit prior to further flight.

Rights in the Directive are limited and implicit. Operators have the right to choose either prescriptive document to place in the Flight Manual, and the right to adopt the software alternative and then remove the Flight Manual limitation. There is no explicit carve-out for operations other than these two paths. The Directive makes clear that the software path is acceptable as an equivalent level of safety, thereby providing an authorised compliance choice.

The Directive itself does not state monetary penalties, criminal sanctions, or specific enforcement processes. It is presented as an Airworthiness Directive issued by the Civil Aviation Safety Authority delegate, and the text focuses on prescriptive compliance actions and timings (e.g. insert document into Flight Manual within 25 hours time in service, verify antenna configuration each power-up, remove unit from service if misconfigured). The document does not include a sanctions schedule.

In practice, Airworthiness Directives are regulatory instruments in the civil aviation framework, and non-compliance with an AD typically affects the continuing airworthiness status of an aircraft or component. The Directive here converts operational procedures into Flight Manual limitations, and failure to observe Flight Manual limitations generally has regulatory consequences under the wider aviation safety regime, for example scrutiny in compliance audits, potential grounding by the regulator, or administrative action. The Directive itself does not set those downstream enforcement steps or thresholds; those broader enforcement mechanisms are not detailed in the source document.

Operational consequences are explicit, and are themselves an enforcement mechanism of a sort. The Directive requires removal of any SKY497 that is discovered to be incorrectly configured during the prescribed power-up procedures, and removal is required prior to further flight. This immediate removal requirement operates to prevent continued use of a possibly dangerous unit, and therefore enforces safety through operational restraints rather than through a separate penalty clause.

Because the Directive references FAA AD 98-25-02 and a BFGoodrich Alert Service Bulletin as the prescriptive material to be placed in the Flight Manual, failure to include or to follow that material would be a failure to comply with the Directive. The Directive’s signatory is a CASA delegate, James Coyne, indicating CASA oversight and ultimate regulatory authority, but the AD text does not say how CASA will treat breaches or whether CASA will require reporting of detection events or rectifications. Those enforcement processes are therefore not specified in the source and would require reference to CASA’s broader enforcement and continuing airworthiness procedures not contained in this Directive.

Practically, operators should treat non-compliance as a regulatory risk because the Directive changes the Flight Manual and operational limitations for affected aircraft. The combination of a formal Flight Manual limitation and a mandatory removal requirement on detection creates a compliance obligation whose breach would likely be material in a regulatory or safety audit. The Directive itself does not list fines, remedial directions, or civil penalties, so any such consequences would derive from application of the broader regulatory framework rather than from the text of this AD.

The Directive explicitly cross-references foreign regulatory and manufacturer material. It requires insertion of FAA AD 98-25-02 Amdt 39-10924 Appendix or BFGoodrich Alert Service Bulletin SB #78A dated 21 October 1998 into the Flight Manual. This creates an interaction between CASA’s Australian AD and the FAA’s AD and the manufacturer service bulletin, effectively adopting the content of those documents into the Australian Flight Manual as limitations. The Directive also contains a Note 3 stating “FAA AD 98-25-02 Amdt 39-10924 refers”, which signals reliance on the FAA’s earlier finding and procedural prescription.

The Directive sits within Australia’s airworthiness oversight regime, issued by a CASA delegate, and thereby forms part of the continuing airworthiness obligations for Australian-registered aircraft. The source text does not recite specific Civil Aviation Regulations or instrument numbers beyond the AD itself, but the issuance by the CASA delegate implies that compliance with the Directive is part of an operator’s regulatory obligations under Australian aviation law. The source does not reproduce or quote wider Australian statutory provisions, therefore the precise statutory enforcement mechanisms are not contained in the document.

Operationally, the Directive modifies an aircraft’s Flight Manual limitations. Flight Manual limitations are part of the aircraft’s operating documentation and interact with pilot operating responsibilities, maintenance schedules, and the aircraft’s approved configuration. By requiring that the FAA AD Appendix or BFGoodrich SB be placed in the Flight Manual, the Directive ensures that the FAA-prescribed or manufacturer-specified power-up procedures become the operative requirement for pilots under Australian jurisdiction. That creates a direct content interaction: FAA/manufacturer technical material becomes an Australian Flight Manual limitation.

The Directive also interacts with manufacturer support and service channels. It recognises manufacturer software versions as an acceptable alternative remedy. The statement that software version 16, 1.7 or 1.8 provides an equivalent level of safety and allows removal of the Flight Manual limitation ties the compliance status to the software release history and installation validation that the manufacturer provides. That creates an interface between operator compliance obligations and the manufacturer’s software supply and installation processes.

There may be implied interactions with insurance, contractual warranties, and maintenance certifications, but the Directive does not address those explicitly. Any such interactions would depend on operators’ commercial arrangements, insurance policy terms and maintenance contracts. The Directive’s immediate legal content is limited to the prescriptive Flight Manual limitation insertion and the removal-from-service requirement when incorrect antenna configuration is detected.

Finally, the Directive supersedes or amends an earlier AD; the source states the original AD became effective on 24 February 1999 and that this is Amendment 1 (AD/RAD/64 Amdt 1). The amendment introduces the software verification option while preserving the Flight Manual procedural requirement. The exact interface between the original AD, the amendment, and any subsequent or parallel regulatory instruments would require examination of those other instruments; the current source sets out only the amendment’s text and dates.

The source itself documents a concise amendment history. The original Airworthiness Directive AD/RAD/64 was first issued and became effective on 24 February 1999. The document before you is Amendment 1, titled AD/RAD/64 Amdt 1, and it was prepared and signed by James Coyne, a delegate of CASA, on 9 November 2006. The amendment was made effective on 21 December 2006, as explicitly stated in the Directive.

Amendment 1 retains the original AD’s central operative actions , insertion of prescribed power-up procedures into the Flight Manual and the removal-from-service requirement on detection of incorrect antenna configuration , but introduces a material change: the amendment recognises specific software versions as providing an equivalent level of safety to the Flight Manual limitation, thereby permitting the removal of the Flight Manual statement where those software versions are installed. The text uses the phrasing “The introduction of software version 16, 1.7 or 1.8 provides an equivalent level of safety to this requirement and the statement may be removed form the flight manual.” That language establishes a technical-compliance alternative to the manual procedure.

The amendment also reaffirms compliance timings from the original Directive: the Flight Manual insertion must be accomplished “Within 25 hours time in service from the effective date of the original issue of Directive”, and removal of a misconfigured SKY497 is required prior to further flight. The amendment’s background paragraph expressly states why the amendment was needed, noting numerous reports to the FAA of internal component failure changing antenna configuration and the operational hazard of target indications being displayed on the incorrect side of the aeroplane.

The Directive text reproduces the applicability table listing aircraft makes and models known to have SKY497 top-mounted antenna installations. That list may not be exhaustive, as the applicability language is framed to apply to SKY497 installations with top-mounted antenna, and the table identifies types “known to be fitted to, but not limited to” those models.

No further amendments beyond Amendment 1 are recorded in the source. There is no reference in the document to subsequent modifications, revocations, or superseding directives in Australia. The amendment history available in the source is thus: original AD effective 24 February 1999, and Amendment 1 signed 9 November 2006 and effective 21 December 2006, with the principal change being recognition of software-based automatic verification as an equivalent compliance measure.

The Directive includes no references to cases, litigation, appeals or legal challenges. The source does not name any judicial or administrative decisions that interpret or test the AD. It does not cite precedent, nor does it record any enforcement action taken in relation to this Directive. The background information references “numerous reports” to the FAA about internal component failure, but these are presented as safety reporting and advisory inputs rather than as litigation or regulatory prosecutions.

Given the source material is an Airworthiness Directive issued by CASA, any legal disputes about its application, validity, or enforcement would likely have occurred, if at all, in the broader administrative law or civil aviation regulatory context. The Directive as printed does not include a record of such disputes. Therefore, based solely on this source, there is no litigation history to report.

Practitioners requiring the full litigation or enforcement history would need to consult CASA records, regulatory enforcement logs, or court and tribunal databases for any matters that arose after the issuance of this AD. The Directive itself provides no further data about appeals, reviews or contested decisions.

The Directive contains several points that create practical hazards of non-obvious compliance risk.

1. Scope language and the applicability table. The Directive applies to Skywatch SKY497 traffic advisory system installations with a top-mounted antenna, and the table lists aircraft “known to be fitted to, but not limited to” certain types. That phrasing means an operator should not rely on the table as exhaustive; any aircraft in the operator’s fleet with a SKY497 and a top-mounted antenna falls within the AD even if the particular airframe model is not listed. Operators who assume only listed types are affected risk non-compliance.

2. Choice of prescriptive documents. Requirement 1 allows either the FAA AD Appendix or BFGoodrich Alert Service Bulletin SB #78A into the Flight Manual. Operators must ensure they insert a full copy of one of those documents into the limitations section, not just a paraphrase or a short note. The Directive states explicitly “This task may be accomplished by inserting a copy of either document into the limitations section of the Flight Manual.” The exact text to be inserted is therefore the content of those documents.

3. Typographical and numbering anomalies. The Directive lists software versions as “16, 1.7 or 1.8”. That is heterogeneous numbering, and may reflect different numbering schemes for different product lines or revisions. Operators and maintainers should verify with the manufacturer which exact software releases correspond to these identifiers, and obtain written confirmation that the installed software is the version recognised by CASA as providing the “equivalent level of safety”. The Directive itself contains the phrase “the statement may be removed form the flight manual,” with “form” likely a typographical error for “from”. Such typos can cause confusion in field compliance unless clarified with the regulator or manufacturer.

4. Repetitive operational burden. The Flight Manual limitation requires the pilot to verify antenna configuration each time the SKY497 is powered up. Depending on operations, that can be a frequent task, and operators need to embed the check into SOPs and pre-flight flows to ensure consistent compliance. Failure to integrate the check into operating procedures risks missed checks and possibly flying with an incorrectly-configured unit.

5. Immediate operational consequence on detection. If an incorrect antenna configuration is found during the power-up procedures, the Directive requires removal of the SKY497 from service “Prior to further flight.” That means the aircraft may be grounded until maintenance can rectify the unit. Operators who do not have spare units or ready maintenance access may face significant disruption and cost. The Directive gives no allowance for ferry flights or alternative mitigation.

6. Software alternative requires verification. While the Directive permits removal of the Flight Manual limitation if the listed software versions are installed, it does not set out how installation is to be evidenced or recorded. Operators should ensure manifest documentation, maintenance release entries, and approvals are in place to demonstrate that the required software version is installed and operational, so that they are able to rely on the alternative compliance path if audited.

7. Interaction with non-Australian documentation. The Flight Manual limitation is to include a copy of a US FAA AD Appendix or a manufacturer’s service bulletin. Operators must ensure that they use the current and complete version of those documents and that any country-specific differences are reconciled. Relying on an incomplete or outdated version could leave an operator technically non-compliant with the Directive.

8. Timing and retrospective compliance. The compliance requirement for the Flight Manual insertion is “Within 25 hours time in service from the effective date of the original issue of Directive.” Practitioners should check the original AD’s effective date and confirm whether compliance windows were met historically, particularly if acquiring aircraft with SKY497 installations. The Directive itself reiterates that timing but does not record any extensions or exemptions.

9. Maintenance and certification paperwork. The Directive does not specify how the Flight Manual amendment should be recorded in the aircraft’s maintenance logs or who is authorised to perform the amendment. Operators should ensure that the amendment is recorded in accordance with normal regulatory practice for Flight Manual changes, and that maintenance personnel record any software upgrades with appropriate certification entries.

10. No explicit reporting requirement. The Directive does not require operators to report discovery of incorrect antenna configuration events to CASA, nor does it prescribe any post-removal test or return-to-service paperwork for the SKY497. Operators should assume that the standard continuing airworthiness reporting and return-to-service procedures apply, and confirm with CASA or their continuing airworthiness authority whether reporting is expected.

A practical compliance checklist drawn from the Directive and its operative text follows. Operators should apply internal governance and documentation controls to ensure auditable compliance.

1. Confirm applicability across the fleet. Identify all aircraft in your fleet that have BFGoodrich Skywatch SKY497 installations with top-mounted antennas. The Directive lists known types, but applicability is defined by the installation characteristic. Do not rely solely on the model list; inspect fleet avionics installations.

2. Obtain the prescriptive documents. Acquire FAA AD 98-25-02 Amdt 39-10924 Appendix “Power-Up Procedures for Skywatch SKY497 Installations with Top-Mounted Antenna” and BFGoodrich Alert Service Bulletin SB #78A dated 21 October 1998. Either document, when inserted into the Flight Manual limitations section, satisfies Requirement 1.

3. Amend the Flight Manual. Within the compliance window (the Directive reiterates “Within 25 hours time in service from the effective date of the original issue of Directive”), insert a copy of one of the two documents into the Flight Manual limitations section. Ensure the inserted document is complete and legible. Record the amendment in the aircraft’s documentation in accordance with your continuing airworthiness management procedures.

4. Update SOPs and training. Update pre-flight, start-up and power-up checklists to include the antenna configuration verification required by the Flight Manual limitation. Provide pilots and flight crew with training or a familiarisation brief to ensure they know how to perform the prescribed power-up checks and what to do if they detect incorrect configuration.

5. Implement the removal protocol. Establish a procedure that required removal of the SKY497 from service must be followed immediately if an incorrect antenna configuration is detected during power-up, and that no further flight is undertaken until the issue is rectified. Ensure maintenance, operations control and dispatch are aware of this immediate grounding criterion.

6. Consider the software alternative. Contact BFGoodrich or approved maintenance providers to obtain the software identified in the Directive , described in the AD as version 16, 1.7 or 1.8 , and verify with the manufacturer which specific release(s) correspond to these identifiers. Plan and budget for software installation and testing. Once installed and verified, document the installation and, where appropriate, remove the Flight Manual limitation in accordance with procedures for Flight Manual amendments, ensuring that all maintenance release and certification entries are completed.

7. Recordkeeping. Maintain maintenance entries that record Flight Manual amendments, software installations, and any removal-from-service events. If you remove the Flight Manual limitation after installing the recognised software, record the justification and evidence that the installed software provides the equivalent verification at power-up, including software serial or release numbers and installation certificates.

8. Maintenance response plan. Prepare a maintenance response plan for the case where incorrect antenna configuration is detected. The plan should cover fault diagnosis, unit replacement versus repair, availability of spare units, routing the aircraft to a maintenance facility, and estimates for downtime. The Directive requires removal from service but does not specify permitted remedial steps, so rely on certified repair or replacement paths in line with approved maintenance data.

9. Liaise with regulator and manufacturer for clarifications. Where the Directive text is ambiguous , for example with software version numbering or the precise form of Flight Manual wording to be inserted , obtain written clarification from CASA or from BFGoodrich. Keep those communications on file as part of your compliance evidence.

10. Audit and monitor compliance. Integrate verification of these steps into your safety management system and internal audits. Ensure pre-flight checks are observed and that pilots are not bypassing the power-up verification. Record any occurrences where the SKY497 is removed from service and review trends that may indicate broader fleet issues.

Following these steps will align operational practice with the Directive’s requirements. The Directive does not prescribe a formal notification to CASA for installation of the recognised software, but prudent operators will ensure their continuing airworthiness records demonstrate that the software alternative is installed and that the Flight Manual limitation was removed only after such installation and verification.