Posts Tagged ‘Colts’

Week 12 “Official Review”: ‘Chaos,’ DPI, Pereira’s Xbox 360 video controller

• Calls, Week 12
Thursday, December 3, 2009 – 11:14 am | leave a comment

by Ben Austro

This week’s segment of “Official Review” by NFL vice-president of officiating Mike Pereira (video, part 1 and part 2) provides a fascinating insight into the behind-the-scenes work of his department and the grading of officials.

We commented a few weeks ago about Pereira’s modded Xbox 360 controller making its on-air debut and wondered why the change from his simple clicker device he used previously. Turns out that is his everyday equipment for reviewing plays. Pereira said that he was hesitant to try the new equipment, but the controller provides the ability to switch camera angles, as each play is reviewed from a minimum of three angles (the first two are nonbroadcast camera angles, the third is the live shot of the play, and additional angles come from television replays).

Pereira demonstrated the grading process for the officials using an ordinary incomplete pass play from the Giants–Broncos game on Thanksgiving. I counted him shuttling the tape more than 25 times to evaluate every player’s actions on the play. We here, and the rest of the Internet critics, focus on the controversial calls, while the officiating department evaluates some 150 plays per game.  Multiply those 150 plays by 256 games for a total of 38,400 plays. If Pereira used an average play for his demonstration—each of those plays getting reviewed 25 times—that means that in a season, his office does 1 million quality checks on its product a year. And, 98% of the time, the call is correct.

It is a very interesting look at the evaluation process, which also includes periodic written tests and other intangibles. You can see the demonstration on the part 2 video. On to the calls on the field:

  • Pereira reviewed the “chaos to the nth degree,” as he aptly put it, of the final seconds of regulation in the Steelers–Ravens game. He backed up all of our points, but noted something that we did not realize. The crew, amazingly, had the foresight to place the specialized kicking ball for a field-goal kick. Pereira said that in rushed circumstances, the crew should not worry about spotting a “K” ball. He also acknowledged that referee Ed Hochuli forgot to mark the spot of the fumble with his beanbag, which might have jogged his memory of the correct spot when he went to retrieve it. Pereira did acknowledge that stopping the clock to conference about the spot would have been an unacceptable advantage to the Ravens.
  • An early-third-quarter play in the Colts–Texans game gave the Colts 43 yards on a pass-interference penalty against the Texans. Pereira’s assessment was that “it was not a good call.”
  • In the Buccaneers–Falcons game, the down-by-contact rule was reviewed that a player cannot be down if the contact preceeded the receiver catching the ball.

Week 11 “Official Review”: Never-ending game, 2 more errors on replay reviews

• Calls, Follow-up, Week 11
Sunday, November 29, 2009 – 12:36 pm | leave a comment

by Ben Austro

This week’s “Official Review” from the NFL head of officiating Mike Pereira has one less play under scrutiny than usual (three, rather than four). That doesn’t leave us shortchanged, as there are multiple levels of discussion on two plays (video, part 1 and part 2).

Unfortunately, for the second week in a row, Pereira admits that two additional errors were made in the administration of a replay review, upping the count to four in two weeks.

Under review this week:

  • For the final play, and the subsequent quarter-extending play, in the Browns–Lions game, Pereira reaffirmed that the pass interference call was correct, as the pass was in the air, as we reported. Also, we had explained the reason why Lions quarterback Matthew Stafford was allowed to return after an injury timeout without sitting out a down.
  • In the Redskins–Cowboys game, we already reported on the league’s response to a review that should not have been called. Essentially, the Redskins gained 10 yards by the incorrect review, which didn’t have an impact on the score, as the Redskins missed a field goal on the next play. Periera explains:

Since we ruled the runner out of bounds, we essentially killed the play, and the play was over. So nothing that happens after that is relevant. If the receivers catch that pass and run it in for a touchdown, or the defenders intercept it, it’s a dead ball at that point [where the quarterback is] and can’t be reviewed.

So we really reviewed and reversed a play that wasn’t even reviewable.

  • In the Colts–Ravens game, a challenge flag by the Ravens was picked up by coach John Harbaugh with 2:16 remaining in the half. In the conference with the officials, Harbaugh apparently became aware that the officials ruled the receiver dragged a toe in the completion. With that information, Harbaugh changed his mind on the challenge, and the request to withdraw the challenge was granted by referee John Parry. Pereira said that he informed all of the referees this week that this is against the rules:

