SB Nation - Green Bay Packers

A "Brownie" For Your Thoughts - "Rookie" Post

SpecialBrownie — Wed, 11 Nov 2009 05:52:51 -0000

More photos » by Elaine Thompson - AP

2 days ago: Detroit Lions quarterback Matthew Stafford leaves the field after throwing an interception that was returned for a touchdown by Seattle Seahawks' Josh Wilson in the fourth quarter during an NFL football game Sunday, Nov. 8, 2009, in Seattle. The Seahawks won 32-20. (AP Photo/Elaine Thompson)

Browse more photos »

Welcome to a whole new segment on DBN, appropriately titled, A Brownie For Your Thoughts. This is a segment that will be ran once or twice a week and will talk about more off topic football stories. An example would be my uniform fanpost of a week or so ago. I will talk about an idea that has ran across my ever free flowing imagination, speak my own opinion on the subject and ask for all of yours in the comments. I hope you all enjoy it and receive it well!

Now, the title Rookie Post, is an allegoric title. While this may be my own rookie post, it is also a post on how rookies should be brought up in the NFL. Should rookies be thrown in or should they be taught on the sidelines for a period of time? Maybe there is no control when a rookie starts in a NFL game. I'll examine the possibilities...

I have thought of three ways a rookie can be brought up in the NFL, but only two of them can be considered valid choices by a head coach. "Plug and Play" Rookie starter, "Apprentice Rookie starter and "Injury Forced" Rookie starter.

1. "Plug and Play" Rookie Starter - A "Plug and Play" starter, or PaP for short, is what I consider to be when a coach decides to start a rookie in the very first game of the season. Examples of this can be seen with Matthew Stafford of the Detroit Lions or Mark Sanchez of the New York Jets. A lot goes into a PaP starter. How well did they perform in college? How desperate is the team for production and notoriety? Will the rookie get injured?

To save space, we'll just use Matthew Stafford for example purposes.

How well did Stafford perform in college?

Stats Overview	Passing
YEAR	CMP	ATT	YDS	CMP%	YPA	LNG	TD	INT	SACK	RAT
2006	135	256	1749	52.7	6.83	53	7	13	12	108.99
2007	194	348	2523	55.7	7.25	84	19	10	15	128.92
2008	235	383	3459	61.4	9.03	78	25	10	17	153.54

Check.

How desperate is the team for production and notoriety? Detroit Lions 0 - 16 in 2008. Check.

Will the rookie get injured? Stafford missed two games due to a knee injury. Sadly, Check.

PaP conclusion: Essentially, Stafford matches every boundary for a PaP starter, which he was amazingly. The Lions however, are 1 - 7. Stafford has a 5/12 TD to INT ratio and has a 55.9 rating. Now, many other factors play into this but ultimately, a PaP is a high risk/ high reward starter. So far, Stafford has not played out for the Lions. Then again, it is only Week 9 of the 2009 season. Personally, I've never been one for a PaP starter. I feel like you're throwing them to the "Lions" (Do - Do - Do - Chzzz). I agree more with the next type of Rookie starter...

"Apprentice" Starter - This one is short, sweet and opinionated. An "App" starter is one who sits by on the sidelines, learns from successful or smart veterans and is inserted into a starting role when prepared or at least more knowledgeable than a PaP starter. How can this be proven? It really can't; this is a low risk/ high reward approach. You don't know if any factors will change from a PaP starter but what's it going to hurt? Your rookie learns NFL experience before he experiences it. It can only help.

Let's look at Josh Freeman, another 1st Round rookie QB starter. The Tampa Bay Buccaneers went 0 - 7 until Freeman was named the starter for Week 8 against the Green Bay Packers. The first game Freeman was named starter, the Bucs won for the first time in the 2009 season! Freeman has a 3/1 TD to INT ratio and has a satisfying 83.2 rating. It's only been one game though so, really, who knows. Freeman seems to prove my un - provable point though.

App conclusion - LOW RISK/ HIGH REWARD. While you really don't satisfy the fan base or FO by holding back a high profile rookie, you let them learn from seasoned veterans who already know how to handle themselves in a NFL game. I see no real negatives to this approach all except for the negative notoriety. That will change though, once that studying rookie starts winning games.

