Zebra Blog

Justice came swift for the Panthers Dante Wesley for his hit on Clifton Smith of the Buccaneers that we described as being like a runaway locomotive. (He was ejected for the hit with 10 seconds remaining in the second quarter.) We expected an announcement either today or tomorrow, but the NFL wasted no time in handing down judgment. He will be suspended without pay for next week’s game. The announcement from the NFL:

Defensive back Dante Wesley of the Carolina Panthers has been suspended without pay for one game by NFL Executive Vice President of Football Operations Ray Anderson for a flagrant violation of player safety rules.  Specifically, on a punt coverage play on Sunday, Wesley left his feet, launched himself and made shoulder and forearm contact with the neck and head area of Tampa Bay punt returner Clifton Smith, who had not caught or touched the ball and was in a defenseless posture.

The suspension will sideline Wesley for the Panthers’ game against the Buffalo Bills on Sunday, October 25.

In a letter to Wesley, Anderson wrote: “The playing rules (Rule 10, Section 1, Article 1) specifically provide that a member of the kicking team is prohibited from interfering with a receiver attempting to catch an airborne kick.  The prohibited contact in this case went well beyond simply interfering with the receiver.  Instead, by striking your defenseless opponent in the head and neck area, you committed an unnecessary and unnecessarily dangerous act that is specifically prohibited by the rules.”

Anderson added: “Your actions are of particular concern in light of the emphasis that our office has placed on developing and enforcing rules designed to protect players from injury, including head and neck injuries.  The safety of our players is paramount to all of us in the NFL.”

Week 6: Panthers at Buccaneers

Dante Wesley of the Panthers was ejected for a flagrant hit on kick returner Clifton Smith of the Buccaneers. Smith called for a fair catch, and Wesley flattened him to the turf long before the ball even got there. It was penalized as both fair-catch interference and a personal foul, however the fair-catch signal is irrelevant in the fact that this was a malicious hit on a defenseless receiver. (video) Smith appeared to be knocked unconscious by the hit.

The ball immediately bounced out of bounds, allowing for a bench-clearing conference to develop around Wesley. The officials indicated multiple post-play penalties by throwing hats (to indicate a second penalty after his flag had been thrown), however all of these penalties were picked up.

Wesley will certainly be fined heavily for the hit, and we think that a suspension is likely. The last suspension for an on-field incident was Elbert Mack of the Buccaneers, who laid a helmet-to-helmet hit on Falcons quarterback Matt Ryan. A suspension announcement would be likely on Tuesday.

As for the others involved in the brawl after the play, the league will be examining the videotape for those—particularly those who came off the sideline—to mete out fines later in the week.

This week’s “Official Review” by league vice-president of officiating, Mike Pereira, featured several interesting plays from Week 5, leading to a lot of discussion here (video, Part 1 and Part 2):

• As pointed out in our comments, there was a bizarre fair-catch play in the Redskins–Panthers game. Basically, the Panthers, while punting, had blocked Brian Westbrook of the Redskins into his recevier Antwaan Randle El. Not only did the block interfere with Randle El’s opportunity to make a fair catch, but the ball deflected off of Westbrook, creating a live ball. This was not called fair-catch interference, because Westbrook and the Panthers special-teamer (Quinton Teal) were actively engaged in blocking each other. According to Rule 10, Section 1, Article 1, Item 1 of the NFL Rule Book:

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.

• A taunting call that was assessed in the Patriots–Broncos game was, on replay, showing the side judge Jeff Lamberth throwing his flag prior to the taunting incident. Pereira knowledged this “looks fishy,” but, it turns out there were originally multiple fouls on the play. Lamberth was flagging an illegal helmet hit, while back judge Dino Paganelli flagged for the taunt. Headlinesman Kent Payne came in afterward to say that it wasn’t a helmet-to-helmet hit, and that flag (the one seen in the video) was picked up. This left the taunting foul, which came in off screen, as the only penalty called on the play. However, referee Carl Cheffers should have stated in the announcement that the flag for helmet-to-helmet contact was picked up (even though there actually was helmet-to-helmet contact).
• An apparent fumble in the Raiders–Giants game was ruled down by contact, which the Giants challenged. Then referee John Parry explained the dead-ball ruling was not down by contact, but due to forward progress being stopped. The challenge flag was picked up, since forward progress is not reviewable on fumble plays.
• An apparent fumble in the Bengals–Ravens game lead to a rarely seen improper spotting of the ball. This play had a major breakdown in officiating mechanics, where the redundancy in the system failed terribly.
• First, Line judge Michael Spanier (seen in the replay) ruled a fumble and recovery by the Bengals.
  • Failure point #1: Playing this as a fumble, he should have marked the spot of recovery with his beanbag.