We want to make sure that [the officials] understand that if a coach throws the challenge flag for a play that is reviewable—a play like this that is reviewable—then we are going to go through with the challenge, even if he subsequently sees that the call on the field was going to be right. So they’ll end up, actually, getting charged with a challenge and a timeout, since they’re going to lose the challenge. Really, it’s the only fair thing to do.

Interestingly, in the conversation, NFL Network commentator Rich Eisen speculated that a defense might use a time-saving strategy from basketball to their advantage. The ubiquitous intentional foul used in basketball could be used by a defense to disrupt a quick snap by the offense on a potentially challengable play.

As we covered previously, a review can happen on the previous play until there is a legal snap. In case a pre-snap penalty administered, the ability to review the last play is not lost. However, if there is a reversal, the penalty is disregarded as if it never happened. Eisen correctly suggested that on a potentially challengeable play with the offense scrambling to snap the ball (to make a review of the previous play impossible), the defense might foul intentionally (except for a personal foul), just to delay a legal snap, and allowing the previous play to be reviewed. If the play is not overturned, the defense will still be penalized, but if it is overturned, the gamble pays off.

We will be watching carefully for an intentional foul on the defense creating a replay opportunity.

Week 10 “Official Review”: ‘Should never happen, we accept responsibility for that’

• Calls, Follow-up, Week 10
Thursday, November 19, 2009 – 11:40 pm | leave a comment

by Ben Austro

Tough job this week for the NFL vice-president of officiating, Mike Pereira. Frequently, he will give in his weekly “Official Review” segment what we feel is the “clean-laundry” version of some of the disputable calls—sometimes under the cover of “it could go either way.” However, there was no hiding from the fact that his crews made significant administrative errors, and, in this week’s installment (video, part 1 and part 2), it is Pereira, and not the laundry, that comes clean.

The topics under discussion (not in the same order):

  • We discussed earlier in the week how the crew of Jeff Triplette had a major breakdown in administering replay challenges. First, Triplette was willing to review a challenge that the Cowboys recovered a fumble, when the rulebook clearly states this is a nonreviewable play. Pereira said, “I was shocked that we started to even go toward the monitor to review it.”
  • Later in the same game, the Packers attempted to call for a challenge when it had exhausted all of its challenges. Triplette should have known immediately, but (according to Pereira) it was replay assistant Bob Boyleston who informed Triplette of the discrepancy. We noted that the officials then should have penalized the Packers bench for an excess challenge. Pereira backed up our assessment by saying, “We should have thrown the flag right then for unsportsmanlike conduct. It’s a 15-yard penalty … He should have been penalized right at that point. We were wrong in not doing that.”
  • In the Ravens–Browns Monday Night Football game, the Browns were granted a fourth timeout erroneously in the second half. Pereira did not hide the fact that it was a major error:

It happened because we, as a crew, failed to record on our cards the [timeout] at the 3:24 mark of the third quarter. … Everybody on the field basically forgot to record the timeout. And the scoreboard did, too. So, we didn’t have it on our cards [and] it showed on the scoreboard that we had one left. Therefore, we granted the first play after the two-minute warning a fourth timeout. All our fault.”

To sum up all of the operational errors, Periera added this:

These type of administrative things should never happen and we accept responsibility for that.

  • Also under “Official Review” was the oft-talked-about 4th-and-2 play where the Patriots attempted to get the first down to run out the clock, rather than punt to the Colts (video). Because the ball was juggled (and clearly indicated by headlinesman Tom Stabile), forward progress cannot be granted until the player gets control. It was a good call by Stabile in real-time, and a tough call to make on such a pivotal play. With the benefit of replay, it would appear that the Patriots were further back even. When Kevin Faulk maintains control, he is in the air and going to the ground. Even though he has caught the ball, he has not by rule caught the ball until he plants two solid feet, or has gone completely to the ground. (For spotting purposes, forward progress would be given at the point of any body part other than a hand or foot hitting the ground, provided the receiver subsequently completes the process of a catch.) Pereira should have stopped talking at that point, because he said that if the original call was first down, and if the Colts challenged the call, that the original call would have stood. This is a wishy-washy answer, as Faulk is clearly bobbling the ball and not touching the ground until clearly behind the first-down marker.
  • In the Buccaneers–Dolphins game, an incomplete pass was correctly overturned as an interception (video). OK, I know there is dispute at to whether it was correctly overturned. Much like in Week 2, an incomplete pass which is overruled as an interception gives the intercepting team the ball where it was caught, nullifying any return.