"Injury Forced" Starter - This one can't be controlled by anyone. More specifically, this type of starter comes about when the starter above them goes down with an injury for at least one game, forcing the 2nd string rookie to start. This type can't be proven either since it can't be chosen. This one won't have a conclusion, just an explanation and example. It's basically a spontaneous split of the two "coach option" starters. As the 2nd string rookie, you're an App Rookie. Once the veteran above you goes down, said rookie morphs into a PaP Rookie, you have to go in regardless of knowledge or preparedness.

We'll use Kaluka Maiava for this example. Maiava had to come in for D' Qwell Jackson during the Pittsburgh Steelers game and started against the Green Bay Packers the week after. In both games combined, Maiava had a total of 10 tackles and one forced fumble. For an inside linebacker, those are decent stats for a span of two games. But who knows if he was even ready for the unexpectedness of Jackson's injury (he shouldn't have been, unless he planned it.) Maybe he'll get better challenging fellow rookie LB David Veikune for a starter spot or working beside veteran David Bowens. Who knows.

Well, there you go. My first ever post on my new segment. If you want, tell me how I did, critique me so the next post can be better. But please, above all else, TELL ME HOW YOU FEEL. Do you agree with these three types of rookies? Are there more types? Less? Please argue, agree and discuss. Thanks for reading and... GO BROWNS!

P.S. I will also be running the Power Rankings post which collects the Cleveland Browns power rankings from notable websites around the internet. It will usually be posted on Tuesdays or Wednesdays with "Brownie Thoughts" usually on Thursdays or Fridays.

Armageddon 2009: Patriots v. Colts

BigBlueShoe — Tue, 10 Nov 2009 16:40:02 -0000

More photos » by Winslow Townson - AP

New England Patriots quarterback Tom Brady (AP Photo/Winslow Townson)

Browse more photos »

This week, we get to gear up for (arguably) the most anticipated regular season game on the entire NFL schedule: The New England Patriots at the Indianapolis Colts. Despite both teams not playing in the same division, and despite both teams not facing in other in the playoffs since the now-legendary 2006 AFC Championship Game, this match-up is indeed still the best rivalry in pro football.

Hell, it might be the best rivalry in all of sports.

More people will likely watch this game than any Red Sox v. Yankees game that was played last baseball season. It will likely gain higher ratings than the World Series, the NBA Finals, or the excellent Hockey playoff match-up last season that pitted their game's best players (Capitals ace Alexander Ovechkin and Penguins phenom Sydney Crosby) against each other. And while football rivalries like Packers v. Vikings, Cowboys v. Giants, and Steelers v. Ravens feature impressive teams loaded with big stars who are followed by large fanbases, no two players get debated more than Tom Brady v. Peyton Manning. And there is a reason for this.

They are the best in the league; maybe ever.

With all due respect to Drew Brees, who is having an amazing year with the still undefeated Saints, he can't touch Tommy Terrific or Perfect Peyton. Brees has all the physical tools, but until we see him rise to the occasion and lead his team to a conference championship game win, one can't put him on Brady or Manning's level.

Personally, I have long maintained Peyton is better than Tom, and unlike many of the Pro-Brady faction, I actually have tangible evidence to back it up. Peyton has helped his team to more wins. He has more impressive career numbers than Brady. And, to put it bluntly, Peyton has had a bigger overall impact on the league than Tom.

That no-huddle, spread offense the Patriots have used since 2007? Yeah, Peyton brought that back en vogue ten years ago.

But regardless of where you fall in the debate, what many of us agree upon is that these two are, quite possibly, the best to ever play the position. And while the morons in the established media world might claim that this reason or that prevents Manning or Brady from being in the all-time discussion (remember Chris Collingsworth saying earlier this season that Peyton Manning needed to win one more championship to be considered on the same level as Dan Marino... why does this schmuck still have employment?), what we fans know is that time and again these two have DEFINED great quarterback play for an entire generation. And as these two continue to re-write history books, the classic Pats v. Colts rivalry has begun to take a turn.

More so than any other time before, the rivalry has evolved from a nasty, bitter slap fest into one of mutual respect. Sure, we think (and know) the Patriots are cheaters, and Patriots fans think our Colts are nothing but cry-babies who change the rules to help them win. However, despite the outward silliness (and name-calling fun) of the rivalry, both sides also know that both teams demand (and have earned) respect.

