Tuesday, October 05, 2010

An Issue of Timing

Much has already been made of Andy Reid's boneheaded clock mismanagement at the end of the 1st half of the Redskins-Eagles game that resulted in a delay of game that likely cost the Eagles a TD and probably the game.


But while the delay of game has gotten most of the attention, Reid's decision immediately prior to it was even worse and, considering the situation, made it one of the most stupendously stupid time management decisions in recent years.

As everyone knows by now, with 30 seconds to go in the 1st half LeSean McCoy was tackled just short of the goal line but close enough for a booth review. The review was surprisingly long (as were all of the instant replay reviews in the game), lasting nearly 5 minutes. Replays showed that McCoy was tackled before crossing the goal line. The referee announced the decision and started the game clock (because it had been a running play), whereupon Andy Reid called timeout 7 seconds later, with 23 seconds left in the half - and appeared to immediately ask the officials why the ball had been moved back from its original spot. The rest is well known. Because it was under 2 minutes, the timeout was only a 30 second timeout, Kolb was seen running into the huddle with 11 seconds on the play clock and the delay of game was called shortly after.

The incident appears to have settled the annual criticism/debate over who was more at fault for the Eagles continually poor clock management during the Reid/McNabb years by placing responsibility for this unbelievably questionable decision squarely on the shoulders of Andy Reid (notwithstanding Reid's cryptic suggestion that fault lay with the referees when he said in his Monday press conference that to discuss it would be too "expensive," presumably because of a possible league fine for criticizing the officiating).

While the delay of game was inexcusable on its face, just as big a question - which has not been satisfactorily answered and suggests a fundamental lack of understanding about time management principles - is why Reid called the time out when he did.

Why didn't Reid let the clock wind down to about 3 seconds before calling timeout?

It was 4th and 1. Either the Eagles were going to attempt a FG or go for the TD. Either way it should have been the last play of the half (the PAT can be done with 0 seconds on the clock because time does not run during such a play).

Instead, Reid called timeout with 23 seconds left. WHY?!?!?

Presumably, it was because of the "urgency" of questioning why the ball was moved back from its original spot (note this issue is rather unclear. From the replays I saw, the ball was spotted just inside the 1 yard line. I haven't been able to see on any replay where or how the refs moved the ball back to that spot which allegedly prompted Reid's question).

Regardless of the moving spot, Reid should have had the presence of mind to let the clock run down to 3 seconds before calling timeout and questioning the officials. The fact that the timeout occurred immediately after a nearly 5 minute instant replay delay only adds insult to injury. The entire Eagles offensive coaching staff had plenty of time to figure out how and when to call their timeout once play resumed. Compounding the gaffe (as if that were possible), is that had Reid let the clock run down 27 seconds he would have essentially doubled the length of his 30 second time out and given his coaching staff twice as much time to come up with a goal line play.

Was Reid thinking that a failed 4th down TD attempt would leave the ball so close to the goal line that the Redskins might be at risk of a safety on their first play to run out the first half clock? Such a possibility seems far fetched.

The net result was that following the delay of game, the Eagles kicked the field goal and wound up having to kickoff. It was a kickoff that never should have happened and for which Andy Reid still hasn't and never will properly explain.

No comments: