Recent Forum Topics › Forums › The Rams Huddle › Brandin Cooks' return …
- This topic has 2 replies, 2 voices, and was last updated 5 years ago by JackPMiller.
-
AuthorPosts
-
November 21, 2019 at 6:48 pm #108474znModerator
Why Brandin Cooks’ return is huge for Rams with Robert Woods still away
Cameron DaSilva
Why Brandin Cooks' return is huge for Rams with Robert Woods still away
The Los Angeles Rams offense looked very different on Sunday night against the Bears than it did in Week 1. There were two new starters at wide receiver and three new faces on the offensive line, as well as Johnny Mundt replacing Gerald Everett as one of the two starting tight ends.
They had to thrust Josh Reynolds and Mike Thomas into larger roles with Brandin Cooks still recovering from a concussion and Robert Woods tending to a family matter. Being without both players was a big hit to the offense, given the importance of both players’ roles.
It’s unclear when Woods will return to the team and there’s a chance he could miss Monday’s game, but Sean McVay shared some good news on Cooks’ recovery Wednesday. He confirmed the wideout will be back on the field Monday night against the Ravens after missing two games.
“Brandin Cooks is back, he’s excited to be able to play,” McVay said. “He’s felt good for a couple weeks, so when he’s feeling good and we’ve gotten the thumbs up from everybody else, that makes us all feel good. He’s going to play and we’re excited about that.”
This is huge news for the Rams, to say the least.
Cooks has been the least impactful of the Rams’ top three wide receivers this season, but that doesn’t make him unimportant. He simply hasn’t gotten as many opportunities as Woods and Cooper Kupp.
His return to the field changes things dramatically for the Rams offense. With Cooks and Woods both out in Week 11, the Rams went with a completely different approach offensively. They utilized two-tight end sets on 34 plays, which is the highest total of the season. They ran the ball 34 times and Jared Goff only attempted 18 passes, the fewest in his career.
The Rams set out to run the ball straight at the Bears, and it worked to the tune of a 17-7 win. But as we’ve seen all season, McVay prefers to throw the ball over run it. It’s just that putting the ball in the air 40 times with Reynolds and Thomas as two of the top three receivers wasn’t a recipe for success.
We all know how reliant McVay is on 11 personnel, having three receivers on the field more than 90% of the time. The Rams can get back to that on Monday night against the Ravens with Cooks, Kupp and Reynolds, leaving Thomas and his unreliable hands in the No. 4 spot.
Cooks’ speed will also be very valuable. He can stretch a defense like few receivers can, and against the Ravens’ cornerbacks, that’s critical. While Marlon Humphrey has good speed, Marcus Peters and Brandon Carr are somewhat lacking in that area.
If the Rams can get Cooks matched up on Peters or Carr, they can take advantage against single-high safety looks when it’s essentially one-on-one outside. Thomas and Reynolds simply don’t possess that same level of speed as Cooks.
The biggest benefit of Cooks’ return is having three receivers Goff is comfortable with. The Rams clearly shied away from using too many three-receiver sets against the Bears because of his and Woods’ absences, but that should change on Monday night.[
November 21, 2019 at 8:16 pm #108481znModeratorBrandin Cooks is coming back from another concussion, but should he?
Rich Hammond
THOUSAND OAKS, Calif. — Brandin Cooks has started 28 NFL games since the beginning of February 2018. Four of them ended with Cooks being diagnosed with a concussion.
That’s a staggering percentage. Serious questions would be asked if a player suffered ankle injuries that frequently. Or back, or shoulder or knee. That many injuries, in that short of a time period, to one body part is not normal. Cooks’ issue involves his brain, and isn’t that supposed to be cause for more caution?
There’s something a little uncomfortable about Rams practice this week. Cooks, a four-time 1,000-yard receiver, apparently has sufficiently recovered from the concussion he suffered in the Oct. 27 game against Cincinnati and is on track to play in a huge Monday night game against the Baltimore Ravens.
But should Cooks play? Is he risking his long-term health? Shouldn’t everyone who watches the Rams be concerned that Cooks is going to take another big hit and miss more time, or worse?
“It’s one of those things that I’m taking game by game but no, I don’t think you should be concerned, because I’m not,” Cooks said after Thursday’s practice.
Cooks was assertive — even politely defiant — when he spoke for the first time since his latest concussion. No, he isn’t worried. No, he’s not thinking about the possibility of another one. No, he didn’t have anyone — family, friends, teammates — in his ear, urging him to step away.
Cooks recently visited with a specialist in Pittsburgh, and while he understandably declined to go into specifics regarding his health, he said he was encouraged by what he and his wife heard. In so many words, Cooks indicated he had been told that he isn’t at any great risk and that he shouldn’t be worried about the frequency of his concussions.
“To be very honest with you, it was not really concerning at all,” Cooks said. “I understand it’s one of the things that is a part of the game, but at the end of the day, what’s going through my mind is, ‘OK, let’s get some answers and figure out what’s going on.’ It’s a blessing that I don’t ever have symptoms afterward, but it’s one of those things that’s a case-by-case thing. Mine is very unique. I’m grateful to be able to go get answers.”
Credit Cooks for taking an extra step by consulting with a specialist. And to be clear, nobody is doing anything wrong here. Cooks and the Rams have followed established protocol for dealing with concussions. He has been cleared and by all accounts is asymptomatic. Cooks is, as far as everyone knows, no more likely to suffer a concussion this week (or next week or next month) than any other football player in the country. Everyone seems to agree that Cooks can play, and he wants nothing more than to return. So he will.
But even independent from Cooks’ issue, there’s something of a helpless feeling when it comes to NFL players and concussions. With every new report about long-term health implications, fans cringe and some turn away from the sport. A few conscientious players retire early. The league takes steps, seemingly every year, to make games safer.
Yet in the micro, the cycle continues. A player suffers a concussion, goes through protocol, is medically cleared by an independent doctor and expresses his desire to get back on the field. The player returns and, too often, suffers another concussion weeks or months later. This has been Cooks’ life for the past 21 months.
Who is to blame? Anyone? The league has a protocol that it believes keeps players off the field until they are healthy. The Rams aren’t pressuring Cooks to return. They have no real say in the matter. They wait until Cooks is fully evaluated by, and consults with, an independent doctor, and when they’re told he can return, he returns. Imagine the fit that would be thrown by the players’ association if the Rams told Cooks he couldn’t (or shouldn’t) play.
So unless something goes wrong when the Rams return Saturday for their final practice, Cooks will play Monday, 29 days after the fifth documented concussion of his career. That’s a long break for Cooks, given his history.
Dec. 9, 2015: Cooks sustained his first NFL-documented concussion with New Orleans. He was cleared and did not miss a game.
Feb. 4, 2018: Cooks’ second concussion came during the second quarter of the Super Bowl with New England. He did not return to that game and was traded to the Rams two months later, with no apparent concerns.
Oct. 7, 2018: Cooks’ third concussion came in a Week 5 game against Seattle. Soon after, coach Sean McVay declared Cooks to be “symptom-free quickly after the game.” Cooks did not miss a game.
Oct. 3, 2019: Cooks’ fourth concussion came in a Week 5 game against Seattle. The next day, McVay said Cooks was “asymptomatic,” and Cooks did not miss a game.
Oct. 27, 2019: Just two weeks after his return, Cooks suffered his fifth concussion in a Week 8 game against Cincinnati. This time, he did not make a quick return, and after the ensuing bye week, he flew to Pittsburgh to consult with a specialist. Cooks returned to limited practice action shortly thereafter.
By no means is Cooks under any obligation to share what he learned from the specialist in Pittsburgh, but some details might be reassuring. He spoke in general terms on Thursday, about training his brain like a muscle, about “gray area” and “case-by-case basis” and his situation being “an anomaly.”Cooks was definitive about one thing. Asked whether he considered stepping away from the game after last month’s second concussion, he didn’t wait for the question to reach a conclusion.
“Absolutely not,” he said. “No doubt about it. When it happened, that never went through my mind. Even now, it’s not going through my mind. I’m just grateful for a great team around me and for me being comfortable to come out here and play.”
Again, there’s no evidence that Cooks is doing anything wrong, and surely doctors know more than reporters or fans. Might Cooks suffer another concussion this week? It’s possible. Might he go weeks (or months or even years) without another concussion? That’s also possible. Perhaps one day, medical advancements will allow doctors to better analyze or predict such things, but that day has not arrived.
Also, Cooks is an adult. He’s able to make decisions for himself, even some that might be risky. He’s not alone. Other people choose to race cars and skydive. If Cooks is making informed decisions about his life and isn’t being coerced into anything, it’s really not anyone’s place to tell him what to do. These are choices to be made by Cooks and his wife.
“That’s who I go home to,” Cooks said. “Seeing her comfortable during those meetings with me (in Pittsburgh) and being at ease, it’s such a blessing. When you go home, that’s who you’re dealing with the most, as far as questions asked. To see her comfortable and see her not as concerned is definitely helpful.”
On a basic level, it’s just difficult to ignore that Cooks is only 26 and just got married last year. He’s in the prime of his life and in the prime of his career, which should continue at a high level for no fewer than five more seasons. Should he be concerned about his long-term health?
“I don’t think he would go back out on the field if he was worried about that,” McVay said. “Football is a physical game and sometimes those collisions are inevitable. You hate that. You never want to see it. That’s the worst part about this game, is seeing any player get injured. You hate that, because of the work these guys put in, but I do think it’s really important that you go out there with a clear mind and just be able to compete to the best of your ability and not have to worry about those types of things.
“I don’t think he would go back out there if he felt like that was on his mind, and I think he’s really champing at the bit, excited to go.”
One problem is that Cooks isn’t a quarterback who can slide at the end of a scramble or throw the ball away to avoid a crushing sack. He’s not a running back who can skip out of bounds after a 12-yard gain. He’s not a defensive player who, for the most part, can determine the point of contact on a big hit.
As a receiver, Cooks is a target in every sense of the word. He has little say in when the ball is coming to him, or where, or the force with which he’s going to be taken to the ground.
All everyone can do is hope for the best. Cooks is confident and ready to play, he is under contract through the 2023 season and the Rams clearly see him as a huge part of their future. Right now, the best-case scenario isn’t a Rams victory over the Ravens.
It’s Cooks on the field, healthy, at the end of the game — win or lose.
November 22, 2019 at 11:27 pm #108507JackPMillerParticipantBrandin Cooks didn’t consider retiring after concussion
By Kevin Patra
Around the NFL Writer
Published: Nov. 22, 2019 at 09:38 a.mAfter Brandin Cooks’ latest concussion, the question hovered in the L.A. smog: Would the latest head injury bring an abrupt end to the receiver’s career?
For his part, the 26-year-old said he never considered retirement.
“Absolutely not,” Cooks said, via Lindsey Thiry of ESPN. “When it happened, that never went through my mind. Even now, it’s not going through my mind.”
Cooks suffered his second concussion in a 25-day span during the Rams’ Week 8 game in London. The wideout missed the previous two tilts but is expected to play Monday night versus the Baltimore Ravens.
Cooks has now suffered five known concussions in his six-year career. After his latest head injury, the wideout twice traveled to Pittsburgh to meet with Dr. Michael Collins, the director of the UPMC Sports Medicine Concussion Program. After those meetings, Cooks said he grew comfortable returning to the field.
“One of the biggest things that I learned, concussions is a case-by-case thing,” Cooks said. “Mine was very unique, and just thankful once again to be able to go and get answers.”
The young receiver — who signed a five-year, $81-million extension before last season — said he’ll enter Monday night’s game not fearing another heard injury.
“It’s one of those things that I’m taking game by game. But, no, I don’t think you should be concerned, because I’m not,” he said.
The restricted Rams’ pass offense certainly could use Cooks’ dynamic playmaking ability Monday against a streaking Ravens squad. If L.A. is to press back into the playoff picture, a win this week is paramount.
-
AuthorPosts
- You must be logged in to reply to this topic.