Content deleted Content added
m Text markup mismatch |
GreenC bot (talk | contribs) Reformat 2 archive links. Wayback Medic 2.5 per WP:USURPURL and JUDI batch #27al |
||
| (43 intermediate revisions by 26 users not shown) | |||
Line 1:
{{short description|Aircraft collision avoidance system}}
A '''traffic alert and collision avoidance system''' ('''TCAS'''), pronounced {{IPAc-en|ˈ|t|i:|k|æ|s}}
[[File:Tcas EU-Flysafe.jpg|thumb|upright=1.14|Combined TCAS and [[Horizontal situation indicator|EHSI]] cockpit display (color)]]
In modern [[glass cockpit]] aircraft, the TCAS display may be integrated in the
[[File:TCAS Indicator.jpg|thumb|upright=1.14|Combined TCAS and [[Variometer|VSI]] cockpit display (monochrome)]]
Line 10:
== Impetus for a system and history ==
{{for|more examples|Category:Mid-air collisions}}
Research into collision avoidance systems has been ongoing since at least the 1950s, and the airline industry has been working with the [[Air Transport Association of America]] (ATA) since 1955 toward a collision avoidance system. [[ICAO]] and aviation authorities such as the [[Federal Aviation Administration]] (FAA) were spurred into action by the [[1956 Grand Canyon mid-air collision]].<ref name=TCAS71>
Although [[Air traffic control radar beacon system|ATCRBS]] airborne transponders were available, it
A short time later, prototypes of TCAS II were installed on two [[Piedmont Airlines]] [[Boeing 727]] aircraft, and were flown on regularly scheduled flights. Although the displays were located outside the view of the flight crew and seen only by trained observers, these tests did provide valuable information on the frequency and circumstances of alerts and their potential for interaction with the [[Air traffic control|ATC]] system. On a follow-on phase II program, a later version of TCAS II was installed on a single Piedmont Airlines Boeing 727, and the system was [[Airworthiness certificate|certified]] in April 1986, then subsequently approved for operational evaluation in early 1987. Since the equipment was not developed to full standards, the system was only operated in [[visual meteorological conditions]] (VMC). Although the flight crew operated the system, the evaluation was primarily for the purpose of data collection and its correlation with flight crew and observer observation and response.<ref name="20-151B" />
Later versions of TCAS II manufactured by [[Bendix Corporation|Bendix]]/King Air Transport Avionics Division were installed and approved on [[United Airlines]] airplanes in early 1988. Similar units manufactured by Honeywell were installed and approved on [[Northwest Airlines]] airplanes in late 1988. This limited installation program operated TCAS II units approved for operation as a full-time system in both visual and [[instrument meteorological conditions]] (IMC) on three different aircraft types. The operational evaluation programs continued through 1988 to validate the operational suitability of the systems.<ref name="20-151B" />
=== Incidents ===
The implementation of TCAS added a safety barrier to help prevent [[mid-air collision]]s. However, further study, refinements, training and regulatory measures were still required because the limitations and misuse of the system still resulted in other incidents and fatal accidents, which include
* [[1996 Charkhi Dadri mid-air collision]] accident over [[New Delhi]]
* 1999 Lambourne near-collision, involving a [[Boeing 737 Classic#737-300|Boeing 737-300]] and a [[Gulfstream IV]]. The airspace above [[Lambourne]] is the waiting zone for [[Heathrow Airport|Heathrow]]. The event is notable as both planes entered the zone from different directions leading to an imminent head-on collision (one o'clock position). The traffic advisory (amber mark)
* [[2001 Japan Airlines mid-air incident]]
▲* [[2001 Japan Airlines mid-air incident]]; where the Captain of Japan Airlines Flight 907 (a [[Boeing 747-400]]), 40-year old Makoto Watanabe ({{lang-ja|渡辺 誠|translit=Watanabe Makoto|label=none}}), chose to descend, ordered by the air traffic controller, when TCAS told the flight crew to climb, nearly colliding with the descending JAL Flight 958 [[McDonnell Douglas DC-10|DC-10]] en route from [[Gimhae International Airport|Busan]] to Tokyo's [[Narita International Airport|Narita Airport]].
* [[2002 Überlingen mid-air collision]], between a [[Boeing 757]] and a [[Tupolev Tu-154]], where the Tupolev pilots declined to follow their TCAS resolution advisory (RA), instead following the directions of the air traffic controller, while the Boeing pilots followed their TCAS-RA, having no ATC instruction.
* 2006 collision between [[Gol Transportes Aéreos Flight 1907]] (a [[Boeing 737]]) and an [[Embraer Legacy 600]]; the Embraer's transponder had inadvertently been switched off, disabling its own TCAS and rendering the plane invisible to the TCAS on board flight 1907.
Line 32 ⟶ 31:
=== System description ===
TCAS involves communication between all aircraft equipped with an appropriate [[transponder (aviation)|transponder]] (provided the transponder is enabled and set up properly). Each TCAS-equipped aircraft interrogates all other aircraft in a determined range about their position (via the 1030 [[MHz]] [[radio]] [[frequency]]), and all other aircraft reply to other interrogations (via 1090 MHz). This interrogation-and-response cycle may occur several times per second.<ref name=TCAS70>
The TCAS system builds a three dimensional map of aircraft in the airspace, incorporating their range (garnered from the interrogation and response round trip time), altitude (as reported by the interrogated aircraft), and bearing (by the [[directional antenna]] from the response). Then, by [[extrapolating]] current range and altitude difference to anticipated future values, it determines if a potential collision threat exists.
TCAS and its variants are only able to interact with aircraft that have a correctly operating [[Aviation_transponder_interrogation_modes|mode C or mode S]] transponder. A unique 24-bit identifier is assigned to each aircraft that has a mode S transponder.
Line 43 ⟶ 42:
[[File:ACAS Protection Volumes Diagram.svg|TCAS Volume|center]]
{| class="wikitable"
|+ Symbols used to depict nearby traffic on cockpit displays
|-
| style="color: aqua" | ◇
| Distant traffic
|-
| style="color: aqua" | ◆
| Traffic within 6 NM horizontally and 1200 feet vertically
|-
| style="color: gold" | ●
| Traffic close enough to trigger TA, within 40 seconds of potential collision
|-
| style="color: red" | ■
| Traffic close enough to trigger RA, within 25 seconds of potential collision
|}
=== System components ===
A TCAS installation consists of the following components:<ref name="TCAS70" /><ref name="TCAS71" />
;TCAS computer unit: Performs airspace surveillance, intruder tracking, its own aircraft altitude tracking, threat detection, resolution advisory (RA) manoeuvre determination and selection, and generation of advisories. The TCAS
;Antennas: The antennas used by TCAS II include a directional antenna that is mounted on the top of the aircraft and either an omnidirectional or a directional antenna mounted on the bottom of the aircraft. Most installations use the optional directional antenna on the bottom of the aircraft. In addition to the two TCAS antennas, two antennas are also required for the Mode S transponder. One antenna is mounted on the top of the aircraft while the other is mounted on the bottom. These antennas enable the Mode S transponder to receive interrogations at 1030 MHz and reply to the received interrogations at 1090 MHz.
;Cockpit presentation: The TCAS interface with the pilots is provided by two displays: the traffic display and the RA display. These two displays can be implemented in a number of ways including displays that incorporate both displays into a single, physical unit. Regardless of the implementation, the information displayed is identical. The standards for both the traffic display and the RA display are defined in DO-185A.<ref name=DO-185>[http://adsb.tc.faa.gov/SC-147.htm FAA DO-185 Materials and RTCA SC-147 Activities] {{webarchive|url=https://web.archive.org/web/20110507002355/http://adsb.tc.faa.gov/SC-147.htm |date=2011-05-07 }}</ref>
Line 72 ⟶ 87:
* Clear of conflict
When a TA is issued, pilots are instructed to initiate a visual search for the traffic causing the TA. If the traffic is visually acquired, pilots are instructed to maintain visual separation from the traffic. Training programs also indicate that no horizontal maneuvers are to be made based solely on information shown on the traffic display. Slight adjustments in vertical speed while climbing or descending, or slight adjustments in airspeed while still complying with the ATC clearance are acceptable.<ref name=DOC9863-6>
When an RA is issued, pilots are expected to respond immediately to the RA unless doing so would jeopardize the safe operation of the flight. This means that aircraft will at times have to manoeuver contrary to ATC instructions or disregard ATC instructions. In these cases, the controller is no longer responsible for separation of the aircraft involved in the RA until the conflict is terminated.
Line 81 ⟶ 96:
The following points receive emphasis during pilot training:
* Do not
* Inform the controller of the RA as soon as permitted by flight crew workload after responding to the RA. There is no requirement to make this notification prior to initiating the RA response.
* Be alert for the removal of RAs or the weakening of RAs so that deviations from a cleared altitude are minimized.
Line 141 ⟶ 156:
| Shall respond immediately and manoeuvre as indicated, unless doing so would jeopardize the safety of the aircraft || Shall not attempt to modify the flight path of an aircraft responding to an RA
|- valign="top"
| Shall follow the RA even if there is a conflict between the RA and an
|- valign="top"
| Shall never manoeuvre in the opposite sense to an RA, nor maintain a vertical rate in the opposite sense to an RA || Shall acknowledge the report by using the phrase ''"ROGER"''
Line 164 ⟶ 179:
== Safety aspects ==
Safety studies on TCAS estimate that the system improves safety in the airspace by a factor of between 3 and 5.<ref name=ACASA>
However, it is well understood that part of the remaining risk is that TCAS may induce midair collisions: "In particular, it is dependent on the accuracy of the threat aircraft's reported altitude and on the expectation that the threat aircraft will not make an abrupt maneuver that defeats the TCAS Resolution Advisory (RA). The safety study also shows that TCAS II will induce some critical near midair collisions..." (See page 7 of Introduction to TCAS II Version 7 and 7.1 (PDF) in external links below).<ref name="TCAS70" /><ref name="TCAS71" />
Line 173 ⟶ 188:
Both cases have been addressed by Version 7.0 of TCAS II and are currently handled by a corrective RA together with a visual indication of a green arc in the IVSI display to indicate the safe range for the climb or descent rate. However, it has been found that in some cases these indications could lead to a dangerous situation for the involved aircraft. For example, if a TCAS event occurs when two aircraft are descending one over the other for landing, the aircraft at the lower altitude will first receive a ''"Descend, descend"'' RA, and when reaching an extreme low altitude, this will change to a ''"Level off, level off"'' RA, together with a green arc indication directing the pilot to level off the aircraft. This could place the aircraft dangerously into the path of the intruder above, who is descending to land. A change proposal has been issued to correct this problem.<ref name=CP116>[http://adsb.tc.faa.gov/TCAS/CPs/CP116.pdf Change proposal CP116] {{webarchive|url=https://web.archive.org/web/20110717003622/http://adsb.tc.faa.gov/TCAS/CPs/CP116.pdf |date=2011-07-17 }}</ref>{{update|date=April 2021}}
== Security aspects ==
TCAS was not designed with security in mind, even in its newest versions. With the rise of [[Software-defined radio|software-defined radios]], security researchers have investigated wireless attacks on TCAS. Researchers demonstrate<ref name="Usenix">{{Cite web|url=https://www.usenix.org/system/files/usenixsecurity24-longo.pdf|title=On a Collision Course: Unveiling Wireless Attacks to the Aircraft Traffic Collision Avoidance System (TCAS)|website=Usenix Security 2024}}</ref> how to take full control over the collision avoidance displays and create RAs of arbitrary aircraft on a collision course. These attacks can be launched using [[Commercial off-the-shelf|commercial off-the-shelf hardware]] and could be used to instruct the pilot to climb or descend at will. However, these attacks are only possible when the attacker is close to the victim aircraft (up to a distance of 4.2 km), limiting the risk of abuse in the real world.
== Relationship to Traffic Advisory System (TAS) ==
Line 188 ⟶ 206:
In spite of all this, most of the manufacturers do not take the above-mentioned opportunities to make simplified devices. As a result of market forces, many TAS systems operate just like TCAS I (with interference limiting, using TCAS I symbology, etc.), with some having even have better surveillance performance (in range and tracked aircraft) and specifications than TCAS I.
== Relationship to
[[Automatic dependent surveillance – broadcast]] (ADS–B) messages are transmitted from aircraft equipped with suitable transponders, containing information such as identity, ___location, and velocity. The signals are broadcast on the 1090 MHz radio frequency.
TCAS equipment which is capable of processing ADS–B messages may use this information to enhance the performance of TCAS, using techniques known as "hybrid surveillance". As currently implemented, hybrid surveillance uses reception of ADS–B messages from an aircraft to reduce the rate at which the TCAS equipment interrogates that aircraft. This reduction in interrogations reduces the use of the 1030/1090 MHz radio channel, and will over time extend the operationally useful life of TCAS technology. The ADS–B messages will also allow low cost (for aircraft) technology to provide real time traffic in the cockpit for small aircraft.<ref>{{cite web |url=http://www.duncanaviation.aero/straighttalk/adsb/tcas.php |title=TCAS 7.1 | ADSB Straight Talk |publisher=Duncanaviation.aero |date=2012-03-01 |access-date=2013-09-22 |url-status=dead |archive-url=https://web.archive.org/web/20130516094932/http://www.duncanaviation.aero/straighttalk/adsb/tcas.php |archive-date=2013-05-16 }}</ref>
Hybrid surveillance does not make use of ADS–B's aircraft flight information in the TCAS conflict detection algorithms; ADS–B is used only to identify aircraft that can safely be interrogated at a lower rate.
Line 197 ⟶ 215:
In the future, prediction capabilities may be improved by using the state vector information present in ADS–B messages. Also, since ADS–B messages can be received at greater range than TCAS normally operates, aircraft can be acquired earlier by the TCAS tracking algorithms.
The identity information present in ADS–B messages can be used to label other aircraft on the cockpit display (where present), painting a picture similar to what an air traffic controller would see and improving situational awareness.<ref>
== Versions ==
Line 205 ⟶ 223:
=== TCAS II ===
[[File:TCAS RA.png|thumb|An example of a resolution advisory (RA), where the pilot is requested to climb at 1,750 feet per minute to avoid nearby traffic (shown in red)]]
TCAS II is the first system that was introduced in 1989 and is the current generation of instrument warning TCAS, used in the majority of [[commercial aviation]] aircraft (see table below). A US Airways 737 was the first aircraft certified with the AlliedBendix (now Honeywell) TCAS II system. It offers all the benefits of TCAS I, but will also offer the pilot direct, vocalized instructions to avoid danger, known as a "Resolution Advisory" (RA). The suggestive action may be "corrective", suggesting the pilot change vertical speed by announcing, ''"Descend, descend"'', ''"Climb, climb"'' or ''"Level off, level off"'' (meaning reduce vertical speed). By contrast a "preventive" RA may be issued which simply warns the pilots not to deviate from their present vertical speed, announcing, ''"Monitor vertical speed"'' or ''"Maintain vertical speed, Maintain"''. TCAS II systems coordinate their resolution advisories before issuing commands to the pilots, so that if one aircraft is instructed to descend, the other will typically be told to climb – maximising the separation between the two aircraft.<ref name="TCAS71" />
As of 2006, the only implementation that meets the ACAS II standards set by [[ICAO]]<ref>
After the [[2002 Überlingen mid-air collision]] (July 1, 2002), studies have been made to improve TCAS II capabilities. Following extensive [[Eurocontrol]] input and pressure, a revised TCAS II Minimum Operational Performance Standards (MOPS) document has been jointly developed by RTCA (Special Committee SC-147<ref name=SC-147>{{Cite web |url=http://www.rtca.org/CMS_DOC/SC-147%20TOR%20Rev9%20-%20PMC%20Approved%20-%2006-10-2010.pdf |title=SC-147 Terms of Reference – Revision 9 |access-date=2011-08-28 |archive-url=https://web.archive.org/web/20110929020450/http://www.rtca.org/CMS_DOC/SC-147%20TOR%20Rev9%20-%20PMC%20Approved%20-%2006-10-2010.pdf |archive-date=2011-09-29 |url-status=dead }}</ref>) and EUROCAE. As a result, by 2008 the standards for Version 7.1 of TCAS II have been issued<ref name=SIRE>
TCAS II Version 7.1<ref name="TCAS71" /> will be able to issue RA reversals in coordinated encounters, in case one of the aircraft doesn't follow the original RA instructions (Change proposal CP112E).<ref name=CP112E>[http://adsb.tc.faa.gov/TCAS/CPs/CP112E.pdf Change proposal CP112E] {{webarchive|url=https://web.archive.org/web/20090109091211/http://adsb.tc.faa.gov/TCAS/CPs/CP112E.pdf |date=2009-01-09 }}</ref> Other changes in this version are the replacement of the ambiguous ''"Adjust Vertical Speed, Adjust"'' RA with the ''"Level off, Level off"'' RA, to prevent improper response by the pilots (Change proposal CP115).;<ref name=CP115>[http://adsb.tc.faa.gov/TCAS/CPs/CP115.pdf Change proposal CP115] {{webarchive|url=https://web.archive.org/web/20090109091245/http://adsb.tc.faa.gov/TCAS/CPs/CP115.pdf |date=2009-01-09 }}</ref> and the improved handling of corrective/preventive annunciation and removal of green arc display when a positive RA weakens solely due to an extreme low or high altitude condition (1000 feet AGL or below, or near the aircraft top ceiling) to prevent incorrect and possibly dangerous guidance to the pilot (Change proposal CP116).<ref name="CP116" /><ref name=EUROTCAS71>
Studies conducted for [[Eurocontrol]], using recently recorded operational data, indicate that currently{{when|date=July 2012}} the probability of a [[mid-air collision]] for each flight hour in European airspace is 2.7 x 10<sup>−8</sup> which equates to one in every 3 years. When TCAS II Version 7.1 is implemented, that probability will be reduced by a factor of 4.<ref name="EUROTCAS71" />
Line 218 ⟶ 237:
=== TCAS III ===
Originally designated TCAS II Enhanced, TCAS III was envisioned as an expansion of the TCAS II concept to include horizontal resolution advisory capability. TCAS III was the "next generation" of collision avoidance technology which underwent development by aviation companies such as [[Honeywell]]. TCAS III incorporated technical upgrades to the TCAS II system, and had the capability to offer traffic advisories and resolve traffic conflicts using ''horizontal'' as well as vertical
TCAS III attempted to use the TCAS directional antenna to assign a bearing to other aircraft, and thus be able to generate a horizontal maneuver (e.g. turn left or right). However, it was judged by the industry to be unfeasible due to limitations in the accuracy of the TCAS directional antennas. The directional antennas were judged not to be accurate enough to generate an accurate horizontal-plane position, and thus an accurate horizontal resolution. By 1995, years of testing and analysis determined that the concept was unworkable using available surveillance technology (due to the inadequacy of horizontal position information), and that horizontal RAs were unlikely to be invoked in most encounter geometries. Hence, all work on TCAS III was suspended and there are no plans for its implementation. The concept has later evolved and been replaced by TCAS IV.<ref name=skybrary>
=== TCAS IV ===
Line 227 ⟶ 246:
TCAS IV had replaced the TCAS III concept by the mid-1990s. One of the results of TCAS III experience was that the directional antenna used by the TCAS processor to assign a bearing to a received [[Transponder (aviation)|transponder]] reply was not accurate enough to generate an accurate horizontal position, and thus a safe horizontal resolution. TCAS IV used additional position information encoded on an air-to-air data link to generate the bearing information, so that the accuracy of the directional antenna would not be a factor.
TCAS IV development continued for some years, but the appearance of new trends in data link such as Automatic Dependent Surveillance – Broadcast ([[Automatic dependent surveillance-broadcast|ADS-B]]) have pointed out a need to re-evaluate whether a data link system dedicated to collision avoidance such as TCAS IV should be incorporated into a more generic system of air-to-air data link for additional applications. As a result of these issues, the TCAS IV concept was abandoned as [[Automatic dependent surveillance-broadcast|ADS-B]] development started.<ref name="sci_aeronautics" /><ref name=FAA_TCAS>
== Current implementation ==
Although the system occasionally suffers from false alarms, pilots are now under strict instructions to regard all TCAS messages as genuine alerts demanding an immediate, high-priority response. Only [[Airborne_wind_shear_detection_and_alert_system|Windshear Detection]] and [[Ground Proximity Warning System|GPWS]] alerts and warnings have higher priority than the TCAS. The [[Federal Aviation Administration|FAA]], EASA and most other countries' authorities' rules state that in the case of a conflict between TCAS RA and [[air traffic control]] (ATC) instructions, the TCAS RA always takes precedence. This is mainly because of the TCAS-RA inherently possessing a more current and comprehensive picture of the situation than air traffic controllers, whose [[radar]]/[[Transponder (aviation)|transponder]] updates usually happen at a much slower rate than the TCAS interrogations.<ref name="TCAS70" /><ref name="TCAS71" />
If one aircraft follows a TCAS RA and the other follows conflicting ATC instructions, a collision can occur, such as the July 1, 2002 [[Überlingen mid-air collision|Überlingen disaster]]. In this mid-air collision, both airplanes were fitted with TCAS II Version 7.0 systems which functioned properly, but one obeyed the TCAS advisory while the other ignored the TCAS and obeyed the controller; both aircraft descended into a fatal collision.<ref name=BFUAX001>
This accident could have been prevented if TCAS was able to reverse the original RA for one of the aircraft when it detects that the crew of the other one is not following their original TCAS RA, but conflicting ATC instructions instead. This is one of the features
Implementation of TCAS II Version 7.1 has been originally planned to start between 2009 and 2011 by retrofitting and forward fitting all the TCAS II equipped aircraft, with the goal that by 2014 the version 7.0 will be completely phased out and replaced by version 7.1. The [[Federal Aviation Administration|FAA]] and [[European Aviation Safety Agency|EASA]] have already published the TCAS II Version 7.1 Technical Standard Order (TSO-C119c<ref name=TSO-C119c>[http://rgl.faa.gov/Regulatory_and_Guidance_Library/rgtso.nsf/0/95b393711426c9c78625759b006481ea/$FILE/TSO-C119c.pdf FAA Technical Standard Order TSO-C119c]</ref> and ETSO-C119c,<ref name=ETSO-C119c>
[[ICAO]] has circulated an amendment for formal member state agreement which recommends TCAS II Change 7.1 adoption by 1 January 2014 for forward fit and 1 January 2017 for retrofit. Following the feedback and comments from airline operators, [[European Aviation Safety Agency|EASA]] has proposed the following dates for the TCAS II Version 7.1 mandate in European airspace: forward fit (for new aircraft) 1 March 2012, retrofit (for existing aircraft) 1 December 2015. These dates are proposed dates, subject to further regulatory processes, and are not final until the Implementing Rule has been published.<ref name="EUROTCAS71" />
Among the system manufacturers, by February 2010 ACSS<ref name=ACSS71>{{Cite web |url=http://www.acss.com/change71 |title=ACSS Change 7.1 for TCAS II |access-date=2011-08-27 |archive-url=https://web.archive.org/web/20110914103834/http://www.acss.com/change71 |archive-date=2011-09-14 |url-status=dead }}</ref> certified Change 7.1 for their TCAS 2000 and Legacy TCAS II systems,<ref name=ACSSTCAS>
=== Current limitations ===
Line 261 ⟶ 280:
* TCAS is not fitted to many smaller aircraft mainly due to the high costs involved (between $25,000 and $150,000). Many smaller personal business jets for example, are currently not legally required to have TCAS installed, even though they fly in the same airspace as larger aircraft that are required to have proper TCAS equipment on board. The TCAS system can only perform at its true operational potential once all aircraft in any given airspace have a properly working TCAS unit on board.
* TCAS requires that both conflicting aircraft have transponders. If one aircraft doesn't have a transponder, then it will not alert TCAS as there is no information being transmitted.
* Military aircraft may not be using TCAS. They could be operating with their transponders off based on their mission requirements.
To overcome some of these limitations, the FAA is developing a new collision avoidance logic based on dynamic programming.
Line 293 ⟶ 313:
|All commercial turbine-powered transport aircraft with more than 30 passenger seats (or MTOM above {{convert|33000|lb|kg|abbr=on|disp=or}})
|TCAS II
|1 January
|-
|Europe ([[European Aviation Safety Agency|EASA]])
|All civil turbine-powered transport aircraft with more than 30 passenger seats (or MTOM above 15,000 kg)<ref name="eurocontrol">
|TCAS II
|1 January 2000
Line 302 ⟶ 322:
|Europe ([[European Aviation Safety Agency|EASA]])
|All civil turbine-powered transport aircraft with more than 19 passenger seats (or MTOM above 5,700 kg)<ref name="eurocontrol" />
|ACAS II (Effectively TCAS II Version 7.1)
|1 March 2012
|-
|Europe ([[European Aviation Safety Agency|EASA]])
|All civil turbine-powered transport aircraft with more than 19 passenger seats (or MTOM above 5,700 kg)<ref name="eurocontrol" />
|ACAS Xa<ref>{{cite web|title=European legislation clears aircraft to fly with ACAS Xa collision-avoidance systems|url=https://www.flightglobal.com/safety/european-legislation-clears-aircraft-to-fly-with-acas-xa-collision-avoidance-systems/162070.article|date=2025-03-05|archiveurl=https://archive.today/20250305110955/https://www.flightglobal.com/safety/european-legislation-clears-aircraft-to-fly-with-acas-xa-collision-avoidance-systems/162070.article|archivedate = 2025-03-05}}</ref> or ACAS II (Effectively TCAS II Version 7.1)
|10 March 2025
|-
|Australia ([[Civil Aviation Safety Authority|CASA]])
Line 311 ⟶ 336:
|-
|Hong Kong ([[Civil Aviation Department (Hong Kong)|Civil Aviation Department]])
|All aircraft in Hong Kong with more than 9 passenger seats (or MTOM greater than 5,700 kg)<ref name="cad">
|TCAS II Version 7.0
|1 January 2000
Line 321 ⟶ 346:
|-
|Peru ([[Directorate General of Civil Aviation of Peru|Dirección General de Aeronáutica Civil]])
|All civil turbine-powered transport aircraft with more than 19 passenger seats (or MTOM above 5,700 kg)<ref name="RAP121K">
|ACAS II (Effectively TCAS II Version 7.0)
|1 January 2005
|-
|Argentina ([[National Civil Aviation Administration|ANAC]])
|All civil turbine-powered transport aircraft with more than 19 passenger seats (or MTOM above 5,700 kg)<ref>
|ACAS II (Effectively TCAS II Version 7.0)
|1 December 2014
|}
==Proposals==
[[Airbus]] and [[Honeywell]] have tested a proposed automated system, where if the pilot ignored a Resolution Advisory, the aircraft's autopilot would automatically take evasive action.<ref>{{cite news |title=Flying Safety Put on Auto-Pilot |url=https://www.wired.com/2003/08/flying-safety-put-on-auto-pilot/ |work=Wired News |date=12 August 2003 |access-date=21 December 2024 |url-access=subscription}}</ref>
== See also ==
Line 343 ⟶ 372:
== External links ==
{{commons category}}
* [https://web.archive.org/web/20090122222139/http://eurocontrol.int/msa/public/standard_page/ACAS_Startpage.html EUROCONTROL ACAS Website]
* [https://web.archive.org/web/20100421004001/http://www.eurocontrol.int/msa/public/standard_page/ACAS_Upcoming_Changes.html TCAS II Version 7.1]
* [http://www.allstar.fiu.edu/aero/TCAS.htm Discussion of TCAS] {{Webarchive|url=https://web.archive.org/web/20050831201200/http://www.allstar.fiu.edu/aero/TCAS.htm |date=2005-08-31 }}
* {{usurped|1=[https://web.archive.org/web/20070209222607/http://www.airsport-corp.com/adsb2.htm Critical discussion of TCAS using hypothetical abuse/exploit scenarios of TCAS usage]}}
* [http://www.faa.gov/documentLibrary/media/Advisory_Circular/TCAS%20II%20V7.1%20Intro%20booklet.pdf Introduction to TCAS II Version 7.1]
* [https://web.archive.org/web/20110612131435/http://www.eurocontrol.int/msa/gallery/content/public/documents/SIRE+_WP7_69D_v1.2.pdf Decision criteria for regulatory measures on TCAS II version 7.1]
Line 352 ⟶ 382:
* [https://web.archive.org/web/20120226205014/http://www.oilandgasuk.co.uk/downloadabledocs/284/c_Mark_%20Prior.pdf Collision avoidance on the UKCS (TCAS II Trial) by Mark Prior (Bristow)]
* {{cite news |url= https://leehamnews.com/2018/07/13/bjorns-corner-largest-navigation-change-since-radar-part-5/ |title= Bjorn's Corner: Largest navigation change since radar, Part 5 |author= Bjorn Fehrm |date= July 13, 2018 |work= Leeham News}}
{{Aircraft components}}
| |||