"Everett M. Greene" wrote in message
...
"Tarver Engineering" writes:
[snip]
ATC unions have blocked automation for 30 years, but it was not until
lately
that the catastrophic events generated by ATC seperation error became
the
majority of the total body count.

Could we be more specific? Air traffic separation incidents
resulting in a body count implies aircraft collisions. The
only one I can recall is a runway incursion error at LAX a
few years ago. Are there others?

The A-300 at Rockaway and USAir 427 have been identified by the
Administrator as seperation incidents. There is no need for a collision,
just proximity. Following too close can cause "flow separation" due to
turbulance and that flow seperation is known to have caused "rudder
reversal" for the A-300 at Rockaway. USAir 427 is a nearly identical event,
except there was no DFDR to prove the rudder reversed; but only the rudder
pedals pounded through the floor. The system paid a high price for 737
rudder PCU replacement, that was probably specious in nature.

Similar to small GA icing incidents. (ie rudder flow seperation)