Forum Replies Created

Viewing 30 posts - 46,441 through 46,470 (of 47,913 total)
  • Author
    Posts
  • in reply to: What can we expect now? #10608
    Avatar photozn
    Moderator

    They have lost or currently have injured:

    1 WR
    2 QBs
    3 OL
    3 left DEs
    2 free safeties
    3 CBs, including one on IR

    So Shawn Hill is still hurt? or has Austin Davis formally taken the #2 spot?

    Yeah I put that wrong. Davis the novice is starting because Hill was originally injured then Davis replaced him.

    So injury is tied to that but it’s also more than that.

    in reply to: Where do you stand on Austin Davis? #10606
    Avatar photozn
    Moderator

    Sometimes I’m not sure what the game plan is for him. He can throw the occasional deep ball but he needs to know when that isn’t there and have the proper check downs–and if he has that but isn’t doing it then he needs better coaching.

    That;s just him. He has the coaching. Every time he himself says “the coaches stressed this” he comes through for a game.

    Some players just fall back on old instincts when the pressure is on.

    No coach in the universe can change that.

    He is SUPPOSED TO BE checking down. The fact that he isn’t is on him.

    You know…the Rams main issues this year are all execution. Getting down on the weary patient coaches is just a misread of the situation. And the problem with most “coordinator” discussions is that they end up really just confusing execution issues with coaching issues.

    This is execution. A young player, who has not learned yet, and might never learn.

    in reply to: OL injuries #10603
    Avatar photozn
    Moderator

    I wasn’t too excited about relying on Long at LT this year, but I figured at least they have depth. But, man, if Saffold doesn’t keep getting injured. That may be the real death knell. If Saffold continues to suffer, with Wells out, with Long long gone … man, you’ve got to be kidding me. Austin Davis is not going to have a chance. I was just talking about how at least this team was watchable. I said that after the first TD on Sunday. I fear I’ll have to eat those words.

    Of all the Rams OL Injury Epidemics I have seen…and I’ve lost count…this one has the *potential* to be one of the more benign, or should I say, least deadly.

    Before, there was no Robinson and Jones. It was street free agent city.

    If Robinson and Jones can play, then…they are not as completely bad off as they were in prior versions of OL Apocalypse.

    in reply to: Shellshock #10597
    Avatar photozn
    Moderator

    zn wrote:
    I don’t see this team as “bad.” I see it as astonishingly unlucky. For example, not every team has had a 2011 to cope with–and Football Outsiders said the 2011 offense was the single-most injured offense since 2002 (which is as far as they went back).

    So not many teams have a 2011.

    This one has had two, within 4 years.

    That’s just freaking weird heavy bad, bad luck.

    The effect is the same as “being bad.” But still.

    It’s… the curse.

    Okay, sure. That’s true. But they kinda sucked before the OL got all Dresdened yesterday.

    They had an OL that was not together because it didn’t play together in camp because they were recovering. They were starting their 3rd qb. So injuries were already taking their toll, sometimes in indirect ways (like a buncha recovering linemen not playing together as a unit).

    It is true that the defense kept making monumental mistakes of a kind only young players in a new system make.

    But this team was not “bad” at the level of talent or coaching. That’s not what I saw, anyway. I saw the effects of cohesion issues and injuries on offense, and I saw the “McDaniel effect” of young players in a new system on defense.

    They also dominated for stretches on both O and D.

    Teams that meet that overall description improve.

    Unless you injure them up beyond recognition.

    Same as 2011. They didn’t adapt quickly to the McD system, and by the time they were starting to, the St. Louis Reaper came and left injury devastation behind him.

    s

    in reply to: Shellshock #10591
    Avatar photozn
    Moderator

    I don’t see this team as “bad.” I see it as astonishingly unlucky. For example, not every team has had a 2011 to cope with–and Football Outsiders said the 2011 offense was the single-most injured offense since 2002 (which is as far as they went back).

    So not many teams have a 2011.

    This one has had two, within 4 years.

    That’s just freaking weird heavy bad, bad luck.

    The effect is the same as “being bad.” But still.

    It’s… the curse.

    s

    Avatar photozn
    Moderator

    2011.

    Tellin ya, it’s 2011.

    All over again.

    in reply to: OL injuries #10584
    Avatar photozn
    Moderator

    from off the net



    Deadpool

    long out for season

    Mcl and acl.

    Per mri

    in reply to: Where do you stand on Austin Davis? #10583
    Avatar photozn
    Moderator

    from off the net…

    ===

    thehammer

    said I would wait till after next weeks sf game but I’m ready now…

    said in all my previous comments about Davis that he lacks a starter caliber nfl arm…been watching qb’s at camp for decades/not exactly my 1st rodeo and the 1st thing that jumped out at me at camp(and everyone else over the last 2 years) was his lack of arm strength..really struggles in 7v7 man to man passing drills because, as Moe said, lacks the arm strength to complete passes in tight windows

    quick look at pff stats no qb in the nfl are attempting fewer passes in the 10-19 range then Davis except Wilson. Davis 40 to Russell Wilson 39 with Wilson having 25 fewer attempt also Wilson has thrown 25 passes outside the hashmarks to Davis 20..Davis struggles to throw anything outside the hashmarks over 20 yds unless it’s a lofted underthrown bomb to Quick/Britt hoping they outjump shorter cb’s.. Teams know this and gameplan accordingly.

    thought McNabb comments yesterday were spot on…KC playing man to man vs Davis and said Davis had to complete passes to his outside wr’s or run when he has the opportunity..Davis struggles to do either

    .Alex Smith also has a weak arm and ran…Wilson runs..Davis has to occasionally run to beat man to man coverage.

    Quick caught 14 passes in the 1st 2 games and 5 vs philly when they had a huge lead and played a soft zone but has vanished since..Britt is our deep wr and has only caught 16 passes and only 10 in the last 4 games…there is a reason for the dropoff..lack of arm strength and more man to man coverage

    pff gives week to week grades on players…it allows you to watch trends..talented rookies often start slowly with bad pff numbers but around games 6/8 their numbers start trending upwards..the posers get worse…Davis numbers are trending down

    teams will continue playing to man to man vs Davis till he shows them he can beat man to man coverage or starts running…neither Kaepernick or Wilson are great passers but run.

    love Davis decision making when not pressured…reminds me of Montana…BUT for him to be successful he has to work on getting a stronger arm or start running forcing teams to play zone against him..He is a very good zone qb…quick decisions/quick dumpoffs…

    also weak arm qb’s need very good receiving rb’s …Montana had Craig(and could also run) Brees had Sproles and we have Stacy….not exactly the same

    posted a study about a qb’s dna..what stats stays with him his whole career even if traded…sack rate…experience doesn’t seem to help and davis rate is bad..I expect more man to man and lots of pressure going forward if Davis keeps starting

    right now Davis is 28th out of 35 qb’s with a -6.6 rating

    can Davis develop into a Alex Smith type starter? Yes but that looks like his ceiling but he has to run a little and the rams have to surround him with better receiving rb’s/te’s and hope he learns to handle pressure better..will say Hill offers us a MUCH better chance of winning and Keenum also deserves a chance to start..

    ..

    Bradfords best statistical season was 2012(also highest pff grade).which was.also his best rushing season…it wasn’t a coincidence

    we had a weak wr corp and teams were beating us with man to man and our coaches pushed Bradford to run which forced teams to start playing zone opening up the passing game.

    in man to man a wr can run a 9 rt with the other receivers flowing to other side of the field..the cb covering the 9 in man to man never looks back and a running qb can make good yardage on runs..can’t do that in a zone..

    Davis looked good vs Lovie Smiths cover 2…teams are becoming more zone heavy as the nfl gets more running qb’s which should help Davis…some teams simply lack the personnel to play man to man which also will help

    in reply to: What can we expect now? #10581
    Avatar photozn
    Moderator

    At this point with those injuries, I think we’d be lucky to win 2 games. The over and under is probably set at 1.

    More high pics next year.

    If we can go relatively injury free at some point in the next couple of years and get even average QB play, we are going to be really good at some point.

    I think they will win 2-3 games, and maybe 1 more. So, 2-4?

    Long story why I think that but the short version will do.

    Avatar photozn
    Moderator

    HEAD COACH JEFF FISHER

    OPENING STATEMENT: “We clearly got out played the second half of this game, in all three phases. It probably started before half when we had the turnover, got sacked, got no points, and then gave up points so this team is going to have to learn to play consistent through 60 minutes. We started fast but we didn’t finish. Getting out played means we gave up the run, but we also gave up the high completion percentage against the defense, which we knew they had, and we gave up too many third downs, we were third in the league, so we’ve got our work cut out for us. We’re on our way to the west coast, and I’ll @#$%& our injury situations over the next 24 hours, we’re going to have some players that miss some time, but how much and whom, I don’t know but I’ll let you know in time.”

    Jeff that kickoff return to start the third quarter, how deflating was it for the team and had you planned to kick the line drive? “It was a bad kick, Greg (Zuerlein) missed practice with the flu. I don’t know if that had anything to do with it, but he missed a field goal and it was a bad kick. We were trying to get a deep left kick and he just shanked it, and they got off to the run. I haven’t seen it on film, but usually when that happens you’re going to get potentially a hold or two, and it’s uncharacteristic of our cover team to not make that play. But that was it, that was a key play, and that’s what they needed in this game. And we didn’t get that.”

    The sequence that you mentioned on the third down play, would you have wanted Austin (Davis) to have just thrown the ball? “Yep. Throw the ball, just throw it away. He saw the top rushers, and wanted to make the play, but he should have just thrown it out of the back of the end zone, get past the line of scrimmage. But still, that’s a makeable kick, that well into field goal range.”

    Is a performance like this a little more demoralizing only because you beat a good team last week? “Well it’s disappointing, we had a great week, we had a short-lived bit of momentum, but we haven’t been able to put the two in a row together. I’ll credit the guys, we had some young people playing on defense, and the finish was tough when we had players go down just trying to put it together.”

    How much did that handicap you especially at cornerback, especially with so many young guys back there? “We anticipated quick throws and a run game, and we got a lot more attempts in the first half than we expected, but if its working for them they are going to do it, and you know they did it. They knew that they couldn’t get Alex hit and they did a nice job of managing the game and taking it there. We missed some tackles in the open field that could have changed possessions, and we just had a handful of things happen.”

    You had some roughness and some personal fouls, the Alec Ogletree one could be particularly damaging early on in the third quarter. “I have to look at the one on the sideline, I wouldn’t know. I don’t think they should have called the personal foul on E.J. (Gaines) with the quarterback, but you can’t take them feet first or head first, but you have to take a chance to get him down. But I didn’t see what happened with Ogletree, but he’s got to work on that, learn how to be a pro and keep fighting when things aren’t going good and just keep on doing his job. But we will get him straight.”

    Out of 7.0 sacks did they give you any looks that you weren’t anticipating? “No, I think those were individual plays, they’d go out and rush us. And I told our guys this week they have inside push and outside speed and a good combination to get to the quarterback and they are built to do that. It’s not like you have to go out there and do a run defense when you’re down 24-7 you have to go and keep passing.”

    Where do you think E.J. added any crutch to you? “I don’t know, I can’t comment until I see the tape. I mean they all played hard, we just didn’t get any plays. He had the ball in his hand, he tried to get up and run, so if he didn’t run the ball, maybe things would have been different there.”

    How about the offense? After that great start, then you had trouble getting going. “We had a three and out, and we had the deep ball for the turnover and then they started running time of possession, and then we got the turnover. But we didn’t have momentum. When you haven’t gotten the carries and the reps then all of a sudden you get the ball on the nine-yard line, we just didn’t have the momentum at the time, but that’s no excuse we should still come away with some points. But we didn’t, so I’ll let you know on the injuries as soon as we know about them.”

    QB AUSTIN DAVIS

    Describe the heat and the pressure you took in this game: “It was definitely a factor in the ballgame. They did a really good job. We knew coming in they were going to get after the quarterback, so we tried to create a plan to get the ball out quick. I thought our offensive line fought extremely hard. Some guys went down and we were playing with backups. I thought those guys stepped in and did a good job. I’m proud of them and appreciate the way they fought.”

    What do you think happened after the first drive? “It’s hard to say. They took some things away. When that happens, you have to find a way to get some momentum offensively, and we weren’t able to do that. My hat really goes off to them. They did a really good job and made a lot of really good plays, but it’s hard to say without watching film.”

    Can you take us through the 2nd quarter drive when the defense got a takeaway and you started on the 8-yard-line, only to end the drive with a missed field goal? “That was a big point in the game. You get the big turnover. At a minimum you come away with three, but really you need to score a touchdown. I remember the third down play specifically; they did a good job of taking Lance (Kendricks) away down the middle and I had to move a little bit. I probably could have stayed in there a bit more and gotten Chris (Givens) on the back line. Then obviously on the last play, you have to throw it away. You’re even closer and it would have been more of a chip shot for Greg (Zuerlein), so I have to do a better job of throwing the football away and managing that situation. You get the field goal and everyone feels a little bit better. Those types of plays are critical in a close game as it was at that point.”

    You had just scored a touchdown that way. Is that why you didn’t throw the ball away? “Yes. I was trying to make plays. I thought I could move around; you see a lot of big plays happen that way. It felt like we were tight enough that even if I did have a sack we would still have a manageable field goal. But, at the same time you can’t do that. That’s just me trying to do too much.”

    It seems like the tight ends like Jared Cook were pretty quiet today. Did they take that away, somehow, schematically? “I think in every game you look at plays, and yes, they took some things away. But it probably wasn’t as gloved as it felt like. You get back there and start getting a little pressure and start moving a little bit. I will have to take a look at it and see what really happened. We have to move on and keep getting better.”

    How disheartening is it that this game just kind of deteriorated? “It’s tough, but losing is losing and winning is winning and that’s really all that matters. You find a way to win. We have to let this one go just like we would a tight ball game. It hurts right now. We are a better team than we showed and we know that and we have to play that way.”

    You were missing three offensive linemen and your most productive receiver, Brian Quick. How did that complicate things for you offensively? “I feel terrible for those guys. But you have new guys coming in that, like I said earlier, did a pretty good job. It’s hard to come in off the bench like that. It’s hard to come in cold. You start building with new guys, but that’s just part of football. That’s part of what we do, we expect that every week – for guys to come in and play and they’re professionals too. That’s what happens.”

    Was the 99-yard kickoff return to start the 2nd half deflating for the team? “Of course. That’s a tough thing to get over, but it’s not anything that you can’t overcome. We’ve got to find a way offensively to answer that. That’s what we have to do. It’s no different than them going on a long drive and scoring. We still have to go out and answer and flip that momentum. That’s what we’re failing to do right now – take back the momentum once we lose it. We’ve got to figure out a way to do that.”

    On the interception, what did you see or not see? “We were trying to take a shot. It felt like if we could get the corner to turn and run, with his back to me, that we could take a shot with WR Kenny Britt – a ton of speed. It felt like the safety was a little too far over the top. It’s a ball I would like to have back. It’s kind of like a long punt, but at the same time it’s a turnover and you don’t feel good about it. Offensively, we were kind of moving the football so that’s a ball I’d like to have back.”

    CB E.J. GAINES

    Did you always dream of playing at Arrowhead since you grew up so close? “I played in here a couple of times in college. Actually, I played one time in Pop Warner when I was about 10 years old. I’ve been here a couple of times. Playing at this level, in your home town, doesn’t get much better than that.”

    Is it different playing here as a professional? “Oh yeah – everything about it is different. When you get to this level, it’s kind of surreal when you get out there playing against the Chiefs instead of playing against KU or something like that. Anytime that happens, it’s fun to get out here.”

    This couldn’t have been how you envisioned it [playing in Arrowhead against the Chiefs]? “No, not at all. This is something we’ve got to go watch on film and fix our mistakes. We have to play better against San Francisco next week.”

    When you got drafted in the sixth round, did you think you were going to start your first seven career games? “No I didn’t. But, I try to play at my highest level and whatever happens, happens – even if it was playing special teams or doing whatever I could to help out the football team. It didn’t matter. It just happened that I got the opportunity to start.”

    Today, you matched your career high in tackles. Do you feel like your off to a good start? “I think I’m off to an okay start. I had a lot of mistakes out there being a rookie. But, my teammates pick me up. They understand that I’m young. With that being said, they still expect me to play like a vet and limit those mistakes.”

    What is the difference between playing at Missouri and now in the NFL? “The speed of the game is so much different in the NFL. Everybody is that great football player that you might have in college. Coming in and knowing that, I would like to think of myself also as one of those great players. It’s just the competition level.”

    You had a little bit of a rough drive late in the first quarter, beginning of the second quarter. You had the chance to recover the fumble, there were a couple of missed tackles, the illegal contact. Was that you that Travis Kelce put that move on? “Yeah. I had a couple of missed tackles. Those are the things I am saying I need to fix. Those are the plays I’ve got to make on defense.”

    TE LANCE KENDRICKS

    It looked like it was hard for you guys to get things going offensively. What happened out there? “We struggled up front early. They had a well-executed defense. We struggled all across the board. It was loud out there. We couldn’t get the signals out. We couldn’t get the personnel out. So, the game really wasn’t flowing for us as it may have for them. But, that’s on us. We’re professionals. We play ball too. We have to be ready for that type of stuff. I just don’t think we were ready for everything they threw at us.”

    On the touchdown. “It was just a play we repped all week. They were overplaying the corner route I ran. I had an option to step back. They played the corner very well. I just stepped back and caught it in the open void for a touchdown.”

    It’s got to be disheartening [this loss] because you’ve been in every game since the Minnesota game. “Exactly. We’ve either started fast or we finished fast in every game. Last week, we finally put one together. Coming in, we were thinking the same thing but we weren’t able to execute like we should have.”

    Does that add to the frustration because last week you won? “Definitely. We felt like we matched up well against these guys. We have a great team, but it’s just the schematics – we didn’t put it together like we should have. We missed the opportunities that were there for us to score touchdowns.”

    What’s it like when you see all of those guys go down with injuries? “It’s kind of scary. But, we’ve got to put the next man out there and just continue to play the game. The game is not going to stop for anybody. We’ve just got to keep playing and stay focused on task ahead.”

    K GREG ZUERLEIN

    What happened in the opening kickoff of the second half? Was it just a mishit? “I tried to kick it too hard and I hit it a little too high. That’s what happens. You can’t do that.”

    How sick were you? Obviously, sick enough that they wanted to keep you away from practice. “It really doesn’t matter. No matter what the circumstances are, you still have to come out here, perform and do your job. There are no excuses for mishits or missing field goals or anything like that. How sick I was is really irrelevant.”

    You’ve got 10 other guys out there to tackle him [Knile Davis]. You shouldn’t put it all on yourself. “Well, if I do my job, those other 10 guys don’t have to do theirs. That’s the way I look at it. I didn’t do my job, and I put them in a bad position by not getting any hang time or location that we normally have. So, that’s something I need to work on and go forward from there.”

    in reply to: What can we expect now? #10570
    Avatar photozn
    Moderator

    So what can we expect now,
    from a team that was struggling on defense,
    and that has now lost three starters
    on the OLine ? And maybe Quick as well.
    Not to mention Hayes on defense.

    Nine more games.

    O dear.

    Two more wins?

    w
    v

    This is 2011 redux.

    BTW it Hayes is hurt, so is Westbrooks. That means they have 3 injured left DEs.

    They have lost or currently have injured:

    1 WR
    2 QBs
    3 OL
    3 left DEs
    2 free safeties
    3 CBs, including one on IR

    Because of shifts and replacements, that has an effect on:

    CB1, CB2, FS, left DE, LOT, LOG, OC, ROG, WR, & QB.

    10 positions.

    I don’t know how many of the injured come back when so who knows about how long this will last.

    3-4 positions with replacements? That’s just the NFL. Beyond that? It’s not the same team.

    Avatar photozn
    Moderator

    Rams notes: J. Long could be done for year

    By Jim Thomas

    http://www.stltoday.com/sports/football/professional/rams-notes-j-long-could-be-done-for-year/article_deb2cd12-df60-5b45-88fd-d534285adb92.html

    KANSAS CITY • Remember the Cleveland preseason game, when the Rams lost five starters in the first half?

    Well, Sunday’s 34-7 shellacking to Kansas City was that nightmare revisited.

    Early in the second quarter — just two plays apart — the Rams lost wide receiver Brian Quick (arm) and right guard Rodger Saffold (shoulder) to injuries. Quick’s left arm was in a sling after the game; he said he didn’t know the extent of the injury.

    Late in the third quarter, left tackle Jake Long left with a knee injury. Two sources confirmed to the Post-Dispatch after the game that it looks like Long is done for the year with a torn ACL (anterior cruciate ligament). That’s the same injury that sidelined Long in the Tampa Bay game late last season.

    Before the second half was over, center Scott Wells (elbow), free safety Rodney McLeod (knee) and backup free safety Cody Davis (concussion symptoms) had been sidelined with injuries. McLeod apparently has an MCL (medial collateral ligament) injury, which is not nearly as serious as an ACL injury.

    And although there was no in-game announcement regarding William Hayes, the veteran defensive end left the locker room on crutches with a foot injury.

    It all added up to six starters, and a backup, going down with injuries Sunday afternoon.

    “I’ll assess our injury situation over the next 24 hours,” coach Jeff Fisher said at his postgame news conference. “We’re gonna have some players that are gonna miss some time. I don’t know how much and whom, but they’re gonna miss some time.”

    The Rams finished the game with only two of their original five offensive line starters on the field — Greg Robinson and Joe Barksdale. And Barksdale, the team’s right tackle, was the only one playing his original position.

    After Long’s injury, Robinson moved from left guard to left tackle. Mike Person, who had played only four snaps previously all season on the offensive line, came off the bench to play left guard. Barrett Jones, who played in his first game of the season last week against Seattle following back surgery, replaced Wells at center. It was Jones’ first action in the NFL on offense after being drafted in the fourth round out of Alabama in 2013.

    Davin Joseph, who started the first four games of this season at right guard, replaced Saffold there.

    “It’s always a setback, especially when you start losing key players,” Hayes said. “Hopefully we can get ‘em healthy this week and they’ll be ready to go for San Fran. But it just (stinks). Guys work hard and then you see ‘em go down. It’s always tough.”

    SITTING IT OUT

    Rams inactives Sunday were CB Janoris Jenkins (knee), CB Trumaine Johnson (knee), C Tim Barnes (shoulder), DE Ethan Westbrooks (hand), TE Alex Bayer, S Maurice Alexander and QB Case Keenum.

    On Saturday, the Rams placed second-year CB Brandon McGee on the season-ending injured reserve list because of a foot injury that he aggravated in practice last week. He was replaced on the active roster by CB Jemea Thomas, who was promoted from the practice squad.

    Thomas’ Rams debut included an unnecessary roughness penalty after the last Kansas City kickoff of the day.

    RAM-BLINGS

    • The Rams had only 200 yards of offense Sunday, easily their lowest total of the year. Between their game-opening touchdown on their first possession to some garbage-time yards on their final two possessions late in the fourth quarter, they managed only 65 yards of offense over a span equivalent to three quarters.

    • After giving up zero sacks last week against Seattle, the Rams allowed seven sacks Sunday against the Chiefs.

    • LB Marshall McFadden, promoted to the active roster from the practice squad following the release of WR Austin Pettis, made two special teams tackles in his Rams debut, according to unofficial press box stats.

    Avatar photozn
    Moderator

    Bernie: Sing it again … same old Rams

    Bernie Miklasz

    http://www.stltoday.com/sports/columns/bernie-miklasz/bernie-sing-it-again-same-old-rams/article_eae7b482-1b7f-5a5f-9676-761dd2835e93.html

    KANSAS CITY • Chiefs 34, Rams 7 … and the beat goes on.

    And by now, I don’t know what to say. I could throw a tantrum and demand firings to appease the understandably angry mob of Rams fans. But telling the owner to sack the GM and head coach and a coordinator or two is nothing more than a cheap grandstand play. And it has no chance of happening. None.

    After using a satchel of magic tricks to upset the Seattle Seahawks last Sunday, the Rams had a chance to come to Arrowhead Stadium and get a little something going. Just a two-game winning streak to signify that things were on the upswing. You know, a little serving of hope for the people.

    The day began promisingly enough for the visitors, with an opening drive of six plays, 65 yards and a touchdown for a 7-0 lead.

    That’s it.

    There’s your highlight.

    The Chiefs outscored the Rams 34-0 the rest of the way.

    That little slice of hope was shredded by the Chiefs.

    “It’s disappointing,” Rams coach Jeff Fisher said. “We had a great week, a short-lived bit of momentum, and weren’t able to put two in a row together.”

    And now the Rams and their overpopulated list of wounded players go on the road for games at San Francisco and Arizona.

    Good luck with that.

    The bullet points on a 27-point loss:

    • More Rams players limped off the field with broken bodies — six guys were injured in this one including three starting offensive lineman.

    • The Rams allowed a 99-yard kickoff return to start the second half, and the Chiefs were suddenly up 17-7 and well on their way to a systematic rout.

    • Kicker Greg Zuerlein shanked that kickoff to set up the runback. In the second quarter he missed a 38-yard field goal that would have given the Rams a 10-7 edge.

    • QB Austin Davis threw a terrible interception to kill the early momentum. And on at least a couple of occasions Davis failed to throw the ball away to avoid being sacked. The Chiefs sacked him seven times. Davis is a young quarterback who hasn’t always played like a young QB. He played young Sunday.

    • After grabbing that early 7-0 lead, here’s what the Rams did on their next eight possessions: 33 plays, 51 yards, five first downs, six punts, the interception, and the missed field goal.

    • The Rams’ young, injury-torn secondary was shredded by KC quarterback Alex Smith for 24 completions in 28 attempts and a 100.3 passer rating. Defensive coordinator Gregg Williams’ pass defense remains vulnerable.

    • The Rams defense stopped Chiefs RB Jamaal Charles for as long as they could; he had only 14 yards on eight first-half carries. But with the Rams offense unable to stay on the field, the overexposed Rams defense eventually gave way. In the second half Charles galloped for 96 combined rushing-receiving yards and had two touchdowns including a 36-yard breakaway.

    • The Rams actually did a solid job of running the ball — but sort of moved away from the run while this game was within plausible (if not realistic) reach.

    • I’m not sure why offensive coordinator Brian Schottenheimer thinks it’s so clever to use the mini-receiver Tavon Austin on runs between the tackles. Defensive players must chortle when they see Austin lined up in the backfield.

    • And of course there were eight Rams penalties for 68 yards.

    • Faulty preparation was apparently an issue. A quote from tight end Lance Kendricks on the Rams’ sputtering offense: “We struggled all across the board. It was loud out there. We couldn’t get the signals out. We couldn’t get the personnel out. So the game wasn’t really flowing for us as it may have for them. But that’s on us. We’re professionals. We play ball, too. We have to be ready for that type of stuff. I just don’t think we were ready for everything they threw at us.”

    I’m sorry to disappoint you, but I just can’t lather myself up with rage after this one. My supply of rage is running low. After a while, these smackdowns of the Rams just leave me shrugging. I don’t know if I’m just numb to it by now. Or if I’ve just accepted the reality. The Rams lose. And lose. And lose. So why would we expect a different outcome except for the odd Sunday here and there?

    Fisher and the staff and the players are working hard. (I know; no one cares about that. That’s what they’re supposed to do. True.) The Rams aren’t good enough to win consistently when healthy. They sure as heck have no chance to win when they aren’t healthy.

    The Rams are 2-5 on the season.

    They’re 45-105-1 since the start of the 2005 campaign.

    Pardon the mixing of sports, but that’s 151 games … nearly enough to add up to a full major-league baseball season.

    So basically, the Rams are the 1962 New York Mets (40-120), or maybe the 2003 Detroit Tigers (43-119.)

    Sometimes, a team is so bad it becomes comical. I’m not suggesting laughter here … but please don’t have a heart attack over this team. It isn’t worth it.

    I suppose there’s always hope.

    I know this because I’m looking across the parking lot at Kauffman Stadium, and World Series Game 6 will be played there Tuesday night, the San Francisco Giants at the Kansas Royals.

    As you know, the Royals failed to make the MLB playoffs for 29 consecutive seasons, 1986 through 2013. And now the Royals have a chance to win a World Series a few hundred yards from the patch of ground where the Rams curled up to absorb another hideous loss.

    Yeah, so there’s always hope of a Rams turnaround.

    In theory, anyway.

    Just don’t ask me to predict if it’ll happen during your lifetime.

    Avatar photozn
    Moderator


    Rams’ missed chances become Chiefs’ blowout

    By Nick Wagoner

    http://espn.go.com/blog/st-louis-rams/post/_/id/13019/rams-missed-chances-become-chiefs-blowout

    KANSAS CITY, Mo. — The St. Louis Rams have made a habit of starting as the hare and ending as the tortoise in 2014, but for all of those slow finishes, many of them can be directly linked to a series of missed opportunities.

    After the Rams’ 34-7 blowout loss to the Kansas City Chiefs on Sunday afternoon, the 2-5 Rams appear headed down the path to another disastrous season.

    And there will be no sequence of plays that better sums up this year’s team so far than what happened midway through the second quarter of Sunday’s loss.

    In a 7-7 game with the ball at Kansas City’s 8-yard line after a fumble recovery by defensive end William Hayes, the Rams somehow managed to come away with no points. Not a touchdown, not a field goal, nothing. Instead of at least a 3-point Rams’ lead, Kansas City got the ball back and promptly drove for a field goal of its own.

    It was a six-point swing that turned more painful as the Chiefs rattled off the next 27 points of the game. They scored all 34 of their points after the Rams’ opening touchdown.

    “We clearly got outplayed the second half of this game in all three phases,” Rams coach Jeff Fisher said. “It probably started before half when we had the turnover, got sacked, got no points and then gave up points. So this team is going to have to learn to play consistent through 60 minutes.”

    Really, the most consistent thing about this Rams team is the repeated use of that final sentence. Talk of finishing a game, playing a full 60 minutes and other such cliches are staples around the St. Louis locker room and yet nothing seems to change — with rare exceptions like last week’s win against Seattle mixed in.

    Sunday’s failure came at all levels, but the steamroller didn’t really fire up until after the missed second quarter chance.

    The Rams offense had put together an impressive opening drive for a touchdown, and though it hadn’t scored since, had at least moved the ball. On first down from the Chiefs’ 8, running back Tre Mason ran up the middle for 1 yard. On second down, the Chiefs blanketed a Rams receiver corps as pressure came through the Rams’ struggling offensive line and forced quarterback Austin Davis to scramble for a yard.

    Third down is when things really took a turn for the worse as Davis felt pressure, escaped the pocket to the right and instead of throwing the ball away or hanging in the pocket to find receiver Chris Givens in the back of the end zone, took a 14-yard sack.

    “That was a big point in the game,” Davis said. “Obviously you get the big turnover. At minimum, you’ve got to come away with three but really you need to score a touchdown. I’ve got to throw it away. We’re even closer and it would have been more of a chip shot for Greg so I have got to do a better job of throwing the football away and managing the situation. You get the field goal and everyone feels a little bit better. Those types of plays are critical in a close game as it was at that point.”

    In fairness, Davis had thrown a touchdown earlier in the game on a similar play when he rolled out and found tight end Lance Kendricks in the back of the end zone. Taking a sack isn’t a good play but it still left kicker Greg Zuerlein a 38-yard chip shot. Or so it seemed.

    Zuerlein, who has developed a knack for missing kicks at crucial times, said he rushed the kick and didn’t set his plant foot properly.

    “Anytime you go out there they expect you to make the field goal, obviously you should, being that close,” Zuerlein said.

    Once again, there are a lot of simple enough things the Rams should be able to do to help them win games. They’re the things that winning teams do and losing teams don’t. And for as long as the Rams don’t do them, they’ll continue to get the same result.

    Avatar photozn
    Moderator

    Rams crushed in Kansas City 34-7

    By Jim Thomas

    http://www.stltoday.com/sports/foot…cle_c3d8917b-dbf9-50f6-8297-121f30f833df.html

    KANSAS CITY • After a promising start, the Kansas City nightmare continued for the Rams. A 34-7 loss to the Chiefs made the Rams 0-3 against their NFL cousins on the western edge of the state since the move to St. Louis in 1995.

    The composite score in those three contests: Kansas City 137, Rams 51.

    Since that buzz-kill of a season-opening 34-6 loss to Minnesota, the Rams had played everyone tough over the next five games. But not this Sunday.

    While the Chiefs were piling up points in the second half, the Rams were piling up penalties, missed tackles, and injuries. It was an embarrassing afternoon to say the least.

    Injuries to center Scott Wells (elbow), left tackle Jake Long (knee), right guard Rodger Saffold (shoulder), wide receiver Brian Quick (arm), cornerback Rodney McLeod (knee), and safety Cody Davis (concussion symptoms) added injury to insult.

    There couldn’t have been a better start for the Rams in the Sea of Red. For starters there was a 41-yard kickoff return by Benny Cunningham, who entered the day as the NFL’s leader in kickoff return average.

    On third-and-1 from the St. Louis 44, Austin Davis found Kenny Britt open deep down the left sideline for a 43-yard gain to the Kansas City 1. Three plays later, a patient Davis found tight end Lance Kendricks open in the middle of the end zone for a 1-yard touchdown.

    It marked the third game in a row that Kendricks has hauled in a TD catch, with two of the grabs coming in the red zone.

    End of highlight reel. Things went downhill from there on out for the Rams, who dropped to 2-5 on the season and face road games at NFC West rivals San Francisco and Arizona in the next two Sundays.

    On the Rams’ second possession, Davis forced a deep ball into double coverage that was intended for Britt. Fourth-year defensive back Ron Parker hauled in the overthrown pass for a Kansas City interception.

    Starting late in the first quarter, the Chiefs (4-3) took advantage of good field position to even the score on a 53-yard touchdown drive. It was a tough drive for Rams rookie cornerback E.J. Gaines, the Missouri product playing in his hometown.

    First off, he tried to pick up an Alex Smith fumble forced by Robert Quinn instead of falling on the ball. It rolled out of bounds and the Chiefs retained possession. On third-and-7, an illegal contact penalty on Gaines gave KC a first down.

    Then, on third-and-6 from the St. Louis 18, Gaines missed a tackle near the line of scrimmage on a quick sideline toss to tight end Travis Kelce. Kelce wasn’t brought down until he reached the 1-yard line. On the next play, Jamaal Charles was in the end zone running off left guard to tie the score 7-7 early in the second quarter.

    Later in the quarter, the Rams missed a golden opportunity to take the lead when a botched handoff to Charles from Smith resulted in a fumble deep in Kansas City territory. Defensive end William Hayes recovered the loose ball and returned it six yards to the Kansas City 8. But two running plays produced no gain, and then Davis foolishly held onto the ball instead of throwing it away and was sacked for a 14-yard loss.

    Wait — it gets worse. Out trotted Greg Zuerlein, who promptly missed a 38-yard field goal, wide right.

    The Chiefs took over at their 28 and even with back-to-back sacks by Quinn in the final 80 seconds of the half, they were able to tack on a Cairo Santos 53-yard field goal with 1 second left.

    It took Kansas City only 12 seconds to tack onto the lead to start the second half. For some reason, Zuerlein sent a line-drive kick that bounced to Knile Davis at the 1. Davis returned the ball 99 yards for a TD, with only Zuerlein having any kind of a shot at a tackle. Zuerlein whiffed.

    That play seemed to break the Rams’ back. They were never the same afterward.

    It became 20-7 Kansas City on the Chiefs’ next possession on a 28-yard field goal by Santos. The drive started at the KC 6, but the Rams helped the Chiefs downfield with a late hit by linebacker Alec Ogletree and a spearing penalty by Rodney McLeod that led to 30 yards in penalties.

    Also, a missed tackle near the first-marker by Jo-Lonn Dunbar helped Charles turn a short reception into a 30-yard gain to the St. Louis 14 on third-and-6.

    Charles hammered the nail into the coffin early in the fourth quarter with a 36-yard TD run to give the Chiefs a 27-7 lead.

    Avatar photozn
    Moderator

    Rapid Reaction: St. Louis Rams

    By Nick Wagoner

    http://espn.go.com/blog/st-louis-rams/post/_/id/12996/rapid-reaction-st-louis-rams-19

    KANSAS CITY, Mo. — A few thoughts on the St. Louis Rams’ 34-7 loss to the Kansas City Chiefs at Arrowhead Stadium:

    What it means: The Rams’ victory over Seattle last week offered a short respite to forget about all that ails the Rams. But it only took a week for many of those problems to come bubbling to the surface again. The Rams had plenty of chances to jump out to an early lead and make Kansas City work for this one, but instead reverted to their usual M.O. of self-destruction. Never was that more evident than a second-quarter sequence in which the Rams recovered a fumble at Kansas City’s 8 and came away with zero points. The Chiefs scored 34 unanswered points and that was that. At 2-5 with road trips to San Francisco and Arizona the next two weeks, things such as silly penalties, missed tackles and shoddy pass protection remain at the forefront for this team. Until those things change, the results will remain the same.

    Stock watch: Down — The offense, all of it. After an impressive opening drive, the Rams were wholly ineffective with the ball, with plenty of blame to be spread. Start with ineffective play calling that offered little in the way of creativity or adjustments, then go to an offensive line that was leaking from nearly every position to a quarterback who forced a bad interception in the first quarter to receivers failing to create separation. You name it, the Rams did (or didn’t) do all of it. All told, the Rams mustered 200 yards of offense, including just 20 in an atrocious third quarter.

    Injuries pile up: Speaking of the offensive line, a group that has mostly held up on the injury front so far finally had the issues that seemed imminent from the start of the season. Guard Rodger Saffold, center Scott Wells and left tackle Jake Long have been injury-prone in the past few years and it seemed to be a matter of time before it happened again. It happened all at once against Kansas City as Saffold (shoulder), Wells (elbow) and Long (knee) left the game and did not return. Receiver Brian Quick left with an arm injury and also did not come back. The Rams also took major hits at safety, where Rodney McLeod (knee) and Cody Davis (concussion) departed and did not return.

    Game ball: Defensive end Robert Quinn. In an ongoing theme this season, there wasn’t much to choose from here, but Quinn had his best day of the season, posting back-to-back sacks in the second quarter and forcing an Alex Smith fumble from behind in the opening quarter. After going without a sack in the season’s first five games, Quinn has three in the past two weeks and seems to be coming to life.

    What’s next: The Rams head to San Francisco to take on the 49ers for the second time in four weeks. It will be the second game in a three-game road trip.

    in reply to: Greg Zuerlein needs to be replaced. #10540
    Avatar photozn
    Moderator

    He’s 49 for 59 with a 60 yarder that’s 83%

    Adam Vinatiri is 83%

    Check out other kickers %

    83% is pretty good plus Greg the Leg has the capability kick 60 yarders.

    Today’s loss was not because of that miss.

    Reality is, …..in the spirit of Denny Green’s famous meltdown. Austin Davis is who we thought he was…

    This year so far though I think he is around 73%.

    in reply to: Barrett Jones #10538
    Avatar photozn
    Moderator

    i missed the last quarter. how did barrett jones look filling in at center?

    greg robinson at left tackle?

    The whole offense was a train wreck at that point so it was hard to tell. For me it was anyway.

    in reply to: Who is more responsible for the wasted draft picks? #10537
    Avatar photozn
    Moderator

    Lets face it, the Snisher record in the draft is not looking good. Should the Rams be looking for a good talent evaluator for the draft. Obviously Snead is not very good.

    I would say of any position they draft Offensive line is most important. Then Linebackers.

    Grits

    I think their draft record looks good. I have done this experiment where I go back and look at older drafts by good drafting teams. You want to go back before 2011, so you know how picks turned out. I counted a “hit” as a starter or important contributing role player on offense or defense.

    What I found was that on avg. 4 hits a year is GOOD to VERY GOOD drafting.
    (Anything beyond 4-5 a yr. on avg. = exceptional).

    2.5-3 a year = avg. drafting.

    2 a year = below avg.

    Less than 2 = bad.

    According to that model, although it’s way too soon to judge the Rams drafts, they certainly look like they are averaging 4 a year at least.

    The Rams draft well.

    I also found out that all good drafting teams have a 1st or 2nd round bust in there somewhere.

    To me, what we saw today was mostly due to multiple injuries.

    in reply to: OL injuries #10520
    Avatar photozn
    Moderator

    You know of course that Rams OLs have been eaten up with extensive injuries before.

    But let’s assume that Jones and Robinson can play. Maybe full of young mistakes, but can still play.

    You know–never in the multi-year history of Rams OL injuries have they had a Jones and a Robinson on the bench before.

    This is different.

    HOW different? Jeesh, I dunno.

    My old formula was this–any OL has injury replacements, and so on. But if you have to replace as many as 3 guys including the OC and LOT, then teams just can’t play. The offense suffers.(I’ve been repeating that formula practically word for word for years now.)

    But it may not be THAT level of bad if the depth at 2 key positions was your future anyway.

    Ironically, though, I also remember the old Bulger debates. I don’t know if anyone here got into them, but back then, in 2007 and 2008, some of us kept saying that if the OL suffers massive injuries, the qb can’t play. On the old huddle, there were people who denied that. They put it all on Bulger. Today, some of the same people out on the net are claiming that the issue today was not Davis, it was the OL injuries. A complete about face.

    And I agree, Davis suffered cause of the OL injuries. But then in 2007, so did Bulger. In the first half of 2012, so did Bradford.

    I have even seen someone say this is the worst they have seen a Rams OL play. Well…no. It ranks right there with some of the worst OL games of 2007, 2008, and 2009 though.

    in reply to: Jeff Fisher ? #10517
    Avatar photozn
    Moderator

    I do not see improvement. You can try and blame it on injuries

    I won’t blame it on injuries if you can name a team that won with injuries like this. So far that’s the #1 and #2 qb and 6 other regular starters. I will settle for 1 qb and 6 other starters.

    If you can’t name a team that won with injuries like that, then, strongly consider the possibility that dismissing EXTENSIVE injuries as an explanation of a game like today is short-sighted and unrealistic.

    in reply to: I owe ER an apology for screwing up. #10514
    Avatar photozn
    Moderator

    Zn my old friend I said minor annoyance,not anything to make a big deal I just thought I should tell you know about it. Thank’s for the apology but really no apology is necessary

    You do get that I ended up stupidly deleting your “Barnes” post. That’s the 2nd mistake I was trying to explain. If it were just a moved thread that needed to be un-moved, I would think, okay, zn, take your time and be more selective combining threads next time. But I glitched every step of the process and ended up with an improperly deleted post.

    So I don’t know if I am apologizing so much as just confessing to being “guilty on account of temporary dumbassery.” s

    in reply to: OL injuries #10513
    Avatar photozn
    Moderator

    Not sure how it all works. I know they can’t cut him right now–but next year when he’s healthy again. How does it work? Do they save his cap money by releasing him or do they take a big hit? Honestly, I don’t know what the situation is regarding all of that. Just curious if anyone knows.

    Someone will come along who knows this better than I do. But, my limited understanding is, once he is under contract, any football related injury means he’s part of the team. I don’t know how it works to cut him while re-habbing…I think after the season, they have to reach an injury settlement.

    in reply to: OL injuries #10510
    Avatar photozn
    Moderator

    So I guess Robinson takes over the LT duties now.

    As for Long? I don’t know the cap issues with cutting him at this point. We’ll have to see.

    I don;t know if Robinson moves to LOT, but if so, damm lucky thing he practiced there.

    You can’t cut an injured player. Not like you’re thinking.

    in reply to: OL injuries #10506
    Avatar photozn
    Moderator

    cgsuddeath wrote:
    Looks like long is out for the season again.So ends the Jake Long experiment

    What’s wrong with Long? What happened?

    Got it.



    Per league source, Rams fear LT Jake Long suffered torn ACL today.
    — ProFootballTalk (@ProFootballTalk) October 26, 2014

    Rams, Jake Long believe he has re-torn ACL

    by Mike Florio

    http://anonymouse.org/cgi-bin/anon-www.cgi/http://profootballtalk.nbcsports.com/2014/10/26/rams-jake-long-believe-he-has-re-torn-acl/

    Two key members of the Rams’ offense tore ACLs last year. Now, both have re-torn the same ligaments this year.

    During the preseason, quarterback Sam Bradford suffered the same season-ending injury as he suffered a year ago. On Sunday, the Rams and left tackle Jake Long believe he tore the same ACL that was torn last season.

    An MRI is expected to confirm the ACL tear on Sunday night. It would be a surprise at this point if the MRI shows anything but the ACL being torn.

    in reply to: posters lament the Chiefs game #10505
    Avatar photozn
    Moderator

    They’re the Washington Generals of the NFL.

    Is that a silver lining?

    kidding.

    This is 2011 all over again.

    .

    in reply to: OL injuries #10504
    Avatar photozn
    Moderator

    Looks like long is out for the season again.So ends the Jake Long experiment

    What’s wrong with Long? What happened?

    in reply to: I owe ER an apology for screwing up. #10502
    Avatar photozn
    Moderator

    Well actually ER it’s worse than you said.

    I got a brain glitch and thought you had started the OL injuries thread. I thought you were complaining that your follow-up post was then orphaned. I fixed it, I thought, by combining your 2 posts and then deleting the orphan.

    And I double-checked. You didn’t start the OL thread. CG did. So … I didn’t combine YOUR 2 posts. What can I say, I F’ed up, and am embarassed. You’re important regular poster and I hope I didn’t offend you.

    So that’s a double screw-up. One, yeah, the OL injuries thread did not belong in the post-game thread. That was a little insensitive on my part.

    Then when I thought I fixed the orphan thing, I made it worse.

    So, my sincere apologies.

    It was just a brain glitch day. I can only apologize again. It wasn’t just bad judgement, it was ordinary dumbassery.

    Unless people think otherwise, I think that combining threads on the same topic–particularly when we have multiple news articles on the same thing–is a good idea.

    Sometimes combining conversation threads is a good idea.

    But from now on, I will be much slower to do it and more selective. Time for a little more anarchy (that’s said with fun sincerity, it’s not ironic.)

    Fair enough?

    If you don’t think it’s not fair enough–speak up. This thread is about honesty.

    in reply to: I owe ER an apology for screwing up. #10493
    Avatar photozn
    Moderator

    zn wrote:
    Have at it.

    Who has a silver lining?

    <ZN I am not liking having my posts micro managed. The comment “and Barnes” makes even less sense than usual when you move it to from the OL thread and lump it in with the post game venting stuff.The silver lining is this minor annoyance got my mind off the 2 hour abomination I just watched.

    Well, we combine threads that are on the same topic. If it’s time to re-think that, then, that;s fair. In this case, your complaint about “and Barnes”–I fixed that with an edit. I didn’t notice that before.

    There’s 2 ways this works. One is, all threads just stay. If someone starts a thread, it just has its own life and lifespan. But then threads go off the page faster, and you see 1-2 at best reply threads on page 2 no one looks for, with new 1-2 response threads on the same topic on page 1. If you combine threads that are posted close together on the same topic–like reactions to the KC game on game day, for example–more participate and there’s more action and conversation, and things don’t move off the 1st page as fast. The danger there, of course, is that someone may think they’re just being pushed around, plus it gets down to the judgement of the combiner.

    OR if you would prefer I move your post back out as a separate thread about OL injuries, just ask. That’s easy.

    So is this a one-time thing? Or is it a genuinely a board issue? I can set us up to discuss it as a board if that’s how you feel.

    Let me know. That’s sincere.

    in reply to: what challenges do the Rams face with KC? Can they win? #10473
    Avatar photozn
    Moderator

    Lots of questions for this game. Same as the other games but in a new framework. Are they progressing or was Seattle one of those “every 21st game the Rams beat someone” games.

    * can they play with a rookie secondary
    * have they re-wired Ogletree
    * this game ought to let the DL do some damage
    * can they contain the edge or will Charles set a world’s record for yards per carry
    * the Rams OL + Mason and the other backs could be a strong suit.
    * who is Austin Davis
    * can they neutralize the KC pass rush

Viewing 30 posts - 46,441 through 46,470 (of 47,913 total)