![]() |
|
|
|
|||
|
Too late is too late. It's a tough call, and no doubt about it. I'd say in your situation, once the dribbler had turned, it was too late.
The trick to getting this call right is A1's "ability to play through". Sounds like there was the ability there, and B2 just took advantage of a "fumble". Whether or not to have called the bump originally would probably depend on the level of play, and the overall style of the game, and what else was being called. You probably got it right by not calling it. |
|
|||
|
I finished my response, and then read Rusty's. Funny that they're the exact opposite!! It just shows that there's lots and lots of judgment involved, and each situation is different. If I were you, I'd keep watching other refs games, and keep adding to your data bank. See how others call this amount of contact at the same level, in similar situations. Work on developing the instincts that might give you an automatic response that you can feel good about.
|
|
|||
|
Quote:
****I like your attitude. : > ) Although in hindsight I should have called it. I was going to get grief from one coach or the other so that was a wash but the steal surprised me as I didn't see him coming in to steal the ball. As I ran past Coach A he asked,...wasn't he bumped? I was busy running down with the layup but by the time I came back past him I realized what had happened and told him that I should have called it. But you live and learn. |
|
|||
|
Quote:
|
|
|||
|
Quote:
And, should the resulting layup count, or should he wipe that off? I think the question isn't whether or not it was a foul, but once he realizes it should've been called a foul, how long can you wait before calling it?
__________________
M&M's - The Official Candy of the Department of Redundancy Department. (Used with permission.) |
|
|||
|
Quote:
I dunno...it's going to look ugly either way. He was late on a foul call...does he want to compound the problem by letting the opposing team benefit TWICE because of the original non-call?
__________________
Dan Ivey Tri-City Sports Officials Asso. (TCSOA) Member since 1989 Richland, WA |
|
|||
|
Quote:
If the subsequent steal was fairly close to the original contact, you can come in with a late whistle and explain it away fairly easily. If the player hasn't recovered his balance yet from the bump, as he said in the op, then it certainly ain't too late. Call it as soon as the ball is stolen. |
|
|||
|
Quote:
I know I've had that brain-locked condition where you see the play, and think to yourself, "Someone should call something"; then you realize you're the one that should be calling something. So how much time should elapse before you just say, ok, now it's too late? I agree as soon as the ball is stolen is still ok. I also agree once the ball is stolen and the other team lays it in, that's too late. Does anyone have any "rule of thumb" as to when is it really too late to come in with a foul call? 2 steps? 2 seconds?
__________________
M&M's - The Official Candy of the Department of Redundancy Department. (Used with permission.) |
|
|||
|
Quote:
Being "too late" is, IMO, dependent on the game so far - what level is the play, how fast are the players, etc.
__________________
"To win the game is great. To play the game is greater. But to love the game is the greatest of all." |
![]() |
| Bookmarks |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Late Hit | bossman72 | Football | 11 | Wed Oct 25, 2006 04:26pm |
| Late Sub | foureyesallbad | Football | 9 | Wed Sep 27, 2006 07:32am |
| Too late for me, but.... | justacoach | Basketball | 10 | Mon May 29, 2006 01:28pm |
| Q2: Sorry I'm a day late. | VaASAump | Football | 15 | Thu Dec 09, 2004 10:10am |