Detroit Lions Running Out of Ways to Lose
What else could possibly happen?
Last Sunday, the Detroit Lions jumped out to a 17-0 lead in the first quarter against the Seattle Seahawks, and still managed to lose by 12 points.
And the beatings go on.
The Lions have been shut out, lost late leads, fallen short in fourth-quarter comebacks, lost because of offense, defense, and special teams.
And that’s just this season. The only good news this season is that the team hasn’t lost by two after an unforced safety.
Yet.
But the Lions are about to play Minnesota, so who knows?
In all seriousness, though, the Lions losing seven out of eight games played this season is no big surprise.
What is surprising is the ability of the Lions to find unique ways to lose those games. No two losses have been quite the same.
Observe:
Week One: New Orleans Saints, 45-27
The Culprit: Slow Starting
The Lions fell behind by two touchdowns early, the woke up and clawed back to within four points. They spent the rest of the game down by between 11 and 18.
Drew Brees had six touchdown passes, a career-high.
Week Two: Minnesota Vikings, 13-27
The Culprit: Turnovers/Defense
The Lions went up 10-0 early, and then remembered they were the Lions. They let the Vikings rattle off 27 unanswered points, and never made any legitimate attempt at holding the lead or coming back once they lost it.
They might have, if not for a plethora of turnovers at various turning points in the game. An interception in Minnesota territory early, a Kevin Smith fumble with the game tied at 10 (which led to a Minnesota touchdown), and another interception in the fourth quarter (which led to another Minnesota touchdown) all contributed to the Lions losing control of this one.
Vikings LB Chad Greenway had both Minnesota interceptions in the game, doubling his career total. He also recovered Smith’s fumble.
Week Four: Chicago Bears, 48-24
The Culprit: Special Teams
As the old cliche goes, special teams is one third of the game.
But if that’s the case, how come the Lions were able to find a way to lose a game on the strength (or lack thereof) of their special teams play?
After the Lions and Bears played to a 21-21 draw in the first half, the Lions kicked off to begin the second. And 102 yards later, Johnny Knox was in the end zone, and the Bears went up for good.
In the game, the Bears averaged 17.4 yards per punt return.
The Lions did not have a punt return.
The Bears had 190 kick return yards on four returns, for an average of 47.5 yards per return. Yes, as in half the field on every kick.
The Lions had less return yardage (149) on twice as many kickoff returns.
Week Five: Pittsburgh Steelers, 28-20
The Culprit: The Comeback That Wasn’t
It was SO close. The Lions came close to pulling a shocker at home over the defending champions.
The Lions began their comeback attempt with 7:55 remaining in the fourth quarter, down 28-13. The Lions, behind backup QB Daunte Culpepper, scored a touchdown, forced a three-and-out, and drove deep into Steeler territory again.
At the two-minute warning, it was first down at the Pittsburgh 21-yard line, with the score 28-20. Overtime was within reach.
The next four plays in order: QB sack (six yards), QB sack (five yards), QB sack (13 yards), incomplete heave to the end zone on fourth-and-34.
For once, the Lions were the team that came alive in the second half, but they couldn’t finish the comeback.
Week Six: Green Bay Packers, 26-0
The Culprit: Flatlining
The Packers committed 13 penalties, allowed five sacks, and came out with a shutout.
That’s when you know nothing has gone your way.
Drew Stanton was considered the leading passer for the Lions, going 5-for-11 for 62 yards and two interceptions.
Aaron Rodgers continued his torrid pace against the Lions, going 29-for-37 for 358 yards and two touchdowns, despite the heavy pressure, and the Packers ran away with the game.
The sad part is, had the Packers not played such a sloppy game, it could have been much worse. But the Lions just didn’t show up, and failed to make the Packers pay for any of their mistakes.
Week Eight: St. Louis Rams, 17-10
The Culprit: No Offensive Production
In this game, the Detroit Lions scored 10 points on a winless team.
A safety (on a bizarre interception return), a touchdown, and a two-point conversion.
On a previously winless team. Seriously.
Sure, the Lions could have done a better job of bottling up Steven Jackson. But even with his 149 yards, the Rams still only scored 17 points. And the Lions couldn’t match it.
Week Nine: Seattle Seahawks, 32-20
The Culprit: One (Quarter) and Done
After the first quarter of the Seattle game, a singular question ran through the minds of Lions fans near and far: “Where has this team been for the last decade?”
Turns out, they were here all along.
The Lions came alive early against the struggling Seahawks, forcing turnovers on Seattle’s first two offensive plays from scrimmage, and capitalizing by turning them both into touchdowns.
On the Seahawks’ next possession,the Lions forced a four-and-out, and turned that into three more points.
By the end of the first quarter, the Lions led 17-0.
Then they took a two-hour nap, and when they awoke, the game was over, and they had lost 32-20.
Matt Stafford threw five interceptions, as he was obviously in a hurry to get back to the sidelines and watch.
The defense played their patented style of “bend-but-don’t-win,” allowing Seattle to climb back into the game, field goal by field goal.
Let this game be proof: If your team plays a Super Bowl-caliber game for 15 minutes, they will still lose if they mail in the remaining 45.