Posts Tagged ‘Sunday Night Football’

Incorrect spot in end-of-regulation scramble could’ve impacted playoff race

• Controversy, Week 12
Monday, November 30, 2009 – 3:23 pm | leave a comment

by Ben Austro

Week 12: Steelers at Ravens

With only moments to think, officials can make decisions based on digesting a 115-page rulebook. On average, 98% of the time they get it right. When there is an error it could have an impact on the game. When divisional foes meet, it could have an impact on the playoffs.

In all fairness, though, even if a bad call occurs, there usually are several opportunities that the affected team did not take advantage of. Much like the weather, the officiating is an element of the game mostly out of the team’s control, but something good teams adapt to.

While most errors are inexcusable, this one has some mitigating circumstances. However, the call is still wrong, and mitigating circumstances do not help officials in their evaluations which determine playoff assignments.

fgspot

Video of fumble and field goal attempt at NFL.com

In a hard-fought divisional game between the Ravens were within long field-goal range against the Steelers near the end of regulation. On third and 9 from the Steelers 34, Ravens quarterback Joe Flacco fumbled the ball at the 42, which was recovered by the Ravens at the 37 with 18 seconds remaining. Out of timeouts, the clock was running while a fire-drill substitution of the field-goal personnel ensued.

Headlinesman Mark Hittner came in to mark the dead ball spot at the 37. While that was the correct dead-ball spot, the Ravens should have gotten the ball at the 42, the spot of the fumble. (The responsibility for the spot goes to the head referee, officially.) Sunday Night Football announcer Al Michaels, after the fact, did call attention to this.

NFL Rulebook 8–7–6: If a fumble by either team occurs after the two-minute warning:

(a) The ball may be advanced by any opponent.

(b) The player who fumbled is the only player of his team who is permitted to recover and advance the ball.

(c) If the recovery or catch is by a teammate of the player who fumbled, the ball is dead, and the spot of the next snap is the spot of the fumble, or the spot of the recovery if the spot of the recovery is behind the spot of the fumble.

Fortunately for Ed Hochuli’s crew, the field goal attempt was two yards short.

I do seem to remember a game in the last five years or so where the ball was spotted incorrectly before a field goal. (I’m looking for it; if you remember, put it in the comments.) Having realized the mistake, the officials wiped out the down, respotted the ball, and the field goal was taken five yards closer. Had there been a field goal from 56 yards, you can imagine the uproar if the officials salted the down to respot for a 61-yard field goal.

So while there was a major error, there are other circumstances that need to be considered:

  • If there was a conference regarding the spot of the ball, Hochuli would have had to call an official’s timeout. This would have given the Ravens time to line up a field goal, which (we’ll never know) could have been an advantage on a 61-yard field-goal attempt.
  • During the mass substitution, officials had to count that there were 11 players on the field. (Offense is counted by the umpire, line judge and headlinesman; defense by the side judge, field judge and back judge.)
  • The field judge and back judge had to position themselves under the uprights for the kick.
  • The line judge and headlinesman were watching for the offense to be set for a full second prior to a snap.
  • The headlinesman was on the Steelers sideline, so it was possible that the coach could have signaled a timeout prior to the kick.

However, as the vice-president of officiating will probably tell us in his weekly “Official Review” video, having too much to think about is not an acceptable excuse. Fortunately, the spot of the ball did not have a determination on the final score or playoff seedings.

Incomplete pass not called on key catch of Steelers opening drive

• Calls, Week 4
Monday, October 5, 2009 – 9:50 pm | leave a comment

by Ben Austro

Week 4: Chargers at Steelers

Pro Football Talk noticed a missed call on the Steelers opening drive during Sunday Night Football. (video)

On the third offensive play of the game, Ben Roethlisberger (who just completed two passes on the first two plays) connected with Mike Wallace for 35 yards, taking the ball down to the Chargers 14-yard line. Head coach Norv Turner could have had an easy reversal, though, had he thrown the red challenge flag.

Wallace was only able to get one foot in bounds before being driven out by Steve Gregory. Since the “force-out” rule has been rescinded, this should have been ruled an incomplete pass.

