Example of Foles missing an easy TD and why we need Quick

  • To unlock all of features of Rams On Demand please take a brief moment to register. Registering is not only quick and easy, it also allows you access to additional features such as live chat, private messaging, and a host of other apps exclusive to Rams On Demand.

maximus

Rookie
Joined
Sep 29, 2015
Messages
118
Drive 7 Comes up after Chicago goes up 24-10.

Ends with another Foles to Welker misconnection on 3rd. Same problem, Foles not having the feel of Welker's speed out of his cut.

Drive 8

Just before the half.

On 2nd down

tsO56pX.png

After Foles releases the ball, Young lines him up for a dirty hit

C6qFlCd.png


Young delivers the dirty hit. Hits Foles' chin with the crown of his helmet. Should had been personal foul. Even the announcers noticed it. The refs were out to get the Rams, while letting everything slide for the Bears. No flag. Although the refs did notice when Cutler was hit with the helmet, they flagged the Rams for that when the Bears took the 17-10 lead.

On 3rd down Kendricks drops it, but it does not matter, as the throw was 2 yards short of the sticks. After this Chicago runs down the clock, the half ends.

Coming back to that Benoit tweet.

#Bears Film: CB’s Porter, Fuller and Callahan all flashed in first half.

So Benoit said all Bears CB flashed, which means they played very well, which means they covered very well, which means Foles was very limited of where he could go with the ball.
 

jrry32

Rams On Demand Sponsor
Rams On Demand Sponsor
Joined
Jan 14, 2013
Messages
29,932
The D did put up a huge stinker against a very beatable Chicago offense, the same offense which the Seahags SHUT DOWN during the whole game.

The OL did put a huge stinker, with 3 holding calls and one blindside block, which helped kill 4 drives while Chicago was taking a 2 TD advantage.

The running game was non-existant outside the 1st drive, apart from a fumble, which killed another drive.

Let's see the huge stinker put up by Foles

2nd drive 3rd down

AsOSsN5.png


Welker about to make his cut, Foles loads up the throw

1f8BO1m.png


Foles about the release the ball. Welker made his cut and looks like he will run along the yellow line. A moment later Foles releases the ball, so he cannot change the direction of the ball in this moment.

g4anXIp.png


Foles had released the ball, unfortunately Welker stops.

BbYlkbC.png


Where Foles put the ball. Dead center between the 2 defenders. If Welker had kept running after his cut, the ball would have been right on him. Unfortunately Welker stopped right after his cut, while Foles thought he would keep running.

Lack of chemistry between Foles and Welker doomed this play. It was exactly the same with the other 3rd down throws to Welker. On 2 other 3rd down throws to Welker, Foles did not had a good feel for Welker's speed coming out of his cut. One of those makes the object of this thread, I already analyzed in the post above.

The 2 were not on the same page, no surprise considering that Welker had just arrived. Welker was getting open, so can't fault Foles for looking for him. 3 drives were killed in the first half because of the lack of chemistry between Foles and Welker, and those misses played in big part in why Foles looked bad.

You wasted time making a post excusing Foles on a throw I already agreed with you on. That was miscommunication.

That throw isn't the problem. The other 20 inaccurate throws in that game were.

That is simply not true.

PQTEMbx.png


Nowhere near to being close to the dirt. Nowhere near. Welker is 1 yard short of the sticks, even falling down the ball was above his shoulders.

What happened was the Welker was one step behind the throw. That is why he undercut it. If Welker was a step in front, it hits him right between the numbers, with Welker being in a great position to break an arm tackle and get the TD.

Foles did not had chemistry with Welker, he did not had a feel for Welker's speed out of his break. Which is understandable, knowing that Welker has just arrived in St Louis It made sense for Foles to put it where he put it, because in the reverse situation, if Welker is faster and Foles thinks he is slower, the throw ends up behind Welker for an easy pick six.

Yes, Welker is falling down. That ball was on a downward trajectory. It was going into the dirt and wide of the WR. Welker undercut the ball because it was thrown inaccurately. Kind of like the majority of Foles's throws in this game.

