PPRuNe Forums - View Single Post - TCAS RA in VMC. Follow the RA or Not?
View Single Post
Old 20th Apr 2005, 11:20
  #16 (permalink)  
HighandWide
 
Join Date: Oct 2001
Location: Washington
Posts: 6
Likes: 0
Received 0 Likes on 0 Posts
TCAS as a system requires full compliance by all for it to be effective!
Yes its hard, especially for pilots who in general have a 'control' persona, to put their faith in a machine. But, lets keep it in context. There were many mid air collisions prior to TCAS, it is also a fundamental part of other systems and procedures, such as RVSM and FANS and therefore it is not really a option to remove it. It has undoubtedly saved more lives.
What is needed is for everyone to respond to TCAS in the same manner. This is why lives were lost in the DHL/Sibair collision.
So;
1) if you get an RA on an approach, respond to it even by a descending. The other aircraft will be climbing and the sooner you BOTH do it the sooner the conflict will clear, and the system is safeguarded by RAs being automatically disconnected below 700' radio height, to remove unwanted 'approach' proximaty alerts. I would be immensely surprised if you haven't been given a similar scenario in a sim check!
2) EGPWS terrain warnings etc have precedence over RA's, so you won't have a CFIT
3) RA's have precedence over ATC. Remember or familise yourself with your RT. 'Callsign, Climbing/Descending due TCAS' this removes ATC from the loop until, 'Callsign, clear of conflict'
4) Operate correctly, and not just for TCAS. Equipment is only as good and correct as the information given to it, by us. So always confirm you have the correct altimeter settings, and climb or descend less than 1000' per minute in the last 1000 feet of your climb and descent profiles (Very few of the pilots in my company regulary do this) to eliminate unwanted TCAS alerts.

To summaries, correct operation and compliance with TCAS by ALL is the safest and most effective system.

With regard the authorities, In there defense (and I am not one of them) the original terminology was written with the intent that it was a 'command'. However it was interpreted differently and this is what was tightened up after DHL/Sibair. In fact the Japan incident had already started to raise concerns, unfortunately nothing happens over night, which is what happened here, and unfortunately DHL/Sibair occurred before changes could be implemented.
HighandWide is offline