Fisher says mistake by clock operator cost Rams in Sunday's loss

Monday, September 10, 2012 | 9:04 p.m. CDT
Rams coach Jeff Fisher, right, argues with NFL referee Donovan Briggans during the second quarter Sunday's 27-23 loss to the Lions in Detroit.

ST. LOUIS — St. Louis Rams coach Jeff Fisher says a mistake by the clock operator late in Sunday's last-second loss at Detroit basically gave the Lions an extra timeout that completely changed how the finish played out.

"In essence, Detroit was granted an extra timeout, I guess, if you want to look at it from our perspective," Fisher said Monday.

The league office agreed Monday. It's just a bit of consolation for a team coming off a two-win season that took the Lions to the wire on the road in their opening 27-23 loss.
Fisher said he didn't replay the events endlessly overnight, mentioning several other potential turning points. He was matter-of-fact discussing the clock issue, keeping his voice even.

"There was an error," he said. "I did report it to the league, and that's all I can do."

After the league's weekly review of game tape, Greg Aiello, the NFL's senior vice president of communications, said the clock was stopped incorrectly.

"The officials did not signal for it to stop," Aiello said in an email to The Associated Press. "The game clock was three seconds behind where it should have been. ... The game clock stopped incorrectly for a few seconds."

Fisher has served on the NFL competition committee since 2000 and was co-chairman for many of those years, so he knows the rule book. Fisher said the mistake was "correctable on the field" but added timing issues were not reviewable.

Fisher was careful not to criticize replacement officials, saying clock operation was unrelated to on-field operations.

"This is clock operator error," Fisher said.

The 40-second time clock started three or four seconds before the game clock resumed after quarterback Sam Bradford slid for a 3-yard gain close to the sideline. Fisher anticipated he could let the clock run to the two-minute warning but instead had to call timeout with 2:03 to go with the play clock about to expire.

The clock operator may have anticipated Bradford's slide taking him out of bounds, but Fisher pointed out that none of the officials called for the clock the stop.

"The issue is the 40-second clock started and then the game clock froze, and the 40-second clock got ahead of the game so I couldn't run it down."

The Rams were set to run on third down after the two-minute warning, forcing the Lions to use their final timeout.

"Of course we're going to run it because we know we're in field goal range at that point. And coach Schwartz has a choice whether he lets it run down or uses the timeout," Fisher said. "And I would assume he would use the timeout immediately, and therefore he wouldn't have a timeout going into his two-minute drive."

Lions coach Jim Schwartz is a former Fisher assistant.

"Knowing Jimmy ... any coach would use their last timeout there," Fisher said. "You've got to conserve time."

Instead, Bradford threw an incompletion, and Greg Zuerlein kicked a go-ahead 46-yard field goal the first play after the two-minute warning.

The Lions had 1:55 to work with on their final drive, running nine plays with time to spare. Stafford completed three passes over the middle, and Detroit used its final timeout with 35 seconds to go on a drive capped by Kevin Smith's 5-yard touchdown catch with 10 seconds to go.

Starting the final possession with 1:55 or less remaining and no timeouts and with 80 yards to go, Stafford would have had to work the sideline to conserve time. 

Like what you see here? Become a member.

Show Me the Errors (What's this?)

Report corrections or additions here. Leave comments below here.

You must be logged in to participate in the Show Me the Errors contest.


Leave a comment

Speak up and join the conversation! Make sure to follow the guidelines outlined below and register with our site. You must be logged in to comment. (Our full comment policy is here.)

  • Don't use obscene, profane or vulgar language.
  • Don't use language that makes personal attacks on fellow commenters or discriminates based on race, religion, gender or ethnicity.
  • Use your real first and last name when registering on the website. It will be published with every comment. (Read why we ask for that here.)
  • Don’t solicit or promote businesses.

We are not able to monitor every comment that comes through. If you see something objectionable, please click the "Report comment" link.

You must be logged in to comment.

Forget your password?

Don't have an account? Register here.