In addition, both fanbases also respect one another. For me, pro football suffers when the Pats v. Colts rivalry suffers. I know about a billion Patriots fans who likely agree with that sentiment.

Keep an eye out here and at Pats Pulpit for more lead-up to this excellent rivalry game.

Analysis: Packers Allow 21 Points In 13 Minutes

Brandon — Tue, 10 Nov 2009 15:00:59 -0000

More photos » by Steve Nesius - AP

Browse more photos »

From Tom Pelissero's always excellent film review:

If the Packers fail to make the playoffs, they may well look back at the final 13 minutes against the Bucs as their defining moments— a stretch that encapsulated everything that’s wrong at the season’s midway point...

Coverage breakdowns on special teams. Technique errors, nosy play and lack of pressure on defense. Protection problems, receivers who can’t get open, penalties, dropped passes and a quarterback with a time clock prone to going haywire.

Make no mistake, the Packers did a lot of things right in the season’s first half. But everything they did wrong showed up again in those final 13 minutes, and it’s a whole lot to fix with eight games to go.

A lot has to go wrong for a 21 point swing in a span of 13 minutes. I can't think of a single good play during that stretch. The only ones that come to mind are QB Aaron Rodgers's scramble for a 1st down and LB A.J. Hawk's INT, but of course those were both called back by penalties.

Mike McCarthy On The Packers Offensive Line

Brandon — Tue, 10 Nov 2009 13:00:37 -0000

by Steve Nesius - AP

View full size photo »

During his Monday press conference, Mike McCarthy said RT Mark Tauscher may play on Sunday against the Cowboys, or he may be out a couple weeks. Obviously former starter RT Allen Barbre would play in his place, but he hasn't played well all season.

McCarthy said he wouldn't switch the coaching responsibilities for the offensive line or special teams at this point. As much as James Campen's and Shawn Slocum's units have struggled, it's not like he can go out and sign Bobby April and Alex Gibbs right now to replace them. The only coaches apparently available at this time of year are in semi-retirement and calling bingo.

Though it does look like T.J. Lang is set to replace Daryn Colledge at left guard, according to the Journal-Sentinel. Of course it would be great if Jason Spitz could step in, but he's unfortunately done for the season. It's about time for Colledge's benching. He gave up a lot of sacks for a guard in 2008, and I've been hoping for his benching since the game in Minneapolis. Actually I don't know how he got his job back after he was benched in 2007.

McCarthy was pretty clear about what needed to be done:

We don't need wholesale change. We may need to adjust some things and that will be our focus. But as far as going outside the building, I'm not going to sit here and tell you that I have all the answers, but I'm very confident in the issues that we've had in pass protection, that they are correctable.

Which is fine, but I wonder if he meant correctable this season. Or with the players currently on the roster. Contrast that statement to something he said after the Bengals game when DE Antwan Odom had 5 sacks:

At some point, you have to win the one-on-one battle with the help being secondary instead of a primary focus.

They were losing one-on-one battles back in week 2, and it hasn't looked much better since then. If your players can't win the one-on-one battles, the only thing would seem to correct the problem is new players.

The Status of Aaron Kampman

Brandon — Tue, 10 Nov 2009 06:31:36 -0000

More photos » by Brian Blanco - AP

Browse more photos »

I noted in the Green Bay Packers game recap that LB Aaron Kampman was bad in coverage on the TD pass to RB Derrick Ward in the 1st quarter. It was a surprise that he was ineffective against the Buccaneers. His main opponent was RT Jeremy Trueblood, who as far as I know is good but not heading to the Pro Bowl. But Kampman occasionally has a game when he doesn't make a big impact.

It turned out he suffered a concussion on the 4th play of the game, but he played until the middle of the 4th quarter. He might not play at all next Sunday against the Cowboys.

With only 2.5 sacks this season, the transition to the 3-4 hasn't been a huge success for him. Something he apparently was worried about when he didn't speak to the media back in May. But he has had many opportunities to lineup as a down lineman, and he hasn't often taken advantage of those opportunities either.

The big problem with his absence is that he'll be replaced by some combination of LB Jeremy Thompson and LB Brady Poppinga. Due to various injuries, Thompson has rarely played outside LB in a game this season or preseason. He's an unknown in some respects, although we've seen him play some at defensive end last season. I know what Poppinga can do, and he's a significant step down from Kampman, but the coaches seem to love him. Rookie LB Brad Jones is another option, but he's an unknown too.

