Zebra Report: Refs Made Correct No-Call On Redskins' Costly Muffed Punt

Zebra Report is FanHouse's analysis of actual NFL rules and how they are to be applied ... because most fans think they could do a better job than the NFL officials, yet definitely could not. Click here for an introduction as to how we do things.

One week later and we know now that the league is mandating the roughing the passer calls we discussed last week. This past week, we also learned that the league admitted error on the Mike Sims-Walker touchdown we discussed, which should help to relieve some of the tension fans are carrying about a perceived lack of accountability. I was pleased to see the league's admission. Let's get to the reviews for this week.

Antwaan Randle El is contacted by his own teammate while trying to catch a punt -- the Panthers recovered the retained the football in the aftermath. As you can see in the youtube video below, Randle El's teammate was clearly blocked into him by a member of the Panthers coverage unit. Watch and see -- the play begins at the 3:22 mark.



After the game, referee Walt Coleman explained:

"What happened was, the two guys were blocking each other. The Washington guy got blocked into his own man, so there was no interference. All we had to figure out who touched it first. If the Washington player is stationary and just standing there and not trying to block, then he can't do that. If they are both trying to block, then he can knock him into him. Because they were both engaged, then that's why there wasn't a foul or anything wrong with that play. If the Washington player is stationary and just standing there and the Carolina player had come down there and knocked him, then it would have been totally different."

Coleman is referring to a very specific and important part of Rule 10-1-1-Item 1 (it's bolded):

It is interference if a player of the kicking team contacts the receiver, or causes a passive player of either team to contact the receiver, before or simultaneous to his touching the ball.

From watching the highlight, it is very clear the Redskins player was actively attempting (attempting being the operative word because he was being physically dominated) to block the Panthers' coverage man, so he was not passive in the least. Thus, there is no penalty for kick-catching interference and the officials made the correct call.

For what it's worth, Redskins head coach Jim Zorn now understands the call but stopped short of expressing regret in wasting a challenge on the play.

"It was very difficult at that particular time, he said. "I talked to NFL Vice President of Officiating Mike Pereira about that this morning about the rule. I read the paragraph in the rule book which talks about getting the opportunity to have a fair catch. It was explained within that paragraph what the problem was. I could have saved a timeout, but it was worth it for me to challenge. That was a key play in the game. I wasn't going to save a timeout for that. It was my duty, in my mind, to challenge that."

Reader Scott submitted this play for examination:

"On an extra point try (in the Bengals-Ravens game), the ball was snapped wide of the holder and a scramble ensued. Once the ball was recovered by a Ravens player, the play was whistled dead. However, this was all rendered moot because a flag was thrown for illegal procedure, lining up over center. What exactly does that mean and what is the rule? Second, is there ever a time that a defensive team can recover a ball during a point after or two-point conversion and attempt to score?"

First of all, thanks for the submission, Scott. Both parts of the question are cut-and-dry rules, though possibly not known to many fans.

Rule 7-2-2 - During a field-goal attempt or a Kick Try, a Team B player, who is within one yard of the line of scrimmage at the snap, must have his helmet outside the snapper's shoulder pads.

There could be some confusion here because in high school and all lower levels, you can line up directly over the center, you just have to give him the opportunity to raise his head after the snap before contacting him. The NFL probably just didn't want to deal with judging what a reasonable amount of time was for the snapper to raise his head. Trust me, there are plenty of high school teams who tell their snapper to never raise his head -- then complain he was roughed when someone waits two seconds before trying to break through.

As for the second part of the question ...

Rule 11-3-2c: If the defense gains possession, the ball is dead immediately. The defensive team cannot score during a Try.

The confusion here likely stems from college football, where the defense can return an extra point attempt for two points.

Justin Fargas fumbles as his forward progress is stopped ... or is it? You can check out the video in MDS' post about Darrius Heyward-Bey's blazing speed. Fortunately this play had no bearing on the outcome of the game, as the Giants stomped a mud-hole in the Raiders. The reason I say "fortunately" is because I believe the decision on when to blow the whistle on plays like this is the most difficult thing any official has to do during any given game. Blowing the whistle a millisecond too early or too late could gravely cost either team. If a team believes their ball-carrier was about to break free, it's the fault of the official. If the defense believes they caused a fumble before the progress was stopped, but a whistle was blown, it's the fault of the official.

I actually wrote more in depth about the difficulty of when to blow the whistle last season. I firmly believe this is one of those things where you truly don't know what it's like until you've experienced it (and if you have, you know what I'm talking about).

Got a rules-related question? Whether it's elementary, high school or NFL, email TZR and he'll see what he can do.