Crucial Miami Dolphins playmakers in jeopardy of missing TNF matchup with Buffalo Bills

There's plenty of reasons to be intimidated by the Miami Dolphins offense and the speed they posses, but with only one more practice opportunity before Thursday Night Football, a couple of key speedsters were unable to practice today, putting their availability for their matchup with the Buffalo Bills in jeopardy. De'Von Achane, a second year […]

Add as preferred source on Google
De'Von Achane
© Sam Navarro-Imagn Images

There's plenty of reasons to be intimidated by the Miami Dolphins offense and the speed they posses, but with only one more practice opportunity before Thursday Night Football, a couple of key speedsters were unable to practice today, putting their availability for their matchup with the Buffalo Bills in jeopardy.

De'Von Achane, a second year running back that was a huge part of the passing attack for Miami in Week 1, an Raheem Mostert, a veteran running back that had a big season last year, both were listed as "Did Not Participates" for the second day in a row. 

Achane's involvement in their Week 1 game was noteworthy. He took 10 carries for only 24 yards, but caught all seven of his targets for 76 receiving yards. When the Dolphins selected Achane in the 2023 NFL Draft, they added to the track team they're building with a running back that ran a 4.32 40-yard dash at the Scouting Combine.

In his rookie season, Achane led the league in runs of over 40 yards with five, doing so on only 103 carries. Second place in that category was Breece Hall with four such runs out of 223 carries on the season. Like Tyreek Hill and Jaylen Waddle, Achane has game-breaking speed. 

If Achane and Mostert will be unable to go, it will certainly lower the overall amount of speed on the field for the Buffalo defense to have to worry about. Tomorrow's final injury report of the week will be a big clue for their availability on Thursday Night. 

Follow along all season for all the latest Buffalo Bills news. You can also find me on X @JonHelmkamp.