The NFL released the 2009 NFL Schedule today, so I’ll do what the 4,000 other websites do and list some of the more juicier matchups of the year. (Although in the sake of being at least a little creative, I’ll list one interesting matchup for each of the 17 weeks on the schedule.)

Before we get to the matchups though, let me state for the record that it’s a complete farce that the Cowboys get six nationally televised games next year despite not making the playoffs last season. I guess “America’s Team” opening a brand new stadium is worth major national exposure…six times a year.

Week 1: Bears at Packers, 8:20PM ET
Jay Cutler’s first game in a Bears uniform will be at Lambeau against the rival Packers on Sunday Night Football. How much will John Madden overplay the, “The Bears finally have a quarterback” angle after every pass Cutler completes?

Week 2: Giants at Cowboys, 8:20PM ET
One of the ‘Boys six nationally televised games, Dallas will open up their new stadium against division rival New York on Sunday Night Football. How much will John Madden overplay the, “Tony Romo and Wade Phillips must win now because Jerry Jones built this brand new stadium and he wants a contender” angle?

Week 3: Falcons at Patriots, 1:00PM ET
The over/under on the number of times Matt Ryan is compared to Tom Brady in this game has officially been set at 800,994,990.

Week 4: Chargers at Steelers, 8:20PM ET
AFC Divisional Round rematch in Pittsburgh – let’s see if the Chargers can hold onto the ball for more than 17 seconds in the third quarter unlike the last time these two teams met.

Week 5: Patriots at Broncos, 4:15PM ET
If Bill Belichick shakes Josh McDaniels’ hand at midfield after this game, I’m calling shenanigans on the behalf of Eric Mangini.

Week 6: Bears at Falcons, 8:20PM ET
Here’s hoping the Bears’ secondary figured out that they have to cover the out pattern when that’s the only route Matt Ryan can look for when there’s 11 seconds on the clock and he needs to get his team into field goal range.

Week 7: Cardinals at Giants, 8:20PM ET
Kurt Warner seeks maximum revenge against Eli Manning for taking his starting job in New York in a few years ago. This is also the battle of two goofy (yet loveable) quarterbacks. (Look, I know Warner is a good guy but you have to admit those gloves he wears look ridiculous.)

Week 8: Giants at Eagles, 4:15PM ET
I’d write something humorous about this matchup, but there’s just nothing funny about the NFC East – or Philadelphia fans. People may die…

Week 9: Dolphins at Patriots, 1:00PM ET
The Big Tuna returns to his old stomping grounds in what could be a midseason battle for first place in the AFC East. Unless of course Miami was a fluke last year, Tom Brady re-injuries himself or the Bills and Jets are in first place by a wide margin. But seriously, if those things don’t happen, then this could be a midseason battle for first place in the AFC East.

Week 10: Patriots at Colts, 8:20PM ET
Tom Brady vs. Peyton Manning – finally, a forum where fans can debate who the best quarterback is in the NFL. I’m tired of not having the opportunity to discuss who the better quarterback is between Brady and Manning because these two teams never play each other.

Week 11: Chargers at Broncos, 4:15PM ET
Think Ed Hochuli’s crew will be asked to officiate this game?

Week 12: Packers at Lions, 12:30PM ET
Good to see the NFL is still honoring the tradition of keeping Thanksgiving in Detroit. Hopefully this game remains interesting for more than the seven and a half seconds that it was last year when the Titans drubbed the Lions in one of the worst Thanksgiving Day games since Drew Henson and the Cowboys took on Craig Krenzel and the Bears in 2004. (Does anyone remember that game? At one point during that game I actually cursed God for blessing me with vision.)

Week 13: Jets at Bills, 8:20PM ET
T.O. gets his first opportunity to play in front of a national audience in his new city of Buffalo…actually the game is being played in Toronto. Too bad only four people will get the chance to watch it since the game will be on the NFL Network.

Week 14: Panthers at Patriots, 1:00PM ET
Hopefully by this point in the season Tom Brady will be leading the Pats back to the playoffs and Jake Delhomme will have figured out how to get through an entire game without turning the ball over seven times and generally crapping himself. (Side note: There’s no proof that Delhomme has ever crapped himself during a game. I just flat out don’t like him.)