All that said, I was very distracted with Pereira’s new video control device, which seems to be a modded wireless Xbox 360 controller. Seemed to me that the rewind/slow/pause switch that Pereira had up to this point, albeit wired, simply and unobtrusely did its job. Or, perhaps Pereira was playing Madden NFL ‘10: Referee Edition off camera.

Week 9 “Official Review”: Follow the bouncing ball, spiking out of bounds

• Calls, Week 9
Wednesday, November 11, 2009 – 11:29 pm | 1 Comment

by Ben Austro

The “Official Review” segment returns for week 9 action, with the league’s vice-president of officiating, Mike Pereira, disecting some of the more complicated calls. This week, there were certainly some complex calls (video: part 1 and part 2), which we will leave the most complex one for last:

  • In question was the spotting of the ball in the Cowboys–Eagles game on two different plays. In one case, a player going back for the ball is not awarded forward progress (correctly called), because he was not in contact with the defender, therefore not being pushed back. The second one regarded the fourth-down quarterback sneak by Donovan McNabb. Pereira notes that the center-field logo could be used as a demarcation point, and might have given the Eagles a few extra inches. Typically those few extra inches aren’t given during replay, but in this case, there was a clear placement with relation to an on-field mark. Pereira said the ball should have been moved.
  • On a play in the game with the Steelers,  Brandon Marshall of the Broncos spikes the ball at the end of the play, and somehow avoids being penalized. Since he was out of bounds, he is not causing a delay in spotting the ball, therefore no delay of game penalty is administered.

The most complex play, perhaps of the entire season, involved a down-by-contact ruling at the 1-yard line in the Colts–Texans game (video). So complicating are the circumstances, that it becomes a list onto itself.

  • Ryan Moats of the Texans clearly fumbled the ball prior to going to the ground.
  • With the play dead at 2:25, the Texans opted to run the clock to the two-minute warning, giving the Colts’ coaching staff the entire break to review the play. The coach may challenge the final play prior to the two-minute warning up until the first legal snap after the two-minute warning.
  • It is reasonably clear that Moats did not touch the ball after dropping it. Since his tackler was out of bounds while holding Moats, if Moats touched the ball, the ball would be out of bounds at that spot.
  • Jerraud Powers of the Colts jumps back in bounds to retrieve the ball, but since he does not establish two feet in bounds, he makes the ball dead, and it is still Texans’ ball.
  • However, since the ball is ruled out of bounds on the goal line by an offensive fumble, this becomes a touchback, and in this case, is awarded to the Colts’ at the 20-yard line.

Referee Jeff Triplette goes through a Hochulian effort to explain the call, taking about 40 seconds to describe:

After reviewing the play, the runner does fumble the football prior to being down by contact. The ball stays in bounds. The Indianapolis defender is out of bounds when the ball is laying the goal line, comes back in and, with one foot down, touches the football. Therefore, it is a fumble out of bounds in the end zone. It is a touchback. First and 10, Indianapolis, from the 20-yard line.

A lot of things to watch on that play, but one thing missing from Triplette’s description.

Please reset the game clock to 2:24.

Because the play was ruled dead at that point, the time had to be restored to the clock, even though the two-minute warning had already transpired. It is understandable with so much involved in that play, however once a decision is made, the replay official (in this case, Bob Boylston) and the referee must communicate the down, distance, yard line, and time remaining on all reversals. The time taken to determine the spot and the time remaining consistent with the reversal decision is outside of the referee’s 60-second replay review time.

This is the second time this season that Triplette and Boylston failed to relay this information correctly. We noted in Week 5, that a replay reversal failed to account for the correct spotting of the ball, one of several failure points on the same play. In addition, there are six other officials, one of whom should have confered with Triplette to restore the time consumed.

Tough call on the refs there, especially when they made a difficult decision correctly. But the sloppy bookkeeping on replay reversals must be fixed with this crew.