• Then, the field judge Boris Cheek came in to declare down by contact. This was challenged by the Bengals, and upheld as down by contact.
  • Failure point #2: Upon declaring a replay decision, the referee (Jeff Triplette)  and the replay assistant (Bob Boyleston) must determine down, distance, yard line, and the game time. This is not part of the referee’s 60-second window to make a decision on the play call itself. The yard line, at least, was not discussed or was miscommunicated.
  • Failure point #3: Upon spotting the ball ready for play, all seven officials did not realize the ball was placed 4½ yards behind the dead-ball spot. This should have been readily apparent to the headlinesman (Steve Stelljes) since the play, with the bad spot, was a –1 yard net, when the reception was clearly past the line of scrimmage.

Incorrect spots (as opposed to disputed judgment calls) happen very infrequently, but when they do, they are major errors that affect one’s playoff eligibility as an official. While the official game records show a –1 yard play, the officials can expect a –3 on their season scorecards.

In passing, there were two comments by the NFL Network’s Rich Eisen that should have been corrected by Periera. First, Eisen referred to giving the kick receiver that signals fair catch a “halo” area to allow him to catch the ball. The halo rule on a fair catch is an old college rule which did not permit a member of the kicking team within a certain distance of the fair-catch-signalling player. This is not a rule employed above the high school level. Secondly, Eisen remarked that if one official saw two fouls, that he should have marked the second one with his hat. In a case were there are two fouls at one enforcement point, the flag is suffice. (The flag is primarily an enforcement marker by the official, so dropping a hat to mark the same spot is unneccessary.)

Without getting into tremendous detail, the Week 2 edition of “Official Review” (two-part video that aired on NFL Net and NFL.com) covered the same topics we covered this week. The assessments we gave on the calls were entirely backed up by the league’s vice president of officiating, Mike Pereira. The calls under Official Review:

• The call of interference with a fair catch on the Titans
• The interception caught off of a foot by the Giants, overturned on replay, but the return nullified.
• The catch possession through to the ground was discussed as it pertained to the Texans and Panthers touchdowns being upheld. Also, the Dolphins had an interception overturned on Monday Night Football on similar grounds (video highlight at 1:05).

The segment also covered the noncontroversial call on the last play of the Bengals–Packers game. With the clock about to expire, referee Ed Hochuli ruled that the game was over prior to the snap. He then corrected the call that there was one second left on the clock, but since the Packers were not set in their stance at the snap, it was a false-start penalty. Of course, a false start with the clock running under two minutes also includes a 10-second runoff, which then consumed the one second. It was only a matter of clean bookkeeping, as the game ended without a play being run under both circumstances.

Pereira did express regret that the catch/ground issue has been so misconstrued and misunderstood only two weeks into the season. Whether this results in a Competition Committee review (as he alluded to with the Titans interference play) remains to be seen.

Week 2: Texans at Titans

Back to Nashville we go for a fluke of a play that resulted in an extraordinary penalty. By the rules, it is a correct call.

At the end of the third quarter, the Texans’ Jacoby Jones (who just had narrowly escaped a potential replay reversal on his touchdown a quarter earlier) signaled for a fair catch and muffed the catch (video at 3:00). Jason McCourty was right there to catch the ball right out of the air for the Titans. However, Jones had signaled for a fair catch, and since the ball did not hit the ground, he was still entitled to a fair catch. And since McCourty caught the ball off the rebound, he was flagged for interference with a fair catch, a whopping 15-yard penalty. (Obviously, most cases of fair-catch interference involve defenseless receivers having the lumber laid down on them, so that is the basis for the yardage.)

Later in the fourth quarter, a sideline fracas broke out, in which Jason Jones of the Titans was disqualified after throwing a punch.

Walt Coleman was the referee.