Pilot deviations and a new FAA reality

"Steven P. McNicoll" writes:
"Chip Jones" wrote
[snip]
Folks, I see at *least* one pilot deviation a week working traffic in my
small slice of the NAS. I don't report them unless separation is lost,
because I was trained under the "no harm, no foul" mentality. Pilots help
controllers, controllers help pilots, and the NAS ticks along like an old
clock. I'm not changing the way I do business, but I wanted you to know
that other controllers might, in order to cover themsleves against
antagonistic Management.

Pilot deviations come in a variety of flavors. A pilot may bust his
altitude but if there's no other traffic around there's no hazard. No harm,
no foul, no loss of separation.

At the other extreme a pilot blowing a runway hold short as another aircraft
is about to touch down can be disastrous.

On what side of the line should be placed the situation where there was no
loss of separation only because an alert controller stepped in?

I thought the FAA was under the gun to gain better and more
info regarding runway incursions. It sounds as if a controller
may have been admonished/penalized/whatever for failure to make
a "required" report of a runway incursion, not just a simple
pilot deviation. It seems as if the cited incident was quite
serious even though the system worked and no untoward harm
came to any of the parties involved.

"Everett M. Greene" wrote in message
...

I thought the FAA was under the gun to gain better and more
info regarding runway incursions. It sounds as if a controller
may have been admonished/penalized/whatever for failure to make
a "required" report of a runway incursion, not just a simple
pilot deviation. It seems as if the cited incident was quite
serious even though the system worked and no untoward harm
came to any of the parties involved.


Yup, runway incursions has been the hot item for several years.