![]() |
End of Giants-Redskins game
The NFL officials are doing a fantastic job of embarrassing themselves in primetime games this year.
They moved the chains after the 2nd down play and then decided after an incomplete pass on the next play that it was now 4th down. Ultimately I think they got it right in the end, in that they didn't have the yardage for a first down, but to do what they did is inexcusable. |
Yeah that was pretty bad.
The wing official at the top of the screen (Forget which sideline it was) had a spot that looked like a first down on the 2nd and 5 play. (Or was blatantly close enough to measure it) When the Umpire went to spot it, he looked at the other wing guy at the bottom of the screen which moved the spot back about half a yard. The moved the chains and the down box at the bottom of the screen and the down box showed first down, then after the incompletion they brought the chains back and put 4th down on the box. This was about as big of a screw up as the play earlier this year where the QB tried to center the ball and the crew let the clock run out and didn't let the offense run another play. |
I have a question from the game.
After replay of the Redskins touchdown where they were looking if the knee hit the ground or not....the white hat said "the play stands" instead of "the play is confirmed". Cris Collinsworth said this word choice is because they could not find evidence to overturn the play. Is he correct or just blowing smoke? |
Quote:
|
Quote:
|
Quote:
Confirmed=enough evidence to confirm call on the field |
Looking at the play in question, Triplette signaled 'third down' but in a way with his arm upward and diagonally that could have been interpreted as a 'first down'. Some officials 'first down' signals are different, i.e. Hochuli's is a psuedo baseball ejection symbol for a 'first down'.
Triplette basically threw the chain gang under the bus in the post game which is a problem because the head linesman clearly gave a signal to the chain gang to move the chains. I believe he did that because he saw Triplette's confusing first down signal and assumed he meant 'first down'. I know they didn't want to give the offense a free timeout, but the clock has to be stopped in this situation to get everything right because in a game like this, it doesn't effect the rest of the season, but if this were a playoff game, well as Al Michaels would say: There would be hell to pay. There is also a photo on the internet while Shanahan was arguing that showed the chain gang less than pleased with the officials. |
While officials are averse to interrupting the flow late in the game at any level, this is the kind of screw-up that can pop up when you hurry and fail to communicate properly. It is still our job to administrate and if that means stopping and measuring then so be it.
I agree that the U spotted the ball incorrectly off the HL. It appeared The LJ foot was on the unofficial yellow line when the play ended. |
I read that the chains were reset as they were getting the 3rd down play off.
|
Quote:
They screwed up. As soon as Triplette saw the chains moving he had to know there was a problem on that sideline and stopped it. And he obviously did as he began signalling 3rd down to that linesman emphatically. |
A way to solve this problem, in the future, is to use both arms to signal second or third down, why? Because 'first down' is always signaled with one arm. It is something I always saw the late Gordon McCarter do. Either that or late in a half, always have the referee signal the down with an open microphone.
People say they never saw this before. Something like this happened to Bob McElwee about a decade ago in a Bears game at the University of Illinois stadium while Soldier Field was undergoing renovations. |
Quote:
|
Quote:
If I'm remembering correctly, I think they ultimately got the spot right, and it should have been short. But it should have been measured, especially after the confusion over the down. Triplette basically threw the chain crew under the bus when in reality he's ultimately the one responsible. That's what bothers me most about this situation. Like the Wisconsin-ASU situation early in the year, we have a clear error by an officiating crew that clearly impacts the game, potentially changing the final score. In both cases it should have been an easy fix for the officials, and in both cases, the officials failed to fix the problem. Errors in judgment calls will happen, they're still frustrating to see, but they happen. Administrative errors like these that happen in relatively relaxed action are a lot harder to let slide. |
The way Al was going nuts over it at the end of the game makes me believe he had some cash on the game! ;)
It's clear the HL signaled for the chains to move... but then it looks like he puts 3 fingers up to show 3rd down. |
Quote:
Do you have any other purpose here? I'm sincerely curious. Do you officiate at all? |
Quote:
|
Quote:
When they miss something, it's still called a "mistake" and although much rarer than at other levels, mistakes, life "stuff", happen. The remedy of course is to remain composed, review what's transpired, make whatever adjustments are necessary to get the situation right and then learn from the experience and add it to the pile of other mistakes you will endeavor never to repeat. |
Quote:
|
Quote:
I do officiate baseball. |
I can understand why Tripplette didn't stop the game to give them a free timeout, but, this whole mess could have been avoided if he would have went with the LJ. I always look to the LJ for determining if it's a first down. If he's giving me a first down, as Referee, I'm giving the signal and we are moving the chains.
|
Quote:
The discussions that I participate in are ones that are of interest to me. I always like to get an officials perspective on things, especially if it's a sport I don't officiate myself. I umpire baseball over the summer and just recently started doing in-season high school ball. I spend a lot of time reading on here and on Umpire Empire, among other sites, in an effort to better myself as an official and better my understanding of the game as a whole. I don't officiate football, and I have no plans to officiate football, but I do still have an interest in rules and an official's perspective as to why things happen the way that they do. There have been calls I've disagreed with that, when explained from an official's point of view, made sense. I realize the the bulk of my posts are in threads about officiating controversies, but I do read the other threads. I'm not going to post if I don't have anything to add to the discussion. I don't think I've been unreasonable, with maybe an exception early on in the WI-ASU thread. I'm certainly not on here to mindlessly bash officials. |
Quote:
|
I don't think this was an issue of measuring vs. not measuring. The 46 was the line to gain and the ball was obviously placed well short of the 46. There was no reason to stop the clock to measure. The reason to stop the clock was to correct the H and put the chains back where they belong based on the spot. I do question the spot since the L appeared to have the 46 but ceded to the H for some reason.
|
Quote:
|
Quote:
|
Most of us have learned long ago, no matter how hard you suck on a whistle, that damn "tweet" is NEVER coming back. All it takes is an instant of distraction or loss of focus to create a mistake. What matters then, is how well we deal with our mistake.
Most on-field mistakes generate a little scar tissue we carry forward FOREVER to help prevent us from repeating the mistake. Other than that memory, there's little else of value to bother carrying forward, so the smart thing to do, is reset your focus and concentration and snap the ball for the next play. Next week you'll have another opportunity to work your FIRST perfect game. |
Quote:
|
Quote:
B/R coach upset because 5-yard penalty still kept them in close FG range, but now they have an opportunity to get organized and not have to rush as much. We enforce the penalty and wound the clock quickly and A/K did not get the ball snapped in time anyway. The lesson I learned is I should have let the play go because there is a chance they don't get the ball snapped. If they do and there is still time on the clock kill it at the snap. Stopping it when I did gave them an advantage. It's a good example of why I like the 10-second subtraction rule. |
Quote:
|
Quote:
|
Quote:
|
Bengals' BenJarvus Green-Ellis Scores Controversial TD Against Colts | Bleacher Report
Triplette's on a roll. |
I watched several replays and could not tell if the NT made contact. It looks very possible he tripped on his own which means the reversal was correct. If Triplett did not look at the possible early contact then he may be in a bit of trouble. Per the pool report transcript he only looked at the goal line.
|
Quote:
Cincinnati Bengals vs. Indianapolis Colts Pool Report |
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
And ... seems to me in the replay there's no chance he was tripped by the NT (I admit the one video in this thread is inconclusive). The one shown on the NFL Red Zone was pretty clear. |
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
I'm pretty sure I've seen this Referee work other NFL games, so I presume this wasn't his first opportunity, and there's been no indication the replay official(s) were volunteers selected from the crowd, and therefore most likely highly experienced as both replay officials and field officials, who were conversing with the Referee, which seems to suggest these highly experienced individuals, collectively, viewed all that needed to be viewed before making their decision.
|
Quote:
|
Quote:
It wouldn't be the first time an official erred on an instant replay decision. |
Quote:
Not exactly an embarrassment, though. |
Quote:
Between screwing the Redskins on the downs issue and by his own admission not reviewing the most important part of the play before overturning the call on the field, Triplette's had some pretty big, unacceptable mistakes. |
Quote:
I'm not here mindlessly bashing. I'm commenting on plays as I see them from a non-official's point of view, and I'm getting an official's point of view in response. That's why I post here. Obviously the people on this forum are going to have a better understanding of why things are called the way they are, or the rules that come into play in certain situations, than some idiot on a fan forum or ESPN comment page. I'm not sure what the problem is with saying a call is wrong when it's wrong. Is there a reason I can't offer my opinion on a play when bringing it up for discussion? |
Quote:
Quote:
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
However, the angle that comes from the hanging camera - it was approximately from behind the left tackle, through the NT and RB with goalpost in the background - was VERY clear to anyone who saw it that the NT didn't touch RB at all. That said --- despite numerous searches, I've been unable to find that angle to post here. |
Quote:
I know in the case of the Gronkowski play, I disagreed with the interpretation of the rule cited. |
Quote:
|
Quote:
|
Quote:
|
The IndyStar has a feature today showing stills of the play from the angle it sounds like Red Zone may have had. The live feed and all the feeds I saw from the press box side were inconclusive to me that Chapman tripped the runner. From angle in these stills though it does appear the contact was made.
Anatomy of a Play: Blown call costs the Colts in Cincy Triplett never said the replays didn't show this part of the play. He just said he didn't look at it. We don't know what he did or didn't see. |
Quote:
I can see Hochuli in there... "OK, give me camera 6. No, zoom out. OK, thanks. Now camera 7... Can you zoom in on the goal line there. OK, thanks. How's camera 8? Oops... out of time." Yeah, that would work. |
Quote:
The view they call the "most obvious view" doesn't appear to be contact to me - and in fact is the opposite foot from the previous view - the right foot is closer to us (the camera) than the hand. |
Quote:
If that is indeed the case, the NFL replay system fails miserably. |
Quote:
|
Quote:
What happens though if the replay official doesn't go back far enough to know there was a potential touch earlier in the play? Nothing the referee can do about that. |
Quote:
|
Quote:
|
Quote:
You keep telling us you're not here just to bash officials - you're here to learn and be educated as well. Yet when someone tries to explain something to you, you bash more. I tried to explain the process to you. Not my fault you've decided not to listen. I'm done trying to help. |
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Enough axe grinding.
|
All times are GMT -5. The time now is 08:44pm. |