![]() |
|
|
|||
Quote:
Last edited by DLH17; Fri Mar 26, 2010 at 09:36am. |
|
|||
Nope. Use the "incidental contact" definition right out of rule 4(both NCAA & NFHS). Jalons already gave you the NCAA cite--4-40; NFHS is 4-27.
|
|
|||
Quote:
Got it. Thanks. |
|
|||
I mentioned this in another thread, but I was linked here. (Thanks, grunewar.)
DLH17, I would have passed on it, too. Personally, I'm not sold that that initial contact was missed, either. While there was contact, the dribbler didn't appear to be hindered by it, and we all know the reason for the contact. I've seen coaches get mad at situations like this before. I'm sure it's happened to me once or twice. We all know why the K-State coach got mad, but I think that's part of the bigger problem. Should we accept this belief that the defense can stop the clock anytime they want, just because they're behind? Should we reward the defense with breaking the rules, just because they trail on the scoreboard? Some people think not to call this foul is "unfair." How can it be unfair to the defensive players, when they're the ones committing the infraction? |
|
|||
Quote:
My feeling is by simply "getting" that first contact, we actually have stopped officiating. Officiating is having to make those many decisions about what contact is incidental and what contact is a foul. If one team is trying to foul, and the other team kind of stands there, waiting to be fouled, then yes we can probably lower our threshold a little. But if that other team is purposely playing hard trying to avoid being fouled, then we have continue to officiate by making the same decisions about whether that contact is a foul at that point in the game as in the first half. Don't think of it as "unfair" to the team trying to foul that we may rule some contact incidental, and they have to keep trying. It is just as "unfair" to the team trying to run time off the clock and we stop it for a marginal play that wouldn't have been a foul earlier in the game. Should we know one team is trying to foul? Absolutely, but not to change what we call, but rather to know and be aware so it doesn't surprise us when it happens. In the context of the X/KS St. game, the T might tell us that he was straight-lined and wished he could've called that first contact. But my guess is he did see it, and chose to pass because the dribbler got passed the defender easily. If that exact play had happened in the first half, I don't think we would be talking about a "missed" call.
__________________
M&M's - The Official Candy of the Department of Redundancy Department. (Used with permission.) |
|
|||
Quote:
|
|
|||
Totally agree. This play is a case study for both coaches and refs. I also submit this play is tough because it has the crew spread, somewhat stacked (both behind and across) and on the run. If it's not obvious, I would argue 95% of the top 96 would have passed. I think I would have as well.
|
|
|||
The coach was on one of the morning shows this morning. If I heard correctly, the plan was for the defender to "bearhug" the dribbler. Apparently no concern of the intentional call? He went on to say how the first guy missed the foul, and the second came in "a little too late." He complimented the offensive player for getting the shot up under the circumstances.
__________________
I swear, Gus, you'd argue with a possum. It'd be easier than arguing with you, Woodrow. Lonesome Dove |
![]() |
Bookmarks |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
switch | fullor30 | Basketball | 13 | Fri Jan 23, 2009 03:37pm |
Should I Switch? | PIAA REF | Basketball | 27 | Fri Jan 16, 2009 12:38pm |
Switch-Hitter vs Switch-Pitcher | Jurassic Referee | Baseball | 39 | Thu Jul 03, 2008 01:06pm |
2 man OOB switch | OldCoachNewRef | Basketball | 14 | Thu Jan 20, 2005 08:53pm |
New NCAA mechanics - Long switch or no long switch? | jimcrket | Basketball | 5 | Mon Oct 15, 2001 01:40pm |