Indeed. Search for ICAO Doc 8168 PANS-OPS.

thank you! Is that the only document which supports that claim or are there more, do you know?

Also i meant to ask, i have a document titled CAP413, do you know if this is accepted by either ICAO or EUROCONTROL as binding to all contracting states or is it a UK only material?

You may read this:

http://en.wikipedia.org/wiki/Traffic...oidance_System
http://www.caasd.org/work/project_de...fm?item_id=153
http://www.aerowinx.de/html/tcas.html

for those who want facts and please remember the conclusion:

http://www.eurocontrol.int/msa/galle..._21Apr2005.pdf

I have been installing and testing TCAS on several aircrafts and have to say that position accuracy is really not precise on the display, therefore follow the ATC instructions first and if there is a RA command then follow the TCAS vertical manoeuver!
Never use your TCAS display as a RADAR, it is not designed for that purpose!
The only way for TCAS to be fonctioning correctly is that everybody have to follow the same rules and procedures...if not there will be other cases to discuss...I am affraid

Carpediem: I always like those who have no time to read but want immediate answers,and now it includes future lawyers ! :E

The answer to your question is simple and was already given to you : ICAO PANS-OPS Doc 8168 : this is the bible that set the world standard and its current version says :
" Pilots shall follow the RA even if there is a conflict between the RA and an ATC instruction to manoeuver "
Now all the rest of the world regulations ( like the UK CAP, which , you are correct only applies in the UK ) and all airlines SOPs should reflect that standard. They might use other words , translations, etc,.. but that is the standard.
Please stay away from Wikipedia and other source of info, we are not at school making a project .

Airmen :
Caution not to mix up ACAS displays azimuth resolutions and RAs. That was not the question asked and your answer can confuse the non-initiated. Once an RA has started , the position Display is useless , Pilot concentraton should be on the VSI , not on the position display.
Before an RA , ( and that includes during a TA , pilots should indeed follow ATC instructions , but once the RA has started, pilots should follow the RA, even if it contradicts the latest ATC instruction.

That partially explains why still today only 70% of the RAs are correctly followed , 20% are ignored and worse, in 10% of the cases pilots still choose to manoeuver opposite to the RA.

The other part of the explanation as to why this is still the case were/are discussed here.

I will take that to be driven by the long-established hatred for my future proffession :p I had indeed read almost all posts yet i couldnt find what i was looking for.So i figured i'd post first before i finished my reading of all 9 pages of the thred ;)
And one more random comment: you have no idea how difficult it is to follow your posts with all these details and terminology, it sometimes feels as if i am reading chinese hehe.

Yep i did find the document and it is indeed what i was looking for. Am i correct that this document was not ammended as such before Ueberlingen? Hence if it indeed existed as such, fault could technically be attributed to the pilot who did not follow the RA, correct? Also, both the pilots of the aircraft, didn't they have to inform the ATC that there was a TCAS-descend for the one and a conflicting order for the other? I am not sure that i read something that clearly states so in the posts of the thread.

And one last question to ATC Watcher. I read in a few of your posts that when TCAS II came out, the manufacturing company for obvious liability reasons used the name advisory instead of command for the RA. Is there any document or article etc of the time that i can find this written on, or is it just a rumour/common knowledge in the world of the air?

Carpediem :
Not really, but after having been scr..wed a few times , relying on the ethics of your future profession could be assimilated to masochism...:E

Back to the subject : Correct > the old version was not clear and explicit about this situation. It was changed after Ueberlingen.
The Russian Pilots were not at fault technically as they followed ATC before the RA started. After that, according the rules published at the time , it was left to the pilot to judge to follow the RA or not .

Yes they had to : the B757 pilot did it, but very late ( after 23 seconds ) and that message was blocked out by another transmission, so the controller did not get it .The Tu154 pilot did not advise ATC, (fact) probably because they never followed the RA.( my supposition)

Not common knowledge but a fact stated at the beginning, but on whose insistence I do not know. The company that built the TCAS software is the MITRE Corporation , on contract from the FAA. whether it is the Manufactures, the FAA or the MITRE lawyers that insisted on the change I cannot say. The first manufacturers were both Allied Bendix and Sperry/Dalmo Victor. They might also have influenced the change of terminology . Check their web sites and ask questions if you want to pursue that question .
I would be personally very interested to have the answer if you find it. . ( you can PM me or post it here )

Good luck .

I just emailed them about it so they will reply soon i hope. Thank you very much for your help and i will get back at you if i have something :)

The B757 reported the RA to ACC Zurich, but the controller was working with another aircraft on another workstation, where he could not hear the B757 (or the TU154M).

