Pardon me, but this is the kind of bull**** that's killing GA

A.Coleman wrote:
Please read this. This is what's killing GA and we ought to do something
about it.


http://www.cdapress.com/articles/200...ews/news04.prt

I've read the accident reports on this one. The controller screwed up
big on this. Yes you can take the philosophy that the controller is always
trying to kill you and question every instruction he gives you, but there's
no indication that doing that is inherently safer in the long run either.

Yes, the controller errored in not following procedure on the altitude
snitch alarm (it's there for more than just dinging us pilots for
busting an altitude), but interestingly we have no information about
why the other airplane did not question who else answered to his tail
number... And how did the other airplane get down if he didn't take the
controllers instructions?... In controlled airspace I try to be alert
to similar tail numbers...

And, don't be too worried about Uncle Sam getting sued, he's got your
money to pay it with...

denny

"Denny" wrote in message
oups.com...

Yes, the controller errored in not following procedure on the altitude
snitch alarm (it's there for more than just dinging us pilots for
busting an altitude), but interestingly we have no information about
why the other airplane did not question who else answered to his tail
number... And how did the other airplane get down if he didn't take the
controllers instructions?... In controlled airspace I try to be alert
to similar tail numbers...


That was not the only ATC error. When similar callsigns are on the
frequency the controller is supposed to use full callsigns and alert each
pilot of the situation.

Steven P. McNicoll wrote:
That was not the only ATC error. When similar callsigns are on the
frequency the controller is supposed to use full callsigns and alert each
pilot of the situation.

I've had fun with that. My club owns Archer 17AV. There is also a
Archer 117AV in the area. One day I'm just about to call up NY
Approach returning to HPN when 117AV beats me to it and checks in,
same destination. It took me a while to get the controller to
understand that he hadn't just heard the callsign wrong, and there
really were two of us.

Denny wrote:
Yes, the controller errored in not following procedure on the
altitude
snitch alarm (it's there for more than just dinging us pilots for
busting an altitude), but interestingly we have no information about
why the other airplane did not question who else answered to his tail
number...

snip

Simple, the abbreviated callsign used by the controller was the
correct one for both airplanes (four papa alpha). How would either
airplane know which one the controller was talking to. In the accident
pilot's defense, he did read back with his full callsign and the
controller missed that as well. I'd say the controller had some
responsibilty in this one.

As for the Jacksonville crash, I've read the NTSB report on that one
and I agree with the OP. It was a money grab. The pilot lost it on
missed approach at 1,000 ft. supposedly it was caused by the tower
controllers giving the pilot an altimeter setting that was .03" Hg off.


John Galban=====N4BQ (PA28-180)