Report: Packers WR Christian Watson believed to have high-ankle sprain
If Watson does have a high-ankle sprain, he’s going to miss a significant amount of time.
Green Bay Packers wide receiver Christian Watson left Week 4 versus the Minnesota Vikings with an ankle injury after getting twisted up on a play where he was the targeted receiver on a play that resulted in an interception. While it initially looked like it could have been a knee injury, the Packers reported the injury as an ankle issue when they made the announcements that Watson was questionable and then later out against the Vikings.
Hours after the game, NFL reporter Jordan Schultz tweeted that the “early belief” is that Watson has a high-ankle sprain. In his post-game press conference, head coach Matt LaFleur stated that Watson believed he “just had a sprain” to his ankle, rather than any sort of break.
A high-ankle sprain is not some light injury, though. According to the Cleveland Clinic, a high-ankle sprain can take up to six to eight weeks to fully recover from.
Unless Watson gets some unexpectedly positive news on Monday, when the Packers will apparently run more tests on the receiver’s ankle, you can go ahead and bank on Watson being out of the lineup for a good chunk of the foreseeable future.
Once Watson left the receiver rotation in Week 4, there was an uptick in snaps for Dontayvion Wicks, Bo Melton and Malik Heath, the three receivers behind the starting trio of Watson, Jayden Reed and Romeo Doubs. Wicks was targeted 13 for five receptions, 78 yards and two touchdowns, Melton saw three targets for one reception and 28 yards and Heath caught both of his targets for 12 yards versus the Vikings.
Vikings running back Aaron Jones feels the love from Packers crowd in return to Lambeau Field
Jones, who played seven years in Green Bay, remains a fan favorite. People in green and purple jerseys alike applauded him before the Vikings’ 31-29 win.
Packers most to blame for Week 4 loss to Vikings
The Green Bay Packers nearly pulled off a miraculous comeback after trailing the Minnesota Vikings 28-0 on Sunday, but they ultimately fell 31-29, and largely due to self-inflicted errors.
This was a high-profile matchup coming into this weekend’s slate of games. The Vikings were one of the surprising teams of the season so far, coming into the matchup at 3-0, while the Packers were looking to get their first divisional win on the season and prevent Minnesota from going up two games on them in the standings.
The Vikings ended up coming out on top, but the Packers did show that if they play a clean game, they could possibly come out on top against perhaps the best team in the NFC so far this season. Reality is though, they are two games behind the Vikings in the standings now, having already lost one of the two games with them, and the remaining game against them on the road in the second to last week of the season. Green Bay will have to gain ground in the division over the course of the rest of the season.
There are some players who deserve the most blame for this loss, and let’s get to the three that stick out the most.