Not woulda coulda shoulda. Just Kendricks catching a perfect deep ball from Foles which hit him right in his chest between the numbers. 13 points would have been enough to win the game. There are slugfests in the NFL, just to let you know. Just this past week, Houston beat the Bengals 10-6, the Bucs beat Dallas 10-6.

And no non-delusional person would tell you those QBs played well enough to win. Getting bailed out by the defense isn't playing well enough to win. 13 points sucks ass. And in case you forgot, Foles tossed an INT with the ball in his hands late in the game with the chance to win. That's not playing well enough to win. That's called shitty QB play.

BTW, yes, that is woulda coulda shoulda. Because you're not talking about what happened...you're talking about what would have happened or what should have happened or what could have happened.

Missed Britt deep? You do realize Fisher was afraid of the strong wind, that he did not even kick the extra point? What makes you think Foles was also afraid of the strong wing in the first play of the game, the strong wind could had easily slowed down the ball, allowing the trailing CB to catch, for a pick 6 maybe, seeing that the play was in Rams part of the field.

Wow. You want a QB that is afraid of throwing to a wide open WR because of the wind.

Only 18, against a very good Vikings defense, which limited franchise QB Derek Carr to even less 14 points. The same Derek Carr who in the previous home game put up 34 points against a good Jets defense. That Vikings D is a very good defense, the main reason why they have only 2 losses on the season.

Carr
67.4% completion%
302 yards
7.0 YPA
2 TDs
2 Ints
83.7 QB Rating

Foles
54.5% completion%
168 yards
5.1 YPA
0 TDs
0 Ints
68.6 QB Rating

Don't even talk about those two in the same sentence. Foles was an anchor. He dragged the Rams down and cost us a win. Carr did his damnedest to elevate his team to a win.

The game in GB really screwed his statistics. The game where he was nearly killed in the first half, then he started throwing picks left and right.
That GB game is the only game in Foles' NFL career in which he has thrown more than 2 picks. The only one. It is very clear that the bad beating he took in the beginning of that game Marc Burgered and David Carred him for the rest of that game, which ended with 4 picks and 11 rating, which have really destroyed his statistics.

Good. He was total garbage in that game. And cost the Rams a potential win. His statistics suck because Nick Foles sucks. There are plenty of other good QBs in the NFL that have had bad games. It didn't destroy their numbers. Because they did more than be a crappy game manager in 6 of their other 8 games.

And yet, if Austin and Kendricks catch 2 well thrown deep passes from Foles, the Rams are 6-3.

Oh wow! If Austin and Kendricks don't drop passes, the Rams would be 6-3 DESPITE Foles. But if the Rams actually had a good QB, they'd be 7-2 or even 9-0.

In the Bears game, the D did crap the bed, the OL did crap the bed with numerous penalties with put the offense in bad positions, the WRs did drop the ball. It was not just Foles that is for sure. Yet only Foles got all the blame.

Nobody cares. Foles is getting blamed because he's been an anchor all year. He's dragged down a team that should be competing for the playoffs into mediocrity.

I guess you forgot to mention the 2 well thrown deep balls from Foles, 1 led to the TD, the other 1 should had led to a TD as well, if Tavon held onto a well thrown deep ball. That would definitely been more than enough to get the win.

First of all, that was not a well thrown deep ball to Austin. If it were well thrown, Austin would have had to fully extend for it. Austin should have caught it but don't try to make that throw out to be some thing that it is not. Second of all, here's your problem. You are completely content with Foles being garbage for almost the entire game except for one drive and one throw.

We don't care. We want competent QB play so that we aren't blaming losses on the couple plays in a game where the QB wasn't hot garbage. If we had a quality QB, we win that Minnesota game going away.

Cost the GB game? When he got nearly killed in the first half? Wow. The hate is really strong in this one. The only game since he's been in the league he's thrown more than 2 picks, the bad beating he took without a doubt shellshocked him, leading to 4 picks, 11 rating which have destroyed his stats.

Yep, cost us the Green Bay game. Maybe you forgot his two red-zone interceptions and the pick six we threw. Wipe the pick-six off the board and the score of that game is 17-10. Which means that if the Rams punch it in the end-zone on one of the red-zone possession and kick a FG on the other, we win the game. Foles cost us between 13 and 21 points (AT LEAST) in a game we lost by 14.

Yep, the OL was shit. No argument there from me.

But isn't it convenient that there's is always SOMEONE ELSE to blame. Somehow, it can't be both Foles and the OL that played like shit. No, Foles was an innocent victim. Spare me. You're act like an excuse machine for the guy.

Cost the Minn game? If Tavon helds onto a good deep thrown ball from Foles, that is more than enough to win. If the OL does not allow pressure in Foles' face 1 sec after the snap on that intentional ground play, the Rams kick a FG after that play and win the game.

Yes. He cost us the Minnesota game. He played like shit. Watch the game. Tavon actually contributed something positive to the team in that game.

As usual, it's everybody else's fault.
 

jrry32

Rams On Demand Sponsor
Rams On Demand Sponsor
Joined
Jan 14, 2013
Messages
29,932
Wrong. The ball went right through his hands. That is a drop.

It was 3rd and long, because of the holding penalty. Foles did not know the exact moment Britt would make his cut. Benoit told the truth when he said the CBs of the Bears ran the route for the WRs. This was a prime example of that.

That is a drop. And a late throw. Orchid is right. Ball was thrown late which allowed the CB to close.

And if Foles doesn't know when Britt will make his cut, neither of them should be on the field. The WR routes are drawn up very precisely exactly so the QB knows where he will make his break and when to make the throw. That's why route running is so important in the NFL. Ball should have been on Britt as he was coming out of his break. And as your second picture shows, Britt has plenty of separation at that point.(despite him running a mediocre route)
 

maximus

Rookie
Joined
Sep 29, 2015
Messages
118
Second half starts.

1st drive

Rams get to 2nd down and 7. Then this happens

  • 2nd and 7 at STL 48
    (12:56 - 3rd) N.Foles pass incomplete deep right to J.Cook [J.Jenkins]
The announcers absolutely killed Foles for this play. Foles was too late, that play was on all Foles, they said. Viewers were outraged, it set the tone for the 2nd half, when every Foles mistake was magnified 10 times.

Let's see what happens on this play.

But first I have to look at the first play of the game, very successful play when Cook gains 29 yards

DjwOE8S.png


From the left side of the OL, Cook runs behind the OL.

kM49Dak.png


The Bears were kind enough to bite hard on the fake. The flat was wide open. Easy pitch and catch for 29 yards.

Back to the 2nd half 2nd and 7 play

zitEOwO.png


Almost the same play, with the added wrinkle of 2 receivers up top instead of 1. Kendricks starts to run behind the OL.

DMDRluZ.png


Brown gets blown back 3.5 yards. Kendricks trips over his leg.

3HCL1X0.png


Kendricks falls down.

JJlwlhy.png


Kendricks gets up again and moves ahead of the edge defender. Foles is looking behind #26 of the Bears. #26 turns around, thinking someone has sneaked behind him.

C4KY3XD.png


#26 turns around, but there was no one behind him. Foles had fooled him to get the flat wide open. With #26 turned around, the flat is wide open, unfortunately Kendricks is held and pulled by the jersey by the edge defender. Obvious holding by the defense, no way the refs did not saw that, but they were out to get the Rams, and let everything slide for the Bears.

Foles was obviously looking for a repeat of the 1st play of the game, he worked #26 to get the flat wide open, the flat was wide open for an easy 10 yard gain at least. Problem was, Kendricks got tripped by his own OL, he fell down, then he was held, his jersey was blatantly pulled, he could not get to the flat. The play was there to be made, had Kendricks not gotten tripped. Easy pitch and catch for at least 10 yards.

DAdwS3t.png


Foles has realized the throw to the flat was not there, he now looks for Cook.

MaZC5Dd.png


But it's too late, he throws it under pressure off his back foot, the ball ends out of bounds.

