Ian Rapoport shares updated return timelines for Puka Nacua, Davante Adams - Rams Wire
The Los Angeles Rams' top two receivers are both on injured reserve after getting banged up in the last four weeks. Davante Adams landed on IR first after tearing his hamstring in Week 6, and he was given a 6-10-week recovery timeline following surgery.
Three weeks later, Nacua sprained his MCL and PCL, and is also dealing with turf toe. The Rams put him on IR Thursday, which forces him to miss the next four games and return in Week 15 at the earliest.
Ian Rapoport of NFL Network shared a couple of updates on Nacua and Adams during his appearance on the "Pat McAfee Show" Friday. With Nacua, he said the Rams are targeting a "mid-December" return.
"Sounds like MCL is more of a concern than anything for Puka, who's also got PCL and turf toe. The hope is mid-December for him," Rapoport said.
On Adams, Rapoport says the Rams are eyeing Week 12, which is a week earlier than Sean McVay said when he provided an update on Adams. McVay said the Rams are looking for Adams to return after Week 12, so there's a slight discrepancy between the two timelines.
"They thought Week 12 is the target. Week 12 is the pre-Thanksgiving game, right?" Rapoport asked. "Whatever that is, Week 12 was I know is the target for them."
This Sunday will be Adams' fourth missed game, so he will be eligible to come off IR before the Rams' next game against the Packers on Thanksgiving Eve. But it sounds like the Rams believe his return will come after that game. Either way, he shouldn't miss more than one or two more games, which is encouraging.
Nacua will be out longer, but at least the Rams expect him back at some point this season. They just need to stay afloat until he does return.
Comments reflect the views of their authors, not USA TODAY, its publications or its journalists. We do not fact check, verify, or endorse comments and are not responsible for their accuracy or any reliance on them. We may remove comments or suspend commenting privileges at our discretion. Comments are public; do not post personal information. By commenting, you agree to our Terms of Service, Community Rules, and Privacy Policy.
