<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Zebra Blog &#187; forward progress</title>
	<atom:link href="http://www.footballzebras.com/tag/forward-progress/feed" rel="self" type="application/rss+xml" />
	<link>http://www.footballzebras.com</link>
	<description>A look at the NFL&#039;s officials and the calls they make</description>
	<lastBuildDate>Sun, 29 Aug 2010 01:34:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Week 9 &#8220;Official Review&#8221;: Follow the bouncing ball, spiking out of bounds</title>
		<link>http://www.footballzebras.com/2009/11/11/590</link>
		<comments>http://www.footballzebras.com/2009/11/11/590#comments</comments>
		<pubDate>Thu, 12 Nov 2009 04:29:29 +0000</pubDate>
		<dc:creator>Ben Austro</dc:creator>
				<category><![CDATA[Calls]]></category>
		<category><![CDATA[Week 9]]></category>
		<category><![CDATA[Broncos]]></category>
		<category><![CDATA[Colts]]></category>
		<category><![CDATA[Cowboys]]></category>
		<category><![CDATA[delay of game]]></category>
		<category><![CDATA[Eagles]]></category>
		<category><![CDATA[forward progress]]></category>
		<category><![CDATA[fumble ruled touchback]]></category>
		<category><![CDATA[Jeff Triplette]]></category>
		<category><![CDATA[Mike Pereira]]></category>
		<category><![CDATA[Official Review]]></category>
		<category><![CDATA[replay]]></category>
		<category><![CDATA[Steelers]]></category>
		<category><![CDATA[Texans]]></category>

		<guid isPermaLink="false">http://www.footballzebras.com/?p=590</guid>
		<description><![CDATA[The &#8220;Official Review&#8221; segment returns for week 9 action, with the league&#8217;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 [...]]]></description>
			<content:encoded><![CDATA[<p>The &#8220;Official Review&#8221; segment returns for week 9 action, with the league&#8217;s vice-president of officiating, Mike Pereira, disecting some of the more complicated calls. This week, there were certainly some complex calls (video: <a href="http://www.nfl.com/videos/nfl-network-total-access/09000d5d8142045a/Official-Review-Week-9" target="_blank">part 1</a> and <a href="http://www.nfl.com/videos/nfl-network-total-access/09000d5d814206ab/Official-Review-Week-9-bonus-coverage" target="_blank">part 2</a>), which we will leave the most complex one for last:</p>
<ul>
<li>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 <em>could</em> be used as a demarcation point, and might have given the Eagles a few extra inches. Typically those few extra inches <em>aren&#8217;t</em> 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.</li>
<li>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.</li>
</ul>
<p>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 (<a href="http://www.nfl.com/videos/nfl-game-highlights/09000d5d81406109/Texans-fumble-at-goal-line" target="_self">video</a>). So complicating are the circumstances, that it becomes a list onto itself.</p>
<ul>
<li>Ryan Moats of the Texans clearly fumbled the ball prior to going to the ground.</li>
<li>With the play dead at 2:25, the Texans opted to run the clock to the two-minute warning, giving the Colts&#8217; 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.</li>
<li>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.</li>
<li>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&#8217; ball.</li>
<li><em>However,</em> 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&#8217; at the 20-yard line.</li>
</ul>
<p>Referee Jeff Triplette goes through a <a href="/2009/10/19/507" target="_blank">Hochulian effort</a> to explain the call, taking about 40 seconds to describe:</p>
<blockquote><p>After reviewing the play, the runner <em>does </em>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.</p></blockquote>
<p>A lot of things to watch on that play, but one thing missing from Triplette&#8217;s description.</p>
<blockquote><p>Please reset the game clock to 2:24.</p></blockquote>
<p>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&#8217;s 60-second replay review time.</p>
<p>This is the second time this season that Triplette and Boylston failed to relay this information correctly. <a href="/2009/10/16/470" target="_blank">We noted in Week 5</a>, 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.</p>
<p>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.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.footballzebras.com/2009/11/11/590/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Week 5 &#8220;Official Review&#8221;: Fair-catch interference, fumbled fumbles, &#8216;fishy&#8217; call</title>
		<link>http://www.footballzebras.com/2009/10/16/470</link>
		<comments>http://www.footballzebras.com/2009/10/16/470#comments</comments>
		<pubDate>Fri, 16 Oct 2009 20:32:39 +0000</pubDate>
		<dc:creator>Ben Austro</dc:creator>
				<category><![CDATA[Calls]]></category>
		<category><![CDATA[Follow-up]]></category>
		<category><![CDATA[Week 5]]></category>
		<category><![CDATA[Antwaan Randle El]]></category>
		<category><![CDATA[Bob Boyleston]]></category>
		<category><![CDATA[Boris Cheek]]></category>
		<category><![CDATA[Brian Westbrook]]></category>
		<category><![CDATA[Carl Cheffers]]></category>
		<category><![CDATA[fair catch interference]]></category>
		<category><![CDATA[forward progress]]></category>
		<category><![CDATA[improper spot]]></category>
		<category><![CDATA[Jeff Lamberth]]></category>
		<category><![CDATA[Jeff Triplette]]></category>
		<category><![CDATA[Kent Payne]]></category>
		<category><![CDATA[Mike Pereira]]></category>
		<category><![CDATA[Mike Spanier]]></category>
		<category><![CDATA[multiple fouls]]></category>
		<category><![CDATA[Official Review]]></category>
		<category><![CDATA[picked-up flag]]></category>
		<category><![CDATA[replay]]></category>
		<category><![CDATA[Rich Eisen]]></category>
		<category><![CDATA[Steve Stelljes]]></category>
		<category><![CDATA[taunting]]></category>
		<category><![CDATA[wrong media call]]></category>

		<guid isPermaLink="false">http://www.footballzebras.com/?p=470</guid>
		<description><![CDATA[This week&#8217;s &#8220;Official Review&#8221; 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 [...]]]></description>
			<content:encoded><![CDATA[<p>This week&#8217;s &#8220;Official Review&#8221; by league vice-president of officiating, Mike Pereira, featured several interesting plays from Week 5, leading to a lot of discussion here (video, <a href="http://www.nfl.com/videos/nfl-network-total-access/09000d5d8136a6b6/Official-Review-Week-5" target="_blank">Part 1</a> and <a href="http://www.nfl.com/videos/nfl-network-total-access/09000d5d8136aa63/Official-Review-Week-5-bonus-coverage" target="_blank">Part 2</a>):</p>
<ul>
<li>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&#8217;s opportunity to make a fair catch, but the ball deflected off of Westbrook, creating a live ball. This was <em>not</em> 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 <em>NFL Rule Book</em>:</li>
</ul>
<blockquote><p>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.</p></blockquote>
<ul>
<li>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 &#8220;looks fishy,&#8221; 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&#8217;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).</li>
<li>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.</li>
<li>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.</li>
<li style="list-style-type: none">First, Line judge Michael Spanier (seen in the replay) ruled a fumble and recovery by the Bengals.
<ul>
<li>Failure point #1: Playing this as a fumble, he should have marked the spot of recovery with his beanbag.</li>
</ul>
</li>
<li style="list-style-type: none">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.
<ul>
<li>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&#8217;s 60-second window to make a decision on the play call itself. The yard line, at least, was not discussed or was miscommunicated.</li>
<li>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.</li>
</ul>
</li>
</ul>
<p>Incorrect spots (as opposed to disputed judgment calls) happen very infrequently, but when they do, they are major errors that affect one&#8217;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.</p>
<p>In passing, there were two comments by the NFL Network&#8217;s Rich Eisen that should have been corrected by Periera. First, Eisen referred to giving the kick receiver that signals fair catch a &#8220;halo&#8221; 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.)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.footballzebras.com/2009/10/16/470/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How is forward progress not stopped when player lands 3 yards back?</title>
		<link>http://www.footballzebras.com/2009/10/05/392</link>
		<comments>http://www.footballzebras.com/2009/10/05/392#comments</comments>
		<pubDate>Mon, 05 Oct 2009 04:12:29 +0000</pubDate>
		<dc:creator>Ben Austro</dc:creator>
				<category><![CDATA[Controversy]]></category>
		<category><![CDATA[Week 4]]></category>
		<category><![CDATA[Boris Cheek]]></category>
		<category><![CDATA[Chargers]]></category>
		<category><![CDATA[coach's challenge]]></category>
		<category><![CDATA[forward progress]]></category>
		<category><![CDATA[Jacob Hester]]></category>
		<category><![CDATA[replay]]></category>
		<category><![CDATA[Steelers]]></category>
		<category><![CDATA[Steve Freeman]]></category>
		<category><![CDATA[Steve Logan]]></category>
		<category><![CDATA[Sunday Night Football]]></category>

		<guid isPermaLink="false">http://www.footballzebras.com/?p=392</guid>
		<description><![CDATA[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 [...]]]></description>
			<content:encoded><![CDATA[<h3>Week 4: Chargers at Steelers</h3>
<p>In the <em>Sunday Night Football</em> 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.</p>
<p><a href="http://www.nfl.com/videos/nfl-game-highlights/09000d5d81328f1b/Hester-heads-up-play" target="_blank">The video of the play</a> shows clearly that Logan achieved the 44-yard line, with the fumble occurring at the 41.</p>
<p>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.</p>
<address><strong>Update:</strong> 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.<br />
</address>
<p>There was a coach&#8217;s challenge, but forward progress could not have been overturned on replay.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.footballzebras.com/2009/10/05/392/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