You are Correct on the other workstation ( and the different frequencies ) I should have said "covered" instead of "Blocked". But the end result was the same.

For info to others , the other workstition was only 2,5m away and the controller could follow both transmissions and reply to them, but as the frequencies could not be collapsed together he had to go from one workstation to teh other to transmit. . The problem was that at the time the B757 called, the A320 also called and his call covered the 757 call.

One can find this in the report of the controller and on the communication/time chart published with the BFU report.

downlinking of RA
 

ATC watcher, it was still on my to-do-list to react to your statements about TCAS downlinking to ATC.
First, there may be an average of 29 seconds before a pilot informs ATC. But that does not mean that ATC is unable to become aware much earlier, when an aircraft deviates from its assigned level. At the most 9 seconds after the pilot's following the RA instruction, the climb or descent will become visible in the data block on the controller's screen. Visible, but the controller will only observe height readout if he happens to look to that particular spot on his radar screen. And in the case of a TCAS RA, chances are high that ATC has missed to see the development of a close encounter and consequently will not look to the spot where collision risk exists (because he is too busy elsewhere or because it's an unknown military or GA), unless a simple message from the TCAS RA downlink mechanism through Mode S draws his attention to it.

Second, in case of doubt wether the pilot follows the RA, ATC might ask. Might ask, because I am not sure the question is welcome at the flightdeck during those hectic and critical 29 nine seconds before the average pilot comes to informing ATC himself. But, to all intents and purposes, a simple question is much better than a contravening instruction from ATC which cannot be other then confusing.

Third, either ATC trust that pilots act in accordance with their SOP's and adhere to the RA, or we take it for granted that pilots ignore a potentially life-saving warning. Shouldn't we just agree that it is bad airmanship when pilots play around a TCAS RA. Ok, we know it happens, 10 % according to the study you quote. That means that there is still work to do at this front. But bad controllership also exists and I maintain that it is bad controllership if ATC prefer to ignore knowledge of RA's which affect the progress of a flight. Politique de l'autruche, the ostrich putting its head in the sand.

I'd think this debate is academic and by extension false argumentation. In the case of an RA, the provision of separation by ATC has failed (in the neutral sense of the word) and is replaced by the pilot taking ultimate responsibility for the safety of flight. The only action to be taken by controllers is... to refrain from any action, to shut up except for advising other aircraft in the vicinity which might be affected by the evasive action.

Finally, I must say that I have never understood the lax attitude of the controllers' international organisation IFATCA vis-a-vis the possibility of getting technical life-saving improvements, which could to a high degree prevent a collision from happening.

In the aftermath of the Uberlingen accident technical improvements remained limited to some improvent of procedures and airborne TCAS upgrades. This was necessary and useful, but we are still waiting to see ATC improvements that preclude ambiguity with RA instructions through downlinking of the RA. ATC administrations and airlines who have to pay the bill were wary of the financial implications. Uberlingen was quickly put back in their minds in favour of the rise in traffic figures, resultant capacity problems and cost reduction.

But the controllers had to get through the assassination of one of their colleagues. His recent acquittal by a Swiss court could not bring him back. Every TCAS RA event happening in their sectors reminds them of the shortcomings of the system. Yet, their representative body IFATCA, instead of putting pressure on their administrations to provide them with the best possible technical information about TCAS RA's, kept pressing on legalistic argumentation about responsibilities and accountabilities.

Carpediem,

I work with real lawyers on real aviation cases, amongst other things trying to keep real people out of jail. But my day job is with a university.

I think I can appreciate how difficult it is for people not in the field to understand complex technology. I have been in that position. My inclination is to do what it takes to understand all I have to know in order to make correct informed judgements (I am known for this, and people pay me for it occasionally). There is another way of dealing with things, followed by most experienced lawyers, which is to employ the right experts (that is where your judgement comes in) and believe (and have them transcribe for the court) what they say.

In a real court case, you would be offering ATC Watcher lots of money to say what he has to say. In a moot court, you are unfortunately faced with the first option: no matter how hard it is, you have to get your mind round the details.

[QUOTEcarpediem86]Hence if it indeed existed as such, fault could technically be attributed to the pilot who did not follow the RA, correct[/QUOTE]

That is, if I may say so, far too naive a stance for an putative aviation lawyer.

Obvious question, which should be the first one you ask as a lawyer: who has jurisdiction?

Answer: obviously Germany, since the airspace was German.

So you had better look up applicable German law. If you don't read German, you are lucky in this case in that the applicable German law is translated in the accident report from the BFU, which I may presume that you have read, as a lawyer.

You will therefore have observed that the advice about following RAs is not strictly identical with the advice in PANS-OPS 8168.

But Germany is an ICAO signatory. So which advice applies and why?

You will also observe that there is another applicable German law (which is more or less universal), which says that the airplane on the right (i.e., the Tu-154) has right of way. According to that regulation, your suggestion that
is not correct.

You're the lawyer. You sort it out.

Whoever suggested you work on this either had it in for you or thought you were a legal genius. It is certainly worth trying to sort out, but don't expect anyone here (or anywhere else) to have packaged answers for you.

PBL

Even without TCAS RA aircraft are allowed to deviate from their assigned flightlevel. Only if the deviation exeeds 200ft ATC can become aware of the deviation.

As the radarsystems updates the displayed information in intervals, the timespan between begin of the deviation and recognition by ATC can be several seconds.

Even with all these factors for delay, technically there are two institutions trying to control during a conflict situation (ATC and TCAS). These two obviously need to be coordinated in some way.

This need not be true in all cases. In the case of Ueberlingen, the TCAS RA was issued before the aircraft underrun the 7NM separation limit.

Thanks Peter, I am indeed too naive, Capediem was also asking me in PM a lot more questions ( which I gave him ) .
I realize now that I could perhaps make a living out of this !:O


Now answering songbird :

A lot of things to comment upon in your post.
The easy ones :
First : the 29 seconds is indeed an average. That means some are sooner , but some are also taking longer or missed altogether.
On the sooner ones, you say after 9 seconds max for a radar return, this is not universal . The Zurich radar return was 12 seconds in Ueberlingen for instance .
Also many controllers always wait the second Mode C update to verify trend , as many small deviations are just garbling or aircraft altitude hold variations.

Second : In doubt why not ask the pilot if he is following an RA. : Why not indeed . Just that in case of imminent collision, as a controller, you are more likely to want to issue avoiding instructions instead of loosing precious seconds asking the pilot if he has a functioning TCAS and if he is following an RA.

Thrid : ATC at the moment prefers to refrain from Downlinking RAs , not to ignore RA knowledge. On the contrary ATC urges pilots to report to ATC immediately if they are getting and following and RA. ( In Ueberlingen should the 757 crew had done so earlier , the outcome might ( emphasis on might ) have been different )

A little more info ( to confuse you even more ) on RA downlink to justify IFATCA ( and my own ) position on RA downlink:

A very recent Bretigny Survey of a single Mode S radar messages show the following picture :
90% of RA downlink messages are false RAs not displayed in the cockpit, but are broadcasted. . Half of those were identified as coming from a special transponder manufacturer on certain Boeing 737s ( 51 airframes identified so far , mostly on the UK register ) and a solution for those is expected.
The other half are short false RAs whose reason is not yet understood.
Of the 10% that remains, a further study indicates the following percentages : in 20% the pilots actions are inappropriate, in 10% pilots are acting in the opposite direction of the RA, and only 70% are more or less followed correctly. this confirms other larger studies both in Europe and in the USA.

Now to answer you final questions :
No, IFATCA on the contrary has the correct approach to this. They believe that hastily introducing RA downlink for the wrong reasons ( The Japanese pushed this in ICAO after their JAL/JAL encounter) while there are still so many issues unsoved will create more additional problems than it solves.

I for one believe that downlinking RAs Mode S messages at the moment will increase controller involvement and contribute to more confusion , or Ueberlingen type scenario.


This is a fundamental issue : valid for TCAS, but also for ADS-B and ASAS : Who is responsible for anti collision and when.

Nobody has resolved this issue yet and will resolve it soon I think.

For the moment I am responsible for anti collision TCAS is only a safety net that i should not take into consideration when I work. ( I am even not sure/ aware who has a functioning one ).
If the pilot is coming on the frequency and say "Moving , TCAS RA , " I Know my responsibility ends and he takes over . ..,I do not think any regulator will change this on account of RA downlink. So this is why IFATCA wants the legal bit solved before getting the Downlinks on their radar scopes. Also, based on the current surveys , Mode S RA messages are full or garbage anyway.

We are not putting our heads on the sand. We have been burned already by a hasty and immature introduction of version 6.04 ,often without training , in life traffic. We have had Ueberlingen, so time for the Regulators to take their responsibilities I would say. I support IFATCA 100% on this one .

The ball is in EASA and the FAA camp.

Joernstu wrote :
True for the 200 feet deviation, it's actually 299 feet. But a TCAS originated FL deviation will very soon get beyond 300 feet. I agree this has some impact on the time lapse before a controller could see the FL deviation without a TCAS RA downlink. But remember the context of my point. Because there is no attention getter related to the FL deviation, it is not very likely that the controller will see it because his attention is drawn somewhere else. What the controller needs is the attention getter in order that he can take the right measures, which normally will be to refrain from action vis-a-vis the RA affected aircraft.
Yes, several seconds, but always better than the average 29. In busy areas, with multiple ground radar antennes integrating the signals for display on the controller's radar screen, the delay is only two or three seconds.
Very well put, this is the heart of the matter. And it requires a good solution, see my further points to conclude that a good solution is achievable and is better than a do-nothing attitude, waiting for the best solution.
-
ATC Watcher wrote:
You put the 29 seconds and the 9 seconds in one basket but they apply to different magnitudes. The 29 seconds gives the average time lapse before pilots inform ATC on the radio, whereas the 9 seconds is, at least according to the Qinetiq study, the average radar return. My point was that on average there is 20 seconds to gain for getting the information where it is needed. Now on the detail, in Zurich 2002 the radar return was 12 seconds. However, the Swiss violated here the Eurocontrol standard of 8 seconds. I think this is mentioned in the investigation report but I haven't checked up yet.
As you will have read, I have my doubts myself, but it's better, or shall we say less harmful, to ask a question than a contravening and confusing instruction against TCAS.
Exactly, the instinct of a controller is to do as you describe. But the difficulty is that in the case of a TCAS RA, he should not follow his instincts any more. TCAS has taken over and the controller should act accordingly which in this case is to refrain from action, other than removing third party traffic. You will have seen my own hesitation to put up this possibility of asking the pilot. The main point is that the controller should, at the earliest possible time, be stopped from doing the wrong thing, that is to issue a contravening instruction which is so much confusing in the hectic situation of an RA.
So, connect the downlink to those RA's which are displayed in the cockpit. Problem solved.
A remaining problem indeed. As I said before, a lot of work remains to be done. On the detail again, it is not clear to me wether the '70 % more or less correctly' is of the total population, or only of the 10% that remains. If the latter is the case, then, logically, the real problem is only for 3 % of the TCAS total?
I don't think your statement is supported by the downlink simulations which were organised in Bretigny. Furthermore, how can knowledge, acquired by a downlink, be confusing. It is lack of knowledge and bad decisions taken based on a lack of knowledge, which is confusing. Not only in ATC but anywhere else. In this context but nothing to do with TCAS the Amsterdam crash of the El Al a/c flying into an appartment building springs to mind. The crew couldn't see what had happened with the engines which had fallen off, by this lack of knowledge they decided to turn in the wrong direction which caused the dramatic going down of the aircraft.
STCA (short term conflict alert, the ATC safety net) is only a safety net. I'm sure all area controllers take it into consideration when they work (admittedly, provided the number of false alerts is reasonable, but if this is the case management and technical staff should urgently repair the tool). Why should TCAS, as you say equally 'only a safety net', be treated differently when this is made possible? Why wait the average 29 seconds before it is taken into consideration anyway? I am pleading for improving the controller's situational awareness, rather than impeding. Improved situational awareness will improve his decision making, and not confuse. In my previous message I called this good controllership.
True. The first TCAS versions were introduced, pushed through even, without safety cases as to the impact on ATC. However, that's spilt milk, ATC has to live up to the situation and should embrace the improvement at hand, which brings the individual controller in a better position to apply his judgement when he gets involved in a horrifying RA situation.
I have noticed with satisfaction that you have put in bold 'for the moment'. That would seem to imply that you, and dare I say through you IFATCA, provide an opening to accept the downlinking of TCAS RA. You are right of course that the legal stuff should be solved. But the statement that the ball is elsewhere (what has the FAA to do with Europe, but that's another matter, I would think worldwide ICAO is the Ageny to address), alludes to a passive attitude from the side of IFATCA. Laxism may have been a too strong expression, but I would expect IFATCA to be active on this front. If it's only a few sentences in some documents to be changed : don't wait but go for it.

One scenario I can think of and where this would be problematic is a situation between one aircraft with transponder and TCAS and another without with ATC providing separation.

If aircraft 1 (the one with TCAS) for some reason deviates from its flightpath towards the flightlevel of aircraft 2 and almost simultaneously its TCAS transmits a bogous RA to ATC, the controller will not advice aircraft 1 to return to its flightpath as heshe would see the TCAS RA indication on the screen and could miss to recognise that aircraft 2 cannot be the cause for the RA.

So perhaps for downlinking TCAS RAs in addition to transmitting only real RAs (those issued to the crews), ATC would also need a database on all aircraft listing their transponder state. This database itself could introduce other failure scenarios.

The indication of TCAS RAs to the controller has to be correct 100% when it is made - or the indication should not be made at all.
Reason for this is, that no indication made at all will not change the current situation where ATC and TCAS simultaneous try to control the aircraft - not changing the current level of safety. TCAS RA indications to ATC which aren't 100% correct could lead to controllers acting as though they were 100% correct but in those cases where they aren't lead to dangerous or fatal situations - in extreme lowering the level of safety instead of improving it.

Songbird , here we go again :
A bit more in depth this time.

On the delay : .
Problem is that ATC using radar always look at the past. whether it is, 4, 9 or 12 seconds. TCAS is a very dynamic system, which can issue corrective RAs and whose version 7 can even issue corrective reversal RAs. Those, in order to be effective have to be followed by pilots within 2.5 seconds according the manufacturer manuals. We agree so far right ?
My point :
This will only happen in some particular situations, I agree, but in a mode S download situation what will be displayed to the controller on his screen will be totally different of what is happening in real time, hence increasing the possibility /likelihood of controller intervention.

On the technical downlink medium :This will mean re-encoding the displayed RAs and re-broadcasting them .I am not an engineer, but this will be complex and possibly expensive , and adding an avionic box is not the idea.
Also in Eurocontrol they have already decided that should we go for RA downlink , it ill be using the mode S broadcast. The cost of using the other (better) method of using the 1090 Extended squitter was judged prohibitive for that function only.

Replying to your question :
The 70% is within the initial 10% which are valid correct RAs. The rest is raw data , you cannot start to make percentages values on unvalidated data !

Increasing Controller involvement 2 :
Be careful in analyzing the outcome RADE simulations. the rather large RADE 1 was only a simulation on the HMI ( i.e the display) of RAs, and indeed most controllers there found the HMI adequate.
The 3 subsequent low-scale RADE simulations start to show another picture, and the 4th one ( RADE2T, only with 4 controllers from 2 APPs ) show the real limitations. The number of RAs shown to controller during those simulation was so low that I would refrain from drawing firm conclusions one way or another.
What I myself found interesting (and worrying),in those simulations is that despite this simulated environment, and the low numbers, on 2 occasions controllers intervened after an RA ! Training is still a major issue, also for controllers..

On the safety nets :
Ah, the old discussion between a safety tool and a safety net !
We could debate this for hours,. Short version : NO controllers should not use STCA and TCAS as safety tools. ( and they are trained and told not to )

Finally :
The FAA owns the TCAS system . Changes to its software and procedures have to be discussed with them trough RTCA. It is not a European system. ICAO do only issue SARPs for ACAS . They have no influence on TCAS.( and frankly no expertise either )

As an aside, I do not represent or talk for IFATCA here, but it happens that I agree with what they say on this particular point , which also happens to be very close to what the IFALPA ATS committee says by the way.

In a nutshell : No against Downlinking of RAs per se , but not now. Solve the problems first to make sure we will not add more problems than we want to solve, and increase, not decrease the likelihood of controller intervention .

Absolutely against introducing it now here and there to " see what happens" and " gain experience " etc...

Do all operators use TA/RA all the time?
Do any operators or countries allow for selecting TA only on , say, parallel runway approaches.

As far as I understand it is an FAA recommendation to consider TA only. Original Airbus manuals state TA or TA/RA AS RQRD with a note on the FAA stance.

My employer does not go any further and the accepted practice is always TA+RA. Never had any problems with parallel runway operations (not always approaches) in FRA, MAD, BCN, BRU, AMS, LHR, FCO, LED, SVO, OTP, HEL, MAN, OSL, CDG ... However, the runway spacing is not very tight and there is little or none GA/VFR traffic, which I suppose may be the main reason to select TA only above 800 ft on approach.

FD (the un-real)

I have had 2 RAs at DEN. Out of 5/6 visits this year.
On 1 occasion we were 4 across - to the 4 parallel rwys.
We had a/c on both sides, very close, gear down, and if we all reacted, or did full go-arounds, we would certainly lose sight of each other. And could I trust the software to cope with 3 or 4 simultaneous reactions?

As a followup......This quote was made by Joernstu earlier in this thread.
http://www.eurocontrol.int/msa/galle...n_9_Jul-07.pdf

I direct you to the Eurocontrol ACAS Bulletin #9 and quote...

"Five. The factor of collision risk reduction thanks to TCAS II in the operational world, taking into account some non TCAS II equipped aircraft, inaccurate pilot responses and lack of responses, altitude reporting inaccuracies, etc."

There have been some irresponsible statements made much earlier in this thread. It is rational to Follow The RA even if it contradicts an ATC instruction.