Skip to content
View in the app

A better way to browse. Learn more.

BluegrassPreps.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Bengals 34 Chiefs 31

Featured Replies

On 1/4/2022 at 4:45 PM, oldgrappler said:

While I don't want to get entwined in a lengthy back and forth with @futurecoach, the call at the end of the game to go for it on 4th down instead of kicking the FG was not the right call.  Take the "sure" points, you go ahead and force KC to score in 50 seconds.  It is pretty difficult to get a TD in 50 seconds.  They may get in FG range.  But they have to make the kick.  So worst case scenario, you go into overtime.  Likely scenario, you win the game with a FG.  

Zach Taylor chose not to kick the FG and the attempt to score a TD on 4th down actually failed, twice.  And they still got another play!  Penalties gave the Bengals life when they could have just as easily have turned the ball over on downs.  In addition, KC says the officials missed a flinch by the Cinci guard on third down.  That would have moved the ball back to the 6 yard line.  HC Zach Taylor is very fortunate that offsetting penalties were called and he got a do-over.  What are the chances of that?  Exceedingly slim.  Had he not got the benefit from the ref, the game goes to overtime.  The outcome was fortuitous.  It had very little to do with Taylor making the right call.  The best way to win was to kick the FG.  Which is what happened, btw.  Taylor was lucky, not smart.  

A lot should go into a decision like that.  I think Zac knew his kicker was hurting and a short kickoff (after a FG) would be likely.  Yes, KC would have to make the kick, but the Bengals had to make the kick too, with a kicker nursing a groin issue.  If you don't score on 4th down you are still forcing KC to then go 65 yards from the 1 to get within FG range versus the 25-30 yards needed after a kickoff.

All that being said... I may have gone for it once, but after that I would have kicked the FG.  

 

  • Replies 48
  • Views 4.8k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • oldgrappler
    oldgrappler

    Congrats to Cincinnati.   But that was a bone head call to go for it on 4th down when a FG wins it.  They had to rely on a penalty to stay in possession.  They were very fortunate.

  • That was the equivalent of drawing a 19 in Black Jack and asking for the dealer to “hit me” twice (somehow drawing two aces). Oh yeah, and the house was holding an 18.

  • I'm sure that would be me and you don't have to go back 20 years. I'm still glad that this was not a Nationally televised prime time game.  Baby steps. Burrow is a treasure.  After suffering

22 hours ago, REALSPORT said:

A lot should go into a decision like that.  I think Zac knew his kicker was hurting and a short kickoff (after a FG) would be likely.  Yes, KC would have to make the kick, but the Bengals had to make the kick too, with a kicker nursing a groin issue.  If you don't score on 4th down you are still forcing KC to then go 65 yards from the 1 to get within FG range versus the 25-30 yards needed after a kickoff.

All that being said... I may have gone for it once, but after that I would have kicked the FG.  

 

Do you mean, you would have "gone for it once" on 4th down?  

On 1/7/2022 at 10:22 AM, oldgrappler said:

Do you mean, you would have "gone for it once" on 4th down?  

After the first 4th down penalty I think I would have sent the kicking team out.  I wouldn't have pushed my luck twice.

Home cooking at it's finest, and I'm not talking about Skyline.

Thank God the Bengals scored that TD after the whistle was blown..

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.