Automatic T?

[JRutledge]

Originally Posted by just another ref

You didn't tell us the "no way" part the first time. You're right again, that's about as automatic as it gets.

The "no way" part might have got them a technical, not necessarily the bouncing of the ball. And depending on the history of that kid during the game would have also helped to make that call.

Peace

[just another ref]

Originally Posted by JRutledge

The "no way" part might have got them a technical, not necessarily the bouncing of the ball. And depending on the history of that kid during the game would have also helped to make that call.

Peace

I would say it is the combination of the two things that makes this almost impossible to overlook.

[JRutledge]

Originally Posted by just another ref

I would say it is the combination of the two things that makes this almost impossible to overlook.

I did not say you overlooked it. I said it might not warrant a T. There are other ways to get players and coaches to stop behavior without calling a T. I do it all the time and it works most of the time without anyone noticing there was a problem in the first place.

Peace

[just another ref]

Originally Posted by JRutledge

I did not say you overlooked it. I said it might not warrant a T. There are other ways to get players and coaches to stop behavior without calling a T. I do it all the time and it works most of the time without anyone noticing there was a problem in the first place.

Peace

If a kid says "No way" and slams the ball on the floor so that it bounces 15 feet high, it warrants a T. I think people would notice this problem.

[JRutledge]

Originally Posted by just another ref

If a kid says "No way" and slams the ball on the floor so that it bounces 15 feet high, it warrants a T. I think people would notice this problem.

I do not know about you, but I do not sit around the court with a measuring tape to know if the ball went 15 feet (which is hyperbole on some level) or 8 feet.

In the NCAA Finals, the ball went higher than 10 feet if you judge the ball going over the rim and nothing was called. And the officials were commended by many officiating observers for understanding the situation.

Also I would like to talk to the officials to know if they heard or did not hear the kid said. Once again, there is a reason they passed on a T and I frankly do not like taking the words of only one person that may or may not have been in a position to see or understand what the officials were doing or what they were not doing. And that is most of all why I like to stay away from the "automatic T" stuff.

Peace

[mbyron]

2 scenarios:

(a) Kid gets called for a foul, he's obviously unhappy with the call, slams ball down, it bounces 15 feet high, he walks away. This earns a T from me.

(b) Close game, kid gets called for a foul, he knows he committed a dumb foul, he says "C'mon Smith!" (which is his name), he slams the ball down harder than he means to, he gets this "uh oh" look on his face, retrieves the ball and hands it to me. Probably no T here from me.

I suspect that (a) happens far more often than (b), but I agree with the general principle that technical fouls are almost never "automatic" but sometimes obvious and easy to call.

[Back In The Saddle]

Assuming that it happened just as the OP said, including the height of the bounce, I'm almost certain to have a T. It's just business. If another official chooses to handle it differently during his game, fair enough.

Coach Bill, there's no way we can pass judgment on why the officials in your game didn't T the kid for this. Without even trying I can rattle off half a dozen reasons why they might not have called it. Not the least of which is that they didn't see the situation the same way you did.

[BillyMac]

Originally Posted by mbyron

2 scenariosa) Kid gets called for a foul, he's obviously unhappy with the call, slams ball down, it bounces 15 feet high, he walks away. This earns a T from me.(b) Close game, kid gets called for a foul, he knows he committed a dumb foul, he says "C'mon Smith!" (which is his name), he slams the ball down harder than he means to, he gets this "uh oh" look on his face, retrieves the ball and hands it to me. Probably no T here from me.I suspect that (a) happens far more often than (b), but I agree with the general principle that technical fouls are almost never "automatic" but sometimes obvious and easy to call.

This sounds a lot like like a common sense. How dare you bring common sense into a discussion about NFHS basketball rules.

[Coach Bill]

Originally Posted by mbyron

2 scenarios:

(a) Kid gets called for a foul, he's obviously unhappy with the call, slams ball down, it bounces 15 feet high, he walks away. This earns a T from me.

(b) Close game, kid gets called for a foul, he knows he committed a dumb foul, he says "C'mon Smith!" (which is his name), he slams the ball down harder than he means to, he gets this "uh oh" look on his face, retrieves the ball and hands it to me. Probably no T here from me.

I suspect that (a) happens far more often than (b), but I agree with the general principle that technical fouls are almost never "automatic" but sometimes obvious and easy to call.

That is what I was trying to explain is that it was (a) in my case, and I've always seen a T called in that situation. But, there may have been mitigating circumstances that I was not privy to. I didn't push it. Made my comment, got my dirty look, and moved on.