Foles got murdered by the announcers for this play. He was too late, this play was on all Foles they said. Did they saw Kendricks getting tripped, falling down, being blatantly pulled by his jersey? No, what they saw was only Foles being very late to Cook. It is true that the throw to Cook was very late, but IMHO Foles was looking for a repeat of the 1st play of the game. Even with Kendricks falling down, the play was still there, had the edge defender not pulled his jersey. Foles never saw the jersey being pulled, he probably thought the play was still there.

The refs definitely saw the jersey pull, but they were not there to throw flags on Chicago.

On 3rd down, Foles connects with Tavon for a 1st down for 12, only to be nullified by another holding penalty. 3rd and 17, good luck with that. Punt.

  • 3rd and 7 at STL 48
    (12:49 - 3rd) (Shotgun) N.Foles pass short middle to T.Austin to CHI 40 for 12 yards (B.Callahan). PENALTY on SL-G.Robinson, Offensive Holding, 10 yards, enforced at SL 48 - No Play
 

maximus

Rookie
Joined
Sep 29, 2015
Messages
118
2nd drive of 2nd half

Rams get to 3rd and 7 in the redzone, after a strike by Foles to Quick on a slant moves the ball 37 yards

Then this happens
  • 3rd and 7 at CHI 20
    (2:53 - 3rd) N.Foles pass incomplete short middle to T.Austin
I said it was a drop, and that is what it was.

6NLl7AG.png


This is after the catch, Tavon has it in both his hands, close to his body, with the defender 2 yards away ( 2 steps away). He definitely had time to secure it. Unfortunately he does not do that. Defender dislodges the ball. Incomplete. FG.

About this play, there are these claims

Bad play by Tavon. But also a bad play by Foles. He threw the ball high, made Tavon extend for it, and that allowed the DB to punch it out before he could protect the ball. If Foles had put that ball in the strike zone, Tavon can protect it sooner and gets hit with the ball in stride allowing him to make something happen after the catch..

The reality is that Foles could NOT had placed it better.

XoaZP3G.png


There is a defender's hand right in the passing lane. The ball barely cleared the outside of that hand.

Foles put the ball in the only place
1 Tavon could catch it,
2 The ball does not hit the defender's hand.

If Foles throws the ball to the inside of that defender's hand, the ball ends up way behind Tavon, for an easy pick 6.

It was a good throw and a good play by Foles, but of course he has to be blamed for everything.

The reality is, Tavon had the ball in his hands close to the body, as the first picture shows, with the defender 2 steps away, he had time to secure the ball, but he made a young receiver's mistake, and the ball was disloged. I really like Tavon, he gives everything he has every time they call his number, he runs like a man possessed when they call him for a reverse, but he does make young receiver's mistakes. Should had hold on to this ball. It would had been a different game, with the Rams down only a score at that point.
 

jrry32

Rams On Demand Sponsor
Rams On Demand Sponsor
Joined
Jan 14, 2013
Messages
29,932
2nd drive of 2nd half

Rams get to 3rd and 7 in the redzone, after a strike by Foles to Quick on a slant moves the ball 37 yards

Then this happens
  • 3rd and 7 at CHI 20
    (2:53 - 3rd) N.Foles pass incomplete short middle to T.Austin
I said it was a drop, and that is what it was.

6NLl7AG.png


This is after the catch, Tavon has it in both his hands, close to his body, with the defender 2 yards away ( 2 steps away). He definitely had time to secure it. Unfortunately he does not do that. Defender dislodges the ball. Incomplete. FG.

About this play, there are these claims



The reality is that Foles could NOT had placed it better.

XoaZP3G.png


There is a defender's hand right in the passing lane. The ball barely cleared the outside of that hand.

Foles put the ball in the only place
1 Tavon could catch it,
2 The ball does not hit the defender's hand.

If Foles throws the ball to the inside of that defender's hand, the ball ends up way behind Tavon, for an easy pick 6.

It was a good throw and a good play by Foles, but of course he has to be blamed for everything.

The reality is, Tavon had the ball in his hands close to the body, as the first picture shows, with the defender 2 steps away, he had time to secure the ball, but he made a young receiver's mistake, and the ball was disloged. I really like Tavon, he gives everything he has every time they call his number, he runs like a man possessed when they call him for a reverse, but he does make young receiver's mistakes. Should had hold on to this ball. It would had been a different game, with the Rams down only a score at that point.

As usual, your pro-Foles spin leads you to prop up a bad play by Foles and put all the blame on other players for his mistakes.
Foles_2_zpsmxqtrb4n.png

Foles_3_zpstyn1bn9q.png

Foles_1_zpsffewzptk.png

Foles_4_zps23tkqxxj.png

Foles_5_zpsyuwe4n1d.png

Foles_6_zpsyx7s6ho4.png

Foles_7_zpsd81nxh0v.png

Foles_8_zpsfhb3pdoa.png

Foles_9_zps2fynkjhh.png


Did Austin drop this ball? Yes. He should have caught it. And he should have prioritized putting the ball away over getting up-field. However, Foles was late on the throw as usual, the throw was not placed well, and forced Austin to leave his feet. By the time he got his feet down, he got hit before he had a chance to even get a full step up-field. He likely had time to put it away but Austin wanted to get up-field to try and make a play. Was that a mistake? Yes.

But should that mistake have even happened? No. Foles should have been letting the ball go at picture #4 when Austin is coming out of his break and has his head around. If he does that, he hits Austin much sooner with the huge throwing lane that the OL gave him and gives Austin a chance to pick-up a ton of YAC. Instead, Foles didn't release it until picture #5 which is two steps later. He forces Austin to slow down and jump for the ball which allows the DB to close on the play and hit Austin knocking the ball loose.

The ball should have arrived at picture #5. Instead, that is when Foles is releasing the ball. Look at how much separation Austin has. You want to know why Brady's WRs always seem so wide open? He gets the ball out on time. If you release when Austin is coming out of his break, he has massive separation and an opportunity for a ton of YAC. When you throw late, NFL defenders close.

But tell us all again how it was a good play by Foles, a good throw, and could not have been placed better. I'm sure you're really getting a lot of people to buy this pro-Foles blame-every-other-Ram BS.
 
Last edited:

maximus

Rookie
Joined
Sep 29, 2015
Messages
118
Drive 3 of the 2nd half

It starts with another OL penalty, for good measure. False start. 3 holding calls and one blindside block were not enough. Had to put the offense in another hole. Blame Foles

Rams get to 3rd down.

  • 3rd and 11 at STL 19
    (10:50 - 4th) (Shotgun) N.Foles pass short right to L.Kendricks pushed ob at SL 23 for 4 yards (J.Anderson)
So the play starts at 10:50

zkRfD4x.png


1 sec after the snap, pressure is coming, Foles on the run. Bears rushed only 4, dropped 7 in coverage. Still they got pressure up the middle 1 sec after the snap. Foles dumps it off for a 4 yard gain Then the fake punt.
 

maximus

Rookie
Joined
Sep 29, 2015
Messages
118
As usual, your pro-Foles spin leads you to prop up a bad play by Foles and put all the blame on other players for his mistakes.

But should that mistake have even happened? No. Foles should have been letting the ball go at picture #4 when Austin is coming out of his break and has his head around. If he does that, he hits Austin much sooner with the huge throwing lane that the OL gave him and gives Austin a chance to pick-up a ton of YAC. Instead, Foles didn't release it until picture #5 which is two steps later. He forces Austin to slow down and jump for the ball which allows the DB to close on the play and hit Austin knocking the ball loose.

The ball should have arrived at picture #5. Instead, that is when Foles is releasing the ball. Look at how much separation Austin has. You want to know why Brady's WRs always seem so wide open? He gets the ball out on time. If you release when Austin is coming out of his break, he has massive separation and an opportunity for a ton of YAC. When you throw late, NFL defenders close.

But tell us all again how it was a good play by Foles, a good throw, and could not have been placed better. I'm sure you're really getting a lot of people to buy this pro-Foles blame-every-other-Ram BS.

