A tower-induced go-round

"Jay Honeck" wrote in message
ups.com...

Both of those statements are 100% true.


No they're not. You also said you were 1/2 mile out when the 172 touched
down 1500' from the threshold. If that's correct the controller judged the
spacing just fine.



What an incredible statement, from a guy who wasn't there. I'm
thankful you don't work for the NTSB.


No, I wasn't there. That's why I have to rely on your account. The problem
here is that your story does not support your conclusion. You have to
change one of them.



The controller should have done one of the two following things:

1. He should not have revoked my previously issued landing clearance
and cut the 172 in ahead of me.


According to your story there was adequate spacing to put the 172 ahead of
you, doing that does not revoke your previously issued landing clearance.



*or*

2. He should have ordered the 172 to land long, and keep it rolling.


Perhaps the controller isn't as comfortable telling pilots how to do their
jobs as you are telling controllers how to do theirs.

If your distances are accurate the 172 didn't need to land any longer than
he did. "Keep it rolling" is part of a normal landing, the pilot shouldn't
have to be told to do that.



Either choice would have worked out fine. He blew it, and did
neither. When he finally noticed the spacing issue, he ordered a go-
round.


Did the controller tell you that? Your story makes it sound like he ordered
the go around when he noticed the 172's unexpected stop on the runway.



In the end, it all worked out fine, and there was nothing unsafe about
it. But it was an unusual ATC lapse in judgement, which is why I
posted it.


If you're going to stick with your conclusion, that the controller misjudged
the spacing, you're going to have to put your plane closer to the threshold
when the 172 touches down.