Week 15: Giants at Redskins, 8:30PM ET
Were the guys in charge pissed at the Giants when they were making this schedule? Check out this stretch of games to finish the season: vs. Dallas, vs. Philadelphia, at. Washington, vs. Carolina, at Minnesota. Yikes.

Week 16: Ravens at Steelers, 1:00PM ET
If this game is anything like the three these two teams played last year, we should expect plenty of anger, mass hysteria and controversy.

Week 17: Giants at Vikings, 1:00PM ET
Hey, remember when the Vikings needed to beat the Giants in Week 17 of the season last year in order to get into the playoffs? And they barely did, even though New York played its back ups for most of the game? Well this will be a replay of that game for those that missed it.

The competition committee will propose that when the ball comes loose when a quarterback is throwing, replay can be used to determine if it is a fumble or an incomplete pass. Such a change would resemble the rules alteration made for down-by-contact plays two years ago.

In the final minute of a game at Denver in Week 2, Hochuli ruled a ball that slipped from Broncos quarterback Jay Cutler’s grasp was an incomplete pass instead of a fumble. The ball was recovered by the Chargers and Hochuli later acknowledged his decision was wrong.

It would be a great change to the rule, although I’m sure Ed Hochuli is saying, “WTF? If the NFL had this rule in place last year, then I wouldn’t have been showered with an enormous amount of hate mail…so thanks NFL.”

Did they blow yet another call Saturday to aid the Ravens in their victory over the Titans?

Another game, another officiating error in the NFL. On a key 3rd and 2 with 2:52 remaining in today’s divisional playoff game between the Baltimore Ravens and Tennessee Titans, the play clock clearly expired well before Joe Flacco received the snap, but no delay of game call came from the officials.

The Ravens converted the first down on a long pass to Todd Heap, and ended up kicking the game winning field goal later in the drive.

It’s not uncommon for officials to miss the play clock hitting zero, but when they do the ball is snapped nearly immediately afterwards. On this play, the ball was snapped 1.35 seconds after the play clock expired (yes, I timed it). That might sound trivial, but it’s really, really not. It’s a long time. Watch the replay, it’s preposterous how long the back judge had to make the call.

This doesn’t excuse the Titans for giving up the first down on the 3rd and 2. Nor is it intended to suggest that the Ravens couldn’t have converted on 3rd and 7 after the penalty. The point is, they should have had to.

The game clock on the TV broadcast is not official, but it did look like the Ravens got away with one. Still, the Titans blew the game with their three turnovers, 12 penalties and inability to find the end zone without Chris Johnson. One play/call doesn’t make or break a game for a team.

Following their embarrassing 30-23 loss to the Buffalo Bills at home on Sunday, the Broncos are now one loss away from losing their grip on the AFC West and sending the San Diego Chargers to the playoffs.

All the Broncos had to do was beat a struggling Bills team at home and they would win the AFC West. All they had to do was beat a quarterback in Trent Edwards that hadn’t played in three weeks and score more points on a team that was ready to get the season over weeks ago. And yet the Broncos couldn’t do it.

I guess a win for the Chargers next week would be justice served. The Ed Hochuli game sent San Diego into a massive tailspin and gave Denver momentum for what should have been a season in which they won the AFC West. But a win for the Chargers would be sweet revenge and with the way things have gone this year in the NFL, would anyone be surprised if San Diego beat Denver and went to the playoffs with an 8-8 record? It would be pathetic but so what? Maybe if Hochuli gets the call right in the first meeting between these two teams, the Chargers wouldn’t have collapsed.

The Chargers have all the momentum now, will be playing at home and have a bad taste in their mouths from their loss to Denver in Week 2. Personally, I think San Diego is a lock to win next week.

1. Washington vs. BYU, Sept. 6: Granted, Washington lost every game this season, but they clearly had a shot to beat BYU in September. The Huskies’ quarterback Jake Locker scored a touchdown with two seconds left to bring his team within one. After diving into the end zone, Locker threw his hands — and the ball — into the air in, what appeared to be, a natural reaction of pure excitement. The ref, however, ruled the ball-flipping and jumping up and down to be “excessive celebration.” As a result, kicker Ryan Perkins was placed an extra 15 yards back, his game-tying extra point was blocked and the Huskies lost.

