PPRuNe Forums - View Single Post - Standard of RT in USA
View Single Post
Old 16th Jul 2013, 17:34
  #177 (permalink)  
deefer dog
Join Date: May 2010
Location: europe
Age: 65
Posts: 644
To Hell Man, (and others who don't get the point of the thread),

This thread has NOTHING to do with who handles the most traffic, or who has the best safety record, or indeed who are the World's best Air Traffic Controllers! If you want to argue about these semantics, please start a separate thread and fight among yourselves until you are blue in the face, but please do not divert the thread away from its premise.

The ONLY point of the thread was to question why the vast majority of US operators and ATC operatives feel the need to make use of a completely different code of communicating when using RT than the rest of the World, and one that flies in the face of the Standards and Recommended Practices agreed by all ICAO Member States, including themselves.

If by now you don't understand the concept of ICAO, what its purpose is, who the members are, and how international agreements are decided upon, made and implemented, please read no further as you will never get the point I am trying to make here.

The unavoidable fact that many seem to miss here is that a committee including representatives of the US decided that standardization would be in the best interests of safety and the industry as a whole. They concluded that specific phraseology should be defined and used to direct traffic, and in doing so they created what are in effect SOPS for ATC and pilots. The sole purpose of standardizing the industry in this respect was to minimize the possibility of misunderstandings that could potentially lead to unsafe conflicts. Over time the SARPS have been amended - many of you will recall that we used to say "ready for take off" instead of today's "ready for departure," and in time I'm sure there will be more amendments incorporated as we learn from experiences (and phraseology) that lead to confusion. The point I am trying to make here is simple; ALL users of USA airspace need to understand what they and others are being instructed to do, just as US operators need to when flying outside of what may be their comfort zone.

If some of you still don't get it, consider how those of you in the US would feel if we in Europe started "tweaking" the way we light our airports. How about some of us choosing to use green centre line light bulbs if we run out of white ones, or just for the heck of it choose to space out the lights at different intervals, just because we can't be bothered to stick to the international agreements, or don't have the time during busy periods? Would you be confused, would it likely lead to a degradation of safety? Get my point? Well do you, Hell Man? So what possible argument do you have for discarding the internationally agreed SARPS in respect of ATC comms?

The argument put forward by some is just plain stupid, especially when talking about busy US hubs. Talking slang to a Chinese, Japanese or even Pikanese pilot is more likely to result in a request to "say again prease," if indeed its possible to get a word back in. Use of the correct phraseology in such cases will not only reduce misunderstandings, it will also expedite the traffic flow.

As for isolated instances of traffic conflicts, misheard comms, or simple cock ups, they serve no useful purpose in this thread. Pilots and controllers of all nations screw up from time to time. As the starter of the thread I would rather explore how we can all work together and make best use of the agreed standards, or, if some are to be believed, should we simply all go our own way and chat to each other in any way shape, form or language?

Standardizing ATC comms cannot be argued against, and its my opinion that the US needs to fall into line and follow the rules in the interests of IMPROVING on what is already their excellent safety record!

Last edited by deefer dog; 16th Jul 2013 at 17:45.
deefer dog is offline