There's not a lot of good options here if Kampman can't play. Who's the best one?

Recap: Green Bay Packers Stunned By Buccaneers 38-28

Brandon — Mon, 09 Nov 2009 13:00:54 -0000

by Brian Blanco - AP

View full size photo »

Writing this recap has been brutal. Losing to an 0-7 team is always hard. But looking back at the game, they did so many things right.

Team	First Downs	Yards	Yards/Carry	TOP
Packers	20	404	5.3	35:17
Buccaneers	17	279	3.2	24:43

But then the special teams failed them (blocked punt for TD; 83 yard kickoff return allowed) and the defense, which played great outside the red zone, allowed 3 TDs on all 3 Tampa trips into the red zone. It's bad to have 6 sacks (and 12 QB hits), as the offensive line continues on it's historically awful pace, yet they still scored 28 points. You should win the game if you score 28 points.

In that sense, this loss was very similar to the loss last week to the Vikings. Awful special teams gave the Bucs (and Vikings) a huge field position advantage, and the inability of the defense to hold their opponents to FG attempts in the red zone put the score out of reach. The offense has scored 26 and 28 points in those 2 losses. But it's seemingly impossible for the offense to score more than that with the awful pass protection.

I have a hard time blaming QB Aaron Rodgers. Despite 3 INTs, he did score 3 TDs. They have to be able to win games even when he has a couple turnovers. And I don't count the last INT that was returned for a TD against him since it was a 4th down desperation play.

"We've got to get to work as soon as possible on Dallas," said Mike McCarthy at his post-game press conference. What else can they do? They aren't going to find a consistent pass rush sometime this season. Maybe they can find someone to do a better job on kick coverage and special teams blocking. And the good news is that RT Mark Tauscher's knee injury does not appear to be serious, according to the Press-Gazette, so once he returns (again) and they bench LG Daryn Colledge, the offensive line could actually improve. I'm just fed up with Colledge. He mixes in a couple good games with a stinker like this. He's been doing that in each of his 4 seasons. Though as I mention above, it's not exactly the offense that's the problem.

The remaining schedule is a little rougher. Next week against the Cowboys looks tough. The game in Pittsburgh on December 20 is another bad one. But the rest of them are all winnable games against teams with problems of their own (49ers, Lions, Ravens, Bears and Seahawks). I'd put the Cardinals into the tough category, but it's hard to tell with them since they mix in good wins (Giants, Bears) with a stinker loss (Panthers).

Just focus on a win each week and battle for a Wild Card spot. Play-by-play recap after the jump.

Packers vs Buccaneers coverage; Packers vs Buccaneers recap; Packers vs Buccaneers boxscore.

The play-by-play from NFL.com:

First Quarter

(12:27) 12-A.Rodgers pass deep right to 89-J.Jones for 74 yards, TOUCHDOWN.

Obviously it was a great pass, and a great run by WR James Jones. It's really disappointing to remember how good the pass protection was early in the game, and how it deteriorated as the game went on.

(9:48) 12-A.Rodgers pass deep middle intended for 80-D.Driver INTERCEPTED by 33-E.Mack at GB 44. 33-E.Mack to GB 8 for 36 yards (12-A.Rodgers).

Mike McCarthy said in the post-game press conference that Rodgers just didn't see the cornerback in Tampa's base defense.

(8:52) (Shotgun) 5-J.Freeman pass short right to 28-D.Ward for 6 yards, TOUCHDOWN.

Yes, LB Aaron Kampman isn't very good in pass coverage. But obviously it's really hard for the defense to prevent a score when the Bucs only have to go 8 yards after the INT.

(8:02) 25-R.Grant left tackle to TB 44 for 20 yards (36-T.Jackson).

There were a couple times when RB Ryan Grant almost broke a big run. It was a horrible game for the offensive line, but they did manage to open up some running lanes against the Bucs awful run defense.

Second Quarter:

(12:09) (Punt formation) 7-J.Kapinos punt is BLOCKED by 54-G.Hayes, Center-61-B.Goode, RECOVERED by TB-20-R.Barber at GB 31. 20-R.Barber for 31 yards, TOUCHDOWN.