2. 2008 World Series, Game 3: An error by the first base umpire in Game 3 of the Fall Classic nearly gave the Tampa Bay Rays a series-turning win over the Phillies. It was the top of seventh, Rays at bat. Carl Crawford led off and tapped a well-placed bunt up the first-base line. The Phillies near-46-year-old Jamie Moyer dashed down the line, dove to field the ball and, in one graceful motion, tossed it to Ryan Howard at first, who snatched out of the air bare-handed with his foot on the bag. It looked as though Howard — with ball in hand — stood on the base awaiting Crawford’s arrival. The umpire thought otherwise. Safe! The Rays scored two subsequent runs to come back within one, but the Phillies managed to hang on to their lead for the win and, well, you know the rest.

3. Georgetown vs. Villanova, Feb. 11: Like Holmes’ catch, this one was all about the line. With the score tied at 53 apiece and only a second left on the clock, Georgetown’s Jonathan Wallace sped up the floor, dodging Villanova defenders. Still 70-something feet from the basket, Wallace heard the ref blow the whistle and, thinking there was no way a foul would be called in such a tight situation, Wallace assumed he stepped out of bounds. And when you assume you … I won’t go there. In short, the ref did the unthinkable and called a foul on ‘Nova’s Corey Stokes, gave Wallace two freebies at the line and handed Georgetown a 55-53 win.

4. Heat vs. Clippers, Nov. 29: Sometimes a bad call is any call. With Miami trailing 97-96 and the clock reading 7.6 seconds, Los Angeles’ Baron Davis inbounded the ball after a Miami score. With none of his teammates open, he heaved the ball down court, hoping a Clipper would miraculously take control. Dwayne Wade got it instead. As he grabbed the ball out of mid-air and was falling onto the scorers’ table, Wade threw the ball toward the three lone Heat players near the basket. The ref thought Wade had stepped out of bounds but, after reviewing the play, the steal was upheld. Unfortunately, the breakaway play was cut off, and the Heat was forced to inbounds, which resulted in the Clippers fouling and, ultimately, the Heat losing.

5. Broncos vs. Chargers, Sept. 14: Here you go, Ravens fans. If you thought your call was bad, think about how the Chargers felt on this one. With less than two minutes remaining, the Broncos lined up on the Chargers 1-yard line with the chance to tie the game. As Jay Cutler dropped back, the ball slipped out of his hands and into those of San Diego linebacker Tim Dobbins. As soon as the ball touched the ground, referee Ed Hochuli quickly — too quickly — blew his whistle. Hochuli ruled an incomplete pass, though the replay clearly showed it was a fumble. So, Denver regrouped, scored a touchdown, followed with a two-point conversion and won 39-38. Hochuli later apologized for his error.

You’ll never get a Charger fan to say this but I still feel bad for Hochuli. That guy has been a great ref throughout his career but he’ll always be remembered for this one mistake. Albeit it was a massive mistake, but still…

By now, most of us know what happened, but I’ll set the scene again for those who have missed out on all the hoopla.

Down 11-10 with five seconds remaining in the fourth quarter, the Chargers took possession at the 21-yard line. There, quarterback Philip Rivers threw a forward pass to LaDainian Tomlinson, who then flipped the ball backwards to teammate Chris Chambers, who then tossed the ball backwards to another teammate, but Steelers’ safety Troy Polamalu intervened, knocked the ball out of the air and recovered it on the 11-yard line. From there, Polamalu returned the ball into the end zone, which referees signaled a touchdown. Pending review and an extra point, the Steelers should have won 18-10.

But that’s not what happened. Officials did review the play and determined that it was in fact a touchdown. However, after reconvening, they determined that one of the Chargers’ lateral passes (the one Tomlinson threw) was an illegal forward pass and therefore the touchdown didn’t count.

No harm no foul, right? The Steelers would have won the game regardless and everyone involved can rejoice at the fact that no game in the history of the NFL has ever ended with an 11-10 score.

But the call wasn’t right. Even if LT’s pass was deemed illegal, the ball never touched the ground and therefore the play continues. The result of the play was an illegal forward pass, which the Steelers would have declined, and the touchdown should have counted. Head official Scott Green even admitted after the game that he and his crew “misinterpreted” the rule and got it wrong.