This was under the jurisdiction primarily of the field judge, Boris Cheek. The line judge, Michael Spanier, comes in to spot the ball. Both missed an obvious non-catch call.

How is forward progress not stopped when player lands 3 yards back?

• Controversy, Week 4
Monday, October 5, 2009 – 12:12 am | 1 Comment

by Ben Austro

Week 4: Chargers at Steelers

In the Sunday Night Football game, the Chargers special teams player Jacob Hester is credited with a heads-up, 41-yard fumble-return touchdown. However, it is confusing how the Steelers punt returner Steve Logan was driven back three yards in control of the ball without being ruled down by forward progress.

The video of the play shows clearly that Logan achieved the 44-yard line, with the fumble occurring at the 41.

The covering official was back judge Steve Freeman, who marked the point of recovery with his beanbag. The field judge, Boris Cheek, was covering the sideline at the 25 (you will see his hat marking that a player stepped out of bounds), so he was in no position to judge forward progress.

Update: As stated in the comments, the side judge, indeed has coverage on kicks to determine forward progress. I was unable to see his positioning from the video. The side judge in this game was 19-year veteran David Wyant.

There was a coach’s challenge, but forward progress could not have been overturned on replay.

Will Flozell Adams’ 3rd trip in 3 weeks mean 3rd consecutive fine this season?

• Discipline
Tuesday, September 29, 2009 – 8:54 pm | leave a comment

by Ben Austro

Cowboys offensive tackle in a 2007 file photo. (Credit: texas_mustang, Flickr)

Cowboys offensive tackle Flozell Adams in a 2007 file photo. (Credit: texas_mustang, Flickr)

Cowboys offensive tackle Flozell Adams may be fined for a third consecutive week in the three-week-old 2009 season—which, we believe, would be unprecedented. To date, Adams was fined $5,000 in the season opener for helmet contact against the Buccaneers. In the Week 2 Sunday Night Football game, Adams administered two leg whips, one of which knocked the Giants’ Justin Tuck to the ground, injuring Tuck’s shoulder. Adams was fined $12,500 for the flagrant personal fouls (the second one, which caused no injury, was not flagged).

Big Blue Interactive (on their message board, bonus: with video) points to a third instance where Adams tripped a Carolina Panthers defensive lineman, which was again not flagged by the crew. It is very subtle and away from the play, which is why it did not attract a yellow handkerchief.

Will the league garnish Adams’ pay for a third consecutive week? It should not the fact that the trip wound up being harmless, but that this is a repeat of a fined behavior from the previous week. But, for flagrant personal fouls, the league fine schedule merely states, “suspension or fine; severity to be determined by degree of violation; the fine may be $10,000 or higher for first offense.” So the league, using the injury to Tuck as reason to fine more, may have trouble assessing a fine under the criteria of “degree of violation.”

Update 9/30/09: The league dropped the fine hammer today, according to Todd Archer at The Dallas Morning News, to the tune of $7,500. That is $25,000 for three weeks—which is less than 10% of his weekly gross.

Giants interception correctly goes to the spot of recovery, not spot of whistle

• Calls, Week 2
Monday, September 21, 2009 – 2:29 pm | leave a comment

by Ben Austro

Week 2: Giants at Cowboys

The amazing interception by the Giants’ Kenny Phillips off of the foot of Cowboys’ Jason Witten (video) could be the first use of what might be referred to as the “Ed Hochuli rule.”

You may remember last year’s botched call in the Chargers–Broncos game where an incomplete pass ruling could not be overruled as a turnover.

In this weekend’s Sunday Night Football game, the ruling was incomplete. However, in a Rockette-worthy display, it actually caromed of the shoe of Witten into the waiting hands of Phillips. Phillips then trotted to the end zone untouched, although whistles did not blow until he was at the 5-yard line.

Mike Carey overturned the incomplete ruling on replay, but the ball in these situations, even if there is a delayed whistle, will go back to the spot of recovery. Even in the absence of the whistle, the covering official signaled incomplete, which is equivalent to a whistle.

And, yet, I find that this was not the most discussed pick in the game, but this was.

On a side note, there was to be no doubt if a punted ball banged off of the video screen with NBC’s cameras making sure that they showed the 600-ton hovering HDTV on all punts. Annoyingly, I might add.