Matt Flynn (15) is tackled by Washington Redskins nose tackle Barry Cofield (96) in the fourth quarter at O.co Coliseum. The Redskins defeated the Raiders 24-14. Mandatory Credit: Cary Edmondson-USA TODAY Sports

Green Bay Packers not interested in Matt Flynn due to elbow injury

Many wondered if the Green Bay Packers would be interested in a reunion with QB Matt Flynn following his unsurprising release from the Oakland Raiders, but it sounds like that won’t be happening right now. According to ESPN’s Ed Werder, the Green Bay Packers “would have been interested” in bringing back Matt Flynn, but they believe that his elbow injury is a big enough issue to deter them from bringing him in as a much-needed backup QB for Aaron Rodgers.

Re-signing Matt Flynn  would make sense for the Packers, because he is very familiar with the team and had success backing up Rodgers in cases of emergency. Beyond that, it would be the best opportunity for him to be a backup (he’s not going to start anywhere after his play with the Raiders), and the Packers do need a backup quarterback.

That said, the Packers are wise to be scared off by Flynn’s elbow issue, because it has cropped up during his time with the Raiders. In fact, I think it’s the reason why Flynn has struggled to throw the ball downfield, and he will need to get his elbow healed up in order to be effective enough to sign somewhere. It could be that the Packers are concerned for no reason, but that also means that Flynn’s struggles are 100% on him. He isn’t a good quarterback, but he should be a bit better than he has shown in Oakland.

Mike McCarthy recently stated that the Green Bay Packers are not interested in Flynn, and he also gave a vote of confidence in Seneca Wallace. If the Packers actually decide to sign Matt Flynn, then it wouldn’t come soon.

You can follow Joe Soriano on Twitter for more NFL updates and analysis @SorianoJoe. Be sure to like us on Facebook here and follow our site on Twitter as well.

Tags: Green Bay Packers Matt Flynn Rumors

comments powered by Disqus