Christian Darrisaw’s Knee, the Vikings’ Gamble, and a Risk That’s Hard to Justify
The Minnesota Vikings have been walking a tightrope all season with Christian Darrisaw - and it’s starting to look more like a misstep than a calculated risk.
When Darrisaw tore his left ACL and MCL in October 2024, it was clear he’d be sidelined for a significant stretch. That’s no minor injury, especially for a left tackle - the anchor of the offensive line and the blindside protector for a young quarterback.
Still, Darrisaw made his return in Week 3 against the Bengals, logging 38 snaps in a blowout win. It was a promising sign, but in hindsight, maybe it was too soon.
From there, the pattern started: flashes of normalcy followed by setbacks, and a creeping sense that the Vikings were trying to thread a needle with a player who simply wasn’t ready for the full workload.
In Week 4, Darrisaw played every snap against the Steelers in Dublin. The following week in London against the Browns, he was suddenly off the field at the start of the fourth quarter - just as the Vikings were mounting a comeback.
That raised eyebrows, and not without reason. Reporters quickly confirmed that Darrisaw had hit a pre-determined snap limit.
Head coach Kevin O’Connell didn’t hide his frustration postgame - losing your franchise tackle in crunch time isn’t ideal, no matter the plan.
After the Week 6 bye, Darrisaw was back to playing every snap in Week 7 against the Eagles. But the short turnaround for Week 8 against the Chargers brought more uncertainty.
He was listed as questionable - not for rest or maintenance, but with a knee issue. That designation opened the door to more questions, and ESPN’s Kevin Seifert later reported that Darrisaw had actually pulled himself out of the Browns game.
That’s not something players do lightly, especially at that level.
Against the Chargers, Darrisaw went through pregame workouts and was active, but he only lasted nine snaps before exiting. He didn’t return. O’Connell’s postgame comments didn’t clear much up, and the situation grew murkier.
To his credit, Darrisaw bounced back and played full games over the next three weeks. But it wasn’t long before the injury bug struck again.
He left the Week 12 matchup against the Packers early, missed Week 13 versus Seattle, and saw limited action in a Week 14 blowout win over Washington. Then came Week 15 - a win over the Cowboys, but one that Darrisaw missed entirely due to reported swelling in that surgically repaired left knee.
By then, the Vikings had already been eliminated from playoff contention.
So here we are, with three games left in a season that’s already slipping into the rearview mirror, and the Vikings are still evaluating Darrisaw “week to week.” That was the word from O’Connell on Monday, per Seifert.
But it’s fair to ask: what’s left to evaluate?
Let’s call it what it is - Darrisaw hasn’t been fully healthy all season. And while hindsight always offers clarity, it’s hard not to look back at Week 3 and wonder if the Vikings rushed him back.
The fact that he pulled himself out of a game speaks volumes. NFL players pride themselves on toughness, and offensive linemen might be the toughest of the bunch.
For Darrisaw to make that call says everything about how he was feeling - and maybe about the pressure he was under.
There’s also the broader picture. This isn’t just about one player - it’s about protecting your investment in the future.
Rookie quarterback J.J. McCarthy is trying to find his footing, and having a healthy, All-Pro-caliber left tackle makes a world of difference.
But if Darrisaw is playing at 70 percent - or worse - he’s not helping McCarthy. He might even be putting him at greater risk.
Ben Goessling of the Star Tribune put it bluntly during a radio appearance this week: the weekly “cat-and-mouse game” with Darrisaw’s health has dragged on far too long. Fourteen months post-surgery, and the Vikings are still guessing.
Goessling doesn’t believe the team plans to shut Darrisaw down, even if there’s a strong argument for doing so. And that’s the dilemma - balancing short-term reps for your rookie QB against the long-term health of your cornerstone left tackle.
But let’s be real - the reward here doesn’t outweigh the risk. Not with three meaningless games left on the schedule, and not with Darrisaw’s knee still clearly an issue.
Week 16 brings a trip to MetLife Stadium, widely considered the worst field surface in the league. That’s not just a narrative - it’s a reputation earned through years of injuries and complaints from players.
Putting Darrisaw out there on that turf, with a knee that’s been barking all year? That’s a gamble that borders on reckless.
If he’s not healthy - and at this point, there’s little reason to believe he is - then there’s nothing to be gained by having him suit up again this season. The focus should be on getting him right for 2026, not squeezing out a few more snaps in a lost campaign. The risk of compounding the injury and creating a bigger issue heading into the offseason simply isn’t worth it.
And yet, based on how this season has played out, it wouldn’t be surprising to see Darrisaw on the field again - whether by his own drive, team pressure, or some combination of the two.
But the Vikings have to think bigger. This isn’t just about the next three weeks. It’s about the next three years.