Tom Silverstein said that FB John Kuhn failed to pick up the LB who blocked the punt.

(7:46) 12-A.Rodgers pass deep right to 80-D.Driver for 32 yards, TOUCHDOWN.

A great route by WR Donald Driver. He faked CB Ronde Barber into believing a slant route, and then sprinted down the sideline. And made a difficult over the shoulder catch while dancing around in the pylon.

(6:49) 5-J.Freeman Aborted. 52-J.Faine FUMBLES at TB 3, recovered by TB-5-J.Freeman at TB 3. 5-J.Freeman to TB 3 for no gain (77-C.Jenkins).

I thought QB Josh Freeman had 2 botched fumbles, but apparently this was the only one. It was 1 of 2 recorded fumbles, the other was a botched lateral, but neither fumble bounced the Packers' way.

(5:21) (Shotgun) PENALTY on GB-70-T.Lang, False Start, 5 yards, enforced at TB 45 - No Play.

McCarthy had talked about rotating tackles, and at this point LT T.J. Lang came in for LT Chad Clifton for 2 plays. Rodgers wasn't sacked at all during the 1st half, but then Lang committed this penalty, allowed a hit on Rodgers, and was pulled for Clifton by 3rd down. I don't recall seeing him the rest of the game.

(3:11) 5-J.Freeman pass deep left intended for 85-M.Stovall INTERCEPTED by 36-N.Collins at GB 41. 36-N.Collins to TB 46 for 13 yards (85-M.Stovall).

Freeman's accuracy was bad, he only completed 45% of his passes, but this was his only INT. His accuracy did seem to improve in the red zone.

(2:49) (Shotgun) 12-A.Rodgers pass incomplete short middle to 80-D.Driver.

Then the offense did nothing with their best starting field position of the day. It also gave the Bucs another opportunity on offense and Freeman had his best drive of the 1st half which led to a FG. This was easily a 6 point swing if the Packers could have gotten a couple 1st downs after the INT.

Third Quarter:

(14:17) 12-A.Rodgers sacked at GB 1 for -5 yards (sack split by 91-S.White and 95-C.Hovan). Tampa Bay challenged the safety ruling, and the play was Upheld. (Timeout #1.)

Though RT Allen Barbre came in for Tauscher, the 1st sack, and most pressure thereafter, came from the left side. It wasn't anything complicated; they just went in for the bull rush and overpowered the left side (Colledge and Clifton) of the line. DE Stylez White doubled his sack total from 1.5 to 3 in this game.

(10:20) 12-A.Rodgers sacked at GB 27 for -5 yards (71-M.Bennett).

A defensive tackle the Bucs picked up off waivers a few weeks ago threw TE Donald Lee out of the way for the sack.

(8:17) 12-A.Rodgers pass deep middle intended for 85-G.Jennings INTERCEPTED by 25-A.Talib (41-C.Lynch) at TB 1. 25-A.Talib to TB 16 for 15 yards (80-D.Driver).

Another missed opportunity on offense. A 1st down in Tampa territory and Rodgers lofts this one into triple coverage. Though Driver put a huge hit on CB Aqib Talib. Just a bad decision by Rodgers. It took potential points away from the Packers, but the Bucs didn't do anything with the ball on offense.

(6:40) 5-J.Freeman pass incomplete short right to 34-E.Graham.

(1:51) (Shotgun) 5-J.Freeman pass incomplete short right to 18-S.Stroughter (24-J.Bush).

The Packers run defense was very good again in this game. The Bucs have been able to run the ball a little this season, but they didn't do anything against the Packers. On 2 consecutive 3rd and short plays, the Bucs decided to throw instead and failed to convert either.

Fourth Quarter

(13:39) (Shotgun) 12-A.Rodgers sacked at TB 12 for -6 yards (93-R.Miller).

This was a coverage sack. Rodgers was just waiting for something that never opened up.

(13:04) (Shotgun) 12-A.Rodgers scrambles left end for 12 yards, TOUCHDOWN.

But he made good on the next play with the TD run. They ran 6 of 9 plays on this drive out of the shotgun.

2-M.Crosby kicks 70 yards from GB 30 to TB 0. 22-C.Smith to GB 17 for 83 yards (38-T.Williams).

No 11 point lead is safe from the Packers' special teams. K Mason Crosby was supposed to kick it left, according to Tom Silverstein, but it went straight down the middle where the coverage was weak.

(11:44) (Shotgun) 5-J.Freeman pass short left to 82-K.Winslow for 7 yards, TOUCHDOWN.

The big problem in the red zone was Freeman just too well protected. He had time to wait, on this TD he rolled to his left with no pressure. The Packers have been burned this season on the blitz, but rushing only 4 down lineman has produced so little pass pressure. It really hurt that Kampman was out by this point with a head injury. LB Brady Poppinga did nothing as his replacement.

(7:29) (Shotgun) 12-A.Rodgers pass incomplete short middle to 41-S.Havner [91-S.White].

After the Tampa TD, the Packers call 6 straight running plays, and this 3rd down pass fails. An awful punt nets them only 22 yards.

(5:58) (Shotgun) 5-J.Freeman pass deep left to 80-M.Clayton to GB 13 for 29 yards (31-A.Harris).

(4:20) (Shotgun) 5-J.Freeman pass short right to 18-S.Stroughter for 7 yards, TOUCHDOWN.

Again, I don't recall any noticeable pressure on Freeman during this drive. It's not like Freeman's accuracy was greatly improved, I thought that pass to WR Michael Clayton was tipped except it was just under thrown. Though the TD pass was well thrown.

(4:14) (Shotgun) 12-A.Rodgers sacked at GB 13 for -7 yards (98-R.Sims).

(3:05) (Shotgun) 12-A.Rodgers scrambles right end ran ob at GB 32 for 8 yards. PENALTY on GB-73-D.Colledge, Offensive Holding, 10 yards, enforced at GB 24 - No Play.

(2:57) (Shotgun) 12-A.Rodgers sacked at GB 14 for 0 yards (96-T.Crowder).

The first sack should be on RG Josh Sitton. The lineman knocked him back, ran around him up the middle, and collapsed the pocket. Rodgers recovers for a 1st down run, but Colledge only prevented a sack by committing a holding penalty. Last week, Barbre was benched after a critical late holding penalty ended any chance at a rally. This week, Colledge did the same thing and should get benched too. As far as I remember, the final sack on this series (it's hard to keep them all straight) was a total collapse but DE Tim Crowder got credit for it.

(1:31) (Shotgun) 12-A.Rodgers sacked at GB 4 for -9 yards (91-S.White).

(:52) (Shotgun) 12-A.Rodgers pass deep left intended for 80-D.Driver INTERCEPTED by 36-T.Jackson at GB 35. 36-T.Jackson for 35 yards, TOUCHDOWN.

Another sack is one of the reasons, on 4th and 12, Rodgers has to throw a desperate pass to Driver in double coverage that's picked off. The defense gave them another chance, but the o-line couldn't stop the bull rush and the receivers couldn't get open.

Brief Recap: Green Bay Packers Stunned By Bucs 38-28

Brandon — Sun, 08 Nov 2009 21:40:38 -0000

More photos » by Chris O'Meara - AP

2 days ago: Tampa Bay Buccaneers rookie quarterback Josh Freeman (5) fires a first-quarter pass against the Green Bay Packers during an NFL football game Sunday, Nov. 8, 2009, in Tampa, Fla. (AP Photo/Chris O'Meara)

Browse more photos »

There's plenty of blame to go around when you lose to the worst team in the NFL. The Packers got outplayed in a lot of ways. QB Aaron Rodgers had his worst game of the season. The offensive line still can't pass protect. And the defense can't make a stop in the red zone. Just a horrible day on special teams too.

Who played the worst in this game? My vote goes to the special teams because they were so badly outplayed.

How to Win On Your Bye Week

Gonzo — Sun, 08 Nov 2009 21:35:05 -0000

More photos » by Nam Y Huh - AP

Pictured: Chicago Bears' quarterback Jeff George. Not pictured: Jay Cutler (AP Photo/Nam Y. Huh)

Browse more photos »

Step 1 - Watch Jeff George v2.0 and the Bears get completely undressed at home by Kurt Warner, Larry Fitzgerald and company.

Step 2 - Watch the Green Bay Packers ensure that there will be NO winless teams in the National Football League in 2009.

And. . .well, that's all you need, really.

So, if the Vikings play .500 ball the rest of the way. . .the Bears would have to go 7-1 to catch them (and, presumably, hope that that one loss isn't to the Vikings), and the Packers would have to go 8-0 in order to catch them for the NFC North division title.

I don't want to say it's over. . .but there's a rather large woman off-stage there getting her vocal chords warmed up.

GAME DAY PROGRAM- (Orange) Bucs hosting Packers

Niko Houllis — Sun, 08 Nov 2009 13:15:09 -0000

Its here. Whether you've been waiting for 13 years, or 30 years, The Bucs have something for you. Bucco Bruce will return since he was forced to walk the plank over a decade ago, and he will mirror the 1976 uniforms that the Bucs only wore in preseason that year. The team, doing their best throwback impression all year, is looking for their first win of the season, and first since Monte Kiffin announced he would not return last season prior to the Carolina game on Monday Night Football.

Enjoy the HUGE digital program/Media Guide for todays game! Download it here.. week 9 PDF Program

How Could Flex Scheduling Potentially Affect the Minnesota Vikings?

Gonzo — Sun, 08 Nov 2009 12:00:42 -0000

Anthony Carter. . .not THE Anthony Carter, I assume, but who knows. . .brought up something worth pondering in one of the FanPosts yesterday, and that's whether or not the NFL's "flex scheduling" rules will affect the Minnesota Vikings in some way, shape, or form as we move down the stretch. It's getting to that time of year, and the Vikings are becoming a bit of a hot ticket, so it might be worth examining if any of the Beloved Purple's games could end up getting placed into a prime-time slot.

For those unfamiliar with the rules of the flex scheduling, here's a rundown, and we'll look more specifically at the Vikings after the jump.

-Begins Sunday of Week 11
-In effect during Weeks 11-17
-Only Sunday afternoon games are subject to being moved into the Sunday night window.
-The game that has been tentatively scheduled for Sunday night during flex weeks will be listed at 8:15 p.m. ET.
-The majority of games on Sundays will be listed at 1:00 p.m. ET during flex weeks except for games played in Pacific or Mountain Time zones which will be listed at 4:05 or 4:15 p.m. ET.
-No impact on Thursday, Saturday or Monday night games.
-The NFL will decide (after consultation with CBS, FOX, NBC) and announce as early as possible the game being played at 8:15 p.m. ET. The announcement will come no later than 12 days prior to the game. The NFL may also announce games moving to 4:05 p.m. ET and 4:15 p.m. ET.
-Week 17 start time changes could be decided on 6 days notice to ensure a game with playoff implications.
-The NBC Sunday night time slot in "flex" weeks will list the game that has been tentatively scheduled for Sunday night.
-Fans and ticket holders must be aware that NFL games in flex weeks are subject to change 12 days in advance (6 days in Week 17) and should plan accordingly.
-NFL schedules all games.
-Teams will be informed as soon as they are no longer under consideration or eligible for a move to Sunday night.

Now, the one thing that hurts the Vikings when it comes to flex scheduling is that they only have one game this season against a team from the NFC East. . .and ~~official studies~~ casual observations by people that have even an iota of common sense have shown that games involving one or more teams from the NFC East are ten to fifteen times more likely to end up on NBC's Sunday Night Football than games that don't involve any NFC East teams. (Hey, if you think I'm making that up, go back and look at the SNF schedule since it moved to NBC. The imbalance is freaking outrageous.)

So, how many of the Vikings' last seven games have a chance to get flexed into a prime-time slot? Let's take a look at this week by week. . .both the Vikings' scheduled opponent for that week, and the game that NBC has tentatively scheduled for the Sunday night slot.

Week 11
Vikings schedule: vs. Seattle
Current SNF game: Philadelphia at Chicago

There's no way that Seattle at Minnesota is intriguing enough for the NFL's schedule makers to move to Sunday night. The Seahawks have been pretty bad this year. . .they'll be 4-5 at best coming into the Metrodome (more than likely 3-6) and aren't looking at a whole lot of post-season prospects, so I don't give this game much of a chance of being flexed. I don't know if Philly/Chicago will stay in that spot, though. . .there's a pretty juicy looking matchup with Indianapolis traveling to Baltimore that would look good in that spot. However, NBC has a game that fulfills their NFC East criteria, so I don't see the current game being moved from its slot.

Week 12
Vikings schedule: vs. Chicago
Current SNF game: Pittsburgh at Baltimore

Sufficient to say. . .I think NBC has exactly the game they want for Week 12. The Bears, despite not being that good in 2008, were somehow scheduled for five prime-time appearances this season, based largely on their acquisition of Jeff George v2.0 to be their starting QB. How many NFL and network executives do you suppose are kicking their own asses over that brilliant idea right now? (I, personally, hope that somebody has been fired for their ignorance.) So, I think that the NFL would like to forget that fiasco, and I think the only way the Bears are going to get flexed into prime time is if they somehow go against a team from the Lingerie Football League.

Week 13
Vikings schedule: at Arizona
Current SNF game: New England at Miami

This could provide NBC with an intriguing option. The Cardinals, if they can turn it around, should be in position to take the NFC West title again, and after all, they are the defending NFC champions. There's the angle of Warner vs. Favre to look at as well. The only other game that appears to be a candidate to be moved would be Philadelphia at Atlanta. NBC could very well keep the game they currently have, but the Dolphins haven't had a lot of success this year against teams not named the New York Jets, and are fading a bit quickly in the AFC. But I think this game definitely has some flex potential.

Week 14
Vikings schedule: vs. Cincinnati
Current SNF game: Philadelphia at New York Giants

NBC currently has a game that features not one, but TWO NFC East teams scheduled for this week, so we can probably take that game away from NBC when we pry it from their cold, dead hands. But Bengals/Vikings, based on the way things look right now, might be the best game of Week 14. We have the Saints/Falcons rematch, but they've already had one prime-time game, and there's a game between the Chargers and Cowboys that could potentially have some post-season implications for both teams, but again. . .I'd be surprised if the current game gets moved from Week 14 at all.

Week 15
Vikings schedule: at Carolina
Current SNF game: Minnesota at Carolina

The Vikings are already scheduled for Sunday night in Week 15. . .but is there a chance they could get flexed out? The Panthers haven't been very good, and if Jake Delhomme keeps performing like. . .well, like Jake Delhomme. . .there's a very good chance that they'll already be looking to 2010 by the time this game comes around. There are two other solid possibilities for flex scheduling this week, those being Packers at Steelers and Chargers at Bengals. If Carolina's season continues to keep trending south, I wouldn't be surprised to see the Vikings get bumped to an afternoon slot in favor of one of those two games.

Week 16
Vikings schedule: at Chicago (Monday night)
Current SNF game: Dallas at Washington

Monday night games can't be affected by flex scheduling, so there is no chance that the Vikings will conclude their season sweep of the Bears at any time but Monday night. Will Dallas and Washington remain on Sunday night that week? There is a matchup between the Ravens and Steelers out there, although that would make a second SNF matchup for those two teams, as well as the Broncos traveling to Philadelphia to take on the Eagles. It will be interesting to see whether this game gets changed.

Week 17
Vikings schedule: vs. New York Giants
Current SNF game: None

The Week 17 SNF matchup won't be decided until after the Week 16 games have concluded. . .presumably by Sunday night, since the Monday nighter that week should have no post-season implications (except, possibly, for home field advantage through the NFC playoffs for the Vikings). This game could potentially have implications for a first-round bye, among other things, so there's a chance that Giants/Vikings could be the Sunday night game of choice. From the look of the schedule right now, the only other game that appears to have the remote possibility of intrigue is Green Bay at Arizona. . .the rest of the Week 17 matchups look like real stinkers, for the most part.

So, the Vikings do have a bit of flex possibility for the last seven games of 2009. Hopefully the league will see that the Vikings should be in prime-time more frequently. . .certainly more than their division rivals deserve to be. . .and adjust the schedule accordingly.

EDIT: DangerDale has pointed out a thread over at The 506 that says both CBS and FOX get to protect five games from flex scheduling. According to that list, the protected games are as follows:

FOX: Washington/Dallas (Week 11), Chicago/Minnesota (Week 12), Dallas/New York Giants (Week 13), Green Bay/Chicago (Week 14), Green Bay/Pittsburgh (Week 15)
CBS: New York Jets/New England (Week 11), Tennessee/Indianapolis (Week 13), San Diego/Dallas (Week 14), Cincinnati/San Diego (Week 15), Baltimore/Pittsburgh (Week 16)