As usual, your Foles hate leads to spin any play by Foles as a bad one and to excuse any mistake of the receivers as Foles's fault

Once again, Foles did not know at which moment Tavon would cut his route.

O01AAfb.png


The moment Tavon made his cut, Foles is loading up the throw

DtDhckT.png


Foles about to release the ball, after Tavon made the cut.

I understand now. Every receiver mistake, every drop, every fumble, it is Foles' fault. Capisci. LOL.

You compare Foles with Brady? Ha. Genius. Compare Foles with Montana, then say Foles sucks. Compare Foles with Brady, then say Foles sucks. Wow. Your hate for Foles could not be more obvious.

I'm sure you can fool a lot of people with your every receiver's mistake, every drop, every fumble, is Foles' fault routine. This was a drop. But of course Foles got all the blame.
 
Last edited:

Memento

Your (Somewhat) Friendly Neighborhood Authoress.
Joined
Jul 30, 2010
Messages
18,325
Name
Jemma
@maximus welcome to the block party. Too tired of stuff to see your Foles mancrush at this point.
 

maximus

Rookie
Joined
Sep 29, 2015
Messages
118
In the same game, Cutler throws a very high ball to Z Miller for a TD

Dlb76YX.png


Z Miller, who is 6ft 5, has to jump as high as he can, extend his hands at far as he can, just to get to the ball.

Receivers catch high balls all the time. In every weekend, every game, you see receivers adjusting to the ball, high balls or low balls.
 

jrry32

Rams On Demand Sponsor
Rams On Demand Sponsor
Joined
Jan 14, 2013
Messages
29,932
Once again, Foles did not know at which moment Tavon would cut his route.

If you are honestly trying to claim this, you have no earthly idea how a NFL passing game works.

Not only does Foles know at which moment Austin will make his break, he knows the exact spot at which he'll make the cut, and the depth he'll be at after he comes out of the break.

You know what a "see it throw it" QB is? It's a QB that throws the ball AFTER his WR comes open. And that's one of the worst things a NFL QB can be. Read your quote again:
Foles about to release the ball, after Tavon made the cut.
 

maximus

Rookie
Joined
Sep 29, 2015
Messages
118
Drive 4 of the 2nd half

Foles gets sacked on 2nd down not long after the snap

Rams get to 4 down and 6

ObJHK9q.png


Who was open on this play? Foles is about to get sacked, he had to get rid of the ball. Incomplete

After this, the game was truly over. Foles then makes a bad throw into the dirt to Tavon, then he gets picked. He was even blamed for the OL injuries on the pick, but really? Every game you see QBs throwing picks, never see 2 OLs injured. Just bad luck. Apart from the GB game, that was only his 2nd pick in 8 games.
 

maximus

Rookie
Joined
Sep 29, 2015
Messages
118
If you are honestly trying to claim this, you have no earthly idea how a NFL passing game works.

Not only does Foles know at which moment Austin will make his break, he knows the exact spot at which he'll make the cut, and the depth he'll be at after he comes out of the break.

You know what a "see it throw it" QB is? It's a QB that throws the ball AFTER his WR comes open. And that's one of the worst things a NFL QB can be. Read your quote again:

Ever heard of Fisher ball? PROTECT the ball is the main priority, do not put the D in bad spots. Apart from GB game, that is what Foles has been doing throughout the season. That is obvious, the way Foles is throwing. Every play he is careful to not put the ball in harms way. It's been that way since the start of the season, I'm very sure it is by design.

Now combine that with Foles being in the first year in this offense, with new receivers, with very few slanting routes to Tavon until now, and you get this. Of course I know it's highly desirable that the QB throws the ball before the WR makes the cut, but that also leads to bad mistakes when they are not on the same page. I think Foles' main priority was protecting the ball, that is why he was throwing after the receiver made the cut. To reduce to minimum the mistakes.

Speaking of Brady, do you know how many receivers have failed in NE because they could not get on the same page with him? A TON. It's not easy to get on the same page. It takes a lot of practices, and a lot of games. Even then you still get bad mistakes, Brady threw 2 picks in the SB and 1 pick just last game at the Giants goal line, almost cost NE the game.
 

