Quote:
Originally Posted by ajmc
Obviously, you are fully entitled to your opinion, but one of the most persistent MISTAKES people (including some officials) make when assessing a situation from viewing film/video, is ASSUMING that the view the camera has is the same view an official AT GROUND LEVEL (who is often OUTSIDE the film/video view) are the same.
Was the Umpire, in the op, looking at other players who may have been gearing up for a problem, was his view blocked by a mass of humanity between him and the players on the ground (for just a second). If you have NO IDEA what he was looking at, how can you honestly declare what he "should have been" looking at. It's also quite possible that the Umpire actually did vave a BETTER view of what happened and came to a different conclusion than you, based on what he ACTUALLY saw.
Even "facing" something can be quite different than "focusing on" that same something, or even "seeing" something when there are all sorts of things going on in the direction an Umpire may be looking. Even from the video, can you be sure the opponent didn't believe the ball was still loose and was reaching for it? Can you see him ACTUAL "poking in the eye"? Remember, we're not supposed to guess what happens, or surmise what likely happened, we're held to a higher standard of absolutely KNOWING what happened.
|
Agreed. The angle and the B player down next to the RB likely helped #32 get away with it (at the time). As stated, this was apparently a pretty chippy game and the U very well may have been cleaning up another issue or even separating two opponents on his way in to the ball on that play for all we know.
I think we all like to think we'd see that and yet we all know we don't see everything.
MN is 5 man mechanics in playoffs, correct?
My guess is this kid is sitting out of his BB or WR season for a bit.