![]() |
Going for it on fourth down and 25
The reasoning behind it is that either way, you need to make a stop, so why not take a shot at it.
The counter-argument in that scenario is that you leave the possibly of needing a touchdown rather than a field goal after the stop. I hope this starts a trend among coaches in the NFL to go for it in that situation. If you are inside your own ten down by one, the odds turn more in your favor to go for it. The worst-case scenario is that you are guaranteed a chance to get the ball with it being a one-possession game, since the opponent can't run the clock out |
concrete poured
|
I think Andy probably felt like his defense was cashed and would just get the ball run down their throats. Maybe there's a better chance of converting the 4th and 20 than getting the ball back.
|
If you don't make it and can force them to 3 and out with a field goal you still have time to try and score a touchdown
|
Mahomes is one of the few players in the history of the league who can convert this without it taking some fluke (and nearly did). Had no issue with it.
|
If we were in a 41-38 shootout and the offense was rolling then you go for it 100% of the time there. The offense did not look in sync at all in that moment though. Just looked like they were forcing things and playing in a state of panic. You can just tell when the offense feels like the second half vs the Eagles compared to the second half vs the Bengals a couple years ago where they were just completely out of whack. It just didn't feel right at all. And of course that's exactly what happened, Mahomes had to run around and throw up a prayer and the WR couldn't make the play, which is consistent with how they looked on that drive.
|
Um it went straight into the hands of Moore and should have been a 1st down.
|
This shouldn't even be a talking point.
|
Mahomes messed up on 3rd and 20. There was a wide open receiver (Watson?) who could have gained 10-15 yards, making the 4th manageable.
I don't understand going for it on 4th and 25. It leaves the Lions in FG position if you don't make it and then you need a TD not a field goal to potentially drive and win. It would have been a tough catch, but Moore has to come down with a ball that hits both hands. |
<blockquote class="twitter-tweet" data-dnt="true"><p lang="en" dir="ltr">For all the (deserved) Toney talk, Mahomes created a miracle on 4th and 25 and Moore let it bounce off his hands. <br><br>Maybe he was targeting Watson, but this should have absolutely been caught. <a href="https://t.co/nvRAzav7PN">pic.twitter.com/nvRAzav7PN</a></p>— Seth Keysor (@RealMNchiefsfan) <a href="https://twitter.com/RealMNchiefsfan/status/1700121335849267444?ref_src=twsrc%5Etfw">September 8, 2023</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
|
Quote:
At least that forces Andy to keep the ball in Mahomes' hands. |
Quote:
Personally I did not like the decision. Well, at least not how it played out. If you’re going to go for it on 4th and 20, then you need to use 3rd and 20 to gain 8-15 yards, not chuck up a prayer ball beyond the sticks. |
It was the right decision.
Even if it doesn't work, you still have three timeouts. If you punt, you still have three timeouts. Either way, you need a stop from the defense. The defense didn't stop them. The game ended. Why are people talking about this decision like it mattered? It's kicking a FG on 4th and 2 or 4th and 3 earlier that mattered more. |
Personally in that situation I wanted a punt. Usually I want mahines to have one more shot but I thought we could put pressure on Detroit punting. Their offense didn't have to get a first down to kick a field goal but pin them back on their side and maybe we can sell out on the run and force goff to have to throw on 3rd to put the game away.
Honestly I was ok either way though. I agree that the field goal tries on 4th and short were the real issue. |
Didn't care for it at the time, but the ball was clearly catchable
|
All times are GMT -6. The time now is 09:36 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.