Everything is FREE until August 1free through July 31 →
Back to Blog
InjuryNFL2026-08-13

Isiah Pacheco's MCL Sprain Should Not Cost Him Week 1, and It Just Made Jahmyr Gibbs's Handcuff Cheaper

By Verdexed Fantasy Desk

Detroit running back Isiah Pacheco is dealing with a sprained MCL, an injury that cost him four consecutive training camp practices before the Lions confirmed the diagnosis. Head coach Dan Campbell indicated the team feels good about his availability and that Pacheco is expected to be ready for Week 1, when Detroit opens at home against New Orleans.

That is a materially better outcome than the initial silence suggested, and it restores the backfield structure the Lions built this offseason.

The injury, in the right category

MCL sprains span a wide range. A low-grade sprain is typically a two-to-four week absence with no surgical component and no lasting effect on burst or cutting once healed. A high-grade sprain is a different conversation entirely, often involving a brace, a longer ramp, and lingering discomfort into the season.

Everything in the reporting points to the first category. The Lions did not place Pacheco on any list, Campbell publicly framed Week 1 as the expectation, and Pacheco missed practices rather than being shut down. Nothing has been reported about imaging results beyond the sprain designation, and no surgical option has been raised.

The distinction that matters for fantasy: an MCL sprain that resolves in August has essentially no predictive value for the rest of the season. It is not a soft-tissue injury with a recurrence pattern, and it is not a structural knee injury. It is a joint sprain with a healing timeline.

What Pacheco is actually being asked to do in Detroit

Pacheco signed with the Lions this offseason on a one-year deal after four seasons in Kansas City, and he arrived into a defined role: backup to Jahmyr Gibbs. That role became more clearly defined when David Montgomery departed and Detroit committed to Gibbs as the centerpiece with a long-term extension earlier this month.

The Lions did not sign Pacheco to compete for the lead job. They signed him to be the thing they lost when Montgomery left, which is a physical complement who can take short-yardage and closing-time carries and, critically, absorb the full workload if Gibbs misses time.

That last function is where his fantasy value lives, and it is worth more in Detroit than the same function would be worth almost anywhere else. The Lions run one of the league's most productive offenses, they run it through the backfield, and they score often enough that the touchdown equity attached to any Detroit running back is substantial.

Fantasy fallout

Gibbs is a first-round pick whose price already assumed a healthy backfield behind him, and the Pacheco injury changed nothing about that. If anything, a brief August absence for the backup slightly reduces the risk that the Lions get cute with a committee, since Gibbs has taken the reps.

Pacheco is the more interesting asset. His value is almost entirely contingent, and contingent value in a top-five offense is the single most reliably underpriced commodity in fantasy football. The market prices backups by name recognition and by their standalone weekly output, both of which understate what happens when the starter in an elite offense misses two games.

The practical approach:

Draft Pacheco later than his talent suggests and earlier than his current role suggests. He is a bench stash, not a flex play, but he is the specific bench stash that wins a league if it hits.

If you draft Gibbs, take Pacheco. This is one of the cleanest handcuff pairings in football because the backup role is unambiguous. There is no third back with a claim, and Detroit has no reason to invent one.

Do not treat the MCL sprain as a discount signal on Gibbs. Nothing about the injury touches the starter, and any manager reading a Lions backfield injury note as a red flag on the wrong player is making an error you can profit from.

The Verdexed model take

Verdexed's model separates a running back's standalone projection from his contingent projection, and Pacheco is a textbook case of the two diverging. His standalone projection, based on the touches he would receive with Gibbs healthy for a full season, sits well outside the useful fantasy range. His contingent projection, based on the workload he would inherit across a two-to-four game Gibbs absence, sits in the weekly RB2 range.

The correct way to price him is a blend weighted by the probability of that absence, and that probability is never zero for a back who carries the volume Gibbs does. The model's output puts Pacheco meaningfully ahead of the replacement-level backs being drafted around him, which is the definition of an edge.

For Gibbs, the model's projection is unchanged by this week's news. He remains one of a small group of backs with a genuinely uncontested three-down role in a high-scoring offense, and the extension confirms Detroit's intent rather than altering it.

Betting angle

Detroit's season number sits near the top of the NFC North market, and the offense is the reason. Neither the Gibbs extension nor the Pacheco sprain justifies a move on that number in either direction.

The market that does move on this is Pacheco's own rushing props once they post, and those are worth revisiting only if Gibbs's status ever changes. Backup running back props in high-scoring offenses tend to be set conservatively and adjusted late, which creates a window on any week where the starter is questionable.

What's next

The checkpoint is Pacheco returning to full practice, which the Lions' public posture suggests should happen well before the regular season. If he is back in pads and taking his usual reps within the next week or two, this story is over and the only lasting effect is that his draft cost is slightly lower than it would have been.

If the absence stretches into late August without a clear update, the sprain was worse than the initial framing, and Detroit would be entering the season with a backfield one injury away from a genuine problem. That version is not the base case, but it is the version worth checking for before your draft.

Want more analysis?

Check out our predictions and DFS tools powered by the same quantitative engine.