jrry32

Rams On Demand Sponsor
Rams On Demand Sponsor
Joined
Jan 14, 2013
Messages
29,932
It's been that way since the start of the season, I'm very sure it is by design.

No, it's not by design. Which is why Foles's ass is being parked on the bench.

Speaking of Brady, do you know how many receivers have failed in NE because they could not get on the same page with him? A TON. It's not easy to get on the same page. It takes a lot of practices, and a lot of games.

Receivers fail in that offense because it is an extremely difficult and complex offense. It is all about precision and timing with a ton of WR options on each play. It takes a high level of football IQ to succeed in that scheme. But it's also extremely difficult to defend when a WR is capable of handling it.
 

kurtfaulk

Rams On Demand Sponsor
Rams On Demand Sponsor
Joined
Sep 7, 2011
Messages
16,583
.

Seeing all those stills make me want to puke. 3 years of this shit we've had to endure. And it progressively gets worse.

Clemens>Austin>Hill>Foles

You know how badly foles had been going when those other 3 back ups played better than him.

.
 

maximus

Rookie
Joined
Sep 29, 2015
Messages
118
I listed the 12 drives before the game was over. 1st was the TD, on the other 11 drives.

-- 4 drives were killed by OL penalties (Rams had moved the chains on 2 of them, only to have those plays negated by OL penalties). Chicago also had a OL hold, and Cutler came nowhere close of converting the 3rd down

- 3 drives were killed by the lack of chemistry between Foles and Welker. Can't fault Foles for looking for Welker, Welker was getting open consistently on 3rd downs, problem was they had no chemistry, Welker had just arrived.

- 1 drive was killed by RB fumble

- 1 drive was killed when Tavon did not hold onto the ball.

- 1 drive was killed when Foles was sacked on 2nd down, and on 4th down he had nowhere to go with the ball

Those are 10 of the 11 drives after the TD.
The other drive was the one before HT. Foles sailed the throw over Quick on 1st down, then the Bears played very well coverage on the other 2 downs.

The D had a bad game.
The OL had a bad game.
The running game was non-existent after the 1st drive, making the offense 1 dimensional, making it much easier for the Bears to defend it.
Bears could bring pressure with only 4 guys, while dropping 7 into coverage the whole game. The Bears CB were playing very well, as told by Benoit. Obviously that limited severely Foles' options throughout the game. Benoit also told that Foles did not left many throws on the field, whereas Foles haters claimed he left a ton of throws on the field.

What hurt him the most were the OL penalties, which put the offense in bad situations numerous times and the non-chemistry with Welker. Quick also missed a ton of time, all training camp, the first games, then he was slowly integrated into the offense.

Was Foles set up for success with these circumstances? No, he was set up for failure by the circumstances of the game.
 

Memphis Ram

Legend
Joined
Jun 26, 2010
Messages
7,352
Once again, Foles did not know at which moment Tavon would cut his route.

Er...shouldn't he know this?
tumblr_mme5dfIf6E1r38kv3o1_r1_500.gif


Or are we placing ALL of the blame on Tavon Austin?

And despite all of this back and forth, why do YOU believe the coaches benched him after giving him such a nice contract?
 
Last edited:

OldSchool

Rams On Demand Sponsor
Rams On Demand Sponsor
Joined
Nov 3, 2013
Messages
40,544
Wow never thought I'd see somebody try to make an inept QB look like a victim with stills. Nobody is saying the WR and OLine were great and didn't make mistakes. But it seems only one person is saying Foles was good.
 

Memento

Your (Somewhat) Friendly Neighborhood Authoress.
Joined
Jul 30, 2010
Messages
18,325
Name
Jemma
Wow never thought I'd see somebody try to make an inept QB look like a victim with stills. Nobody is saying the WR and OLine were great and didn't make mistakes. But it seems only one person is saying Foles was good.

-cough-RamStalk-cough-Bulger-cough-