People may disagree, but this blunder is just as bad as the Ed Hochuli game because it proves that the replay system in the NFL is broken. The most amazing thing about all of this is that the officials in the Chargers-Steelers game actually spent time getting the call wrong. What happened if the Steelers were down by one and something fluke like this happened and it cost them a win? Can we safely assume that the officials would have gotten the call right if a win was on the line? I can’t, certainly not after watching how the officials eventually handled the actual situation.

Now let’s reintroduce the gambling ramifications, because obviously that’s the main issue here.

An estimated $100 million was wagered worldwide on the game. And approximately 66% of those dollars were wagered on Steelers. Had the touchdown stood, bettors would have cashed in roughly $32 million, but because of the officials’ mistake, it turned out to be a $64 million swing in favor of the bookies.

Some people don’t like gambling because they think it’s stupid to wager your hard earned money on a game. That’s fair, but don’t forget that some people consider gambling as another form of entertainment, just like going to the movies. I might be comparing apples to oranges here, but if you took your family to the movies and only got to see half of it because the projector broke, then you’d want your money back right? The projector cost you your money and entertainment for the night and that’s not fair.

Well, a blown call cost people their money (and we’re talking about more dough than the average movie ticket) and entertainment and that’s not fair either. Again, that might not be the best example but you get the point.

Don’t expect anything to be done about this though. Roger Goodell isn’t going to reverse the call just like he didn’t reverse the outcome of the Broncos-Chargers game that Hochuli blew. It was a mistake by the officials and I wouldn’t hold your breath hoping to get your money back.

But this is going to be more damaging to Goodell’s league than people think. I’m not one for conspiracy theories, but it’s certainly questionable that the Steelers were flagged 23 times to only twice for Chargers (one of those penalties was the infamous “illegal pass” call), and the end of the game resulted in a San Diego cover because they were 4 or 5-point underdogs at most major sports books.

People are justifiably outraged and calling for foul play. In the wake of what transpired in the NBA with Tim Donaghy, suspicions are being raised of the legitimacy of NFL officiating. With that much on the line, how can you blow a call after you first made the correct ruling, then reviewed it, then still made the correct ruling only to eventually make the incorrect ruling? It’s completely ridiculous and I don’t blame anybody if they think NFL games are fixed now.

For the record, I don’t think games are fixed and I certainly don’t think the end of the Chargers-Steelers game was some masterful plan to insure a San Diego cover. I think this was a massive mistake, but I highly doubt anyone got on the phone to the head ref to tell him to call the game a certain way. Too many jobs would be lost and I doubt it’s worth the risk.

But after watching everything play out, I can definitely see why people buy into conspiracy theories. And it’s too bad that this is mostly about gambling because the situation deserves to have some light shed on it. Instead, the mainstream media will bury the story because they want to remain hush-hush about the gambling world.

Even those who don’t bet and didn’t wager on the game witnessed an injustice. And maybe you didn’t lose money – maybe you lost a fantasy game or a football pool at work. Either way, what happened wasn’t right and the NFL is going to be the one that really pays in the end because it no doubt lost some fans due to this fiasco.

The 27-14 final suggests that Philadelphia soundly handled Atlanta, but it doesn’t provide the full story. Rookie QB Matt Ryan connected with Roddy White for his second touchdown pass of the game to cut the Eagles’ lead to 20-14 with just under four minutes remaining in the game.

After forcing Philly to go three and out on their next possession, the Falcons were set to get the ball back with just over two minutes left and no timeouts. But after returner Adam Jennings let a punt bounce at his feet, the refs called a muff and awarded the Eagles the ball at that spot. Replays clearly showed that the ball never touched Jennings but because the Falcons had used all of their timeouts, they couldn’t review it. Brian Westbrook (who had a huge day coming back from injury) then broke off a 39-yard touchdown run to put the game away.

Granted, Atlanta might not have scored anyway, but they never got the opportunity either. And it seems that more than ever, refs are way too flag-happy and it has cost teams chances to win ballgames. Earlier in this game, Trent Cole was flagged for a 15-yard personal foul penalty for a hit on Ryan that couldn’t have been a worse call. Cole hit him square and it wasn’t head-to-head or malicious at all.

I hate to talk about blown calls because they happen to every team every week. But they’ve seemed especially bad this year and it looks like they’ll continue throughout the season.