Started By
Message
locked post

Can we talk about spiking the ball with 23 secs left?

Posted on 9/12/22 at 11:21 am
Posted by Hester Carries
Member since Sep 2012
25960 posts
Posted on 9/12/22 at 11:21 am
The second that happen I was like “I’ve seen this movie before”


Posted by Chad504boy
4 posts
Member since Feb 2005
179950 posts
Posted on 9/12/22 at 11:23 am to
Should have been rush to the line, but then jameis had the brains to let the clock keep ticking down. ATL would have likely used their own TO at that point.
Posted by Bonkers119
Baton Rouge
Member since Dec 2015
12107 posts
Posted on 9/12/22 at 11:30 am to
Having a 10 yd loss there wasn't great, but the offense was on fire. We weren't gonna be stopped.
Posted by Hester Carries
Member since Sep 2012
25960 posts
Posted on 9/12/22 at 11:30 am to
quote:

Having a 10 yd loss there wasn't great, but the offense was on fire. We weren't gonna be stopped.


Not talking about that spike.
Posted by Ancient Astronaut
Member since May 2015
37430 posts
Posted on 9/12/22 at 11:31 am to
Yep gotta make atl burn a time out
Posted by Alt26
Member since Mar 2010
36226 posts
Posted on 9/12/22 at 11:51 am to
quote:

Should have been rush to the line, but then jameis had the brains to let the clock keep ticking down. ATL would have likely used their own TO at that point.


In the heat of the moment the QB is having to process many things quickly. It was already an unusual situation because he spiked it on first down (though I don't necessarily blame Winston because Landry caught the ball in bounds and looked like he was down in bounds). Then, in the rush, he wanted to make sure above all that the Saints at least got a chance at a FG.

Perhaps I'm wrong, but I think the coaches were still able to communicate (via his mic) with Winston. That's when, as a QB, you probably want your coach to help you out by letting you know the situation.
Posted by Hester Carries
Member since Sep 2012
25960 posts
Posted on 9/12/22 at 11:55 am to
quote:

Then, in the rush, he wanted to make sure above all that the Saints at least got a chance at a FG.


I would understand at like 10 secs. But 23!?
Posted by Seen
Member since Aug 2022
1127 posts
Posted on 9/12/22 at 11:59 am to
Honestly I think he and DA just panicked. DA basically admitted to it, glad we got the win. I mean they played clutch but definitely some panicking with clock management
Posted by bayouboo
Member since Jan 2007
3669 posts
Posted on 9/12/22 at 12:00 pm to
The ref should have communicated to Winston the situation or not released the ball to play.
Posted by adamb2151
Houston, Texas
Member since Jun 2013
6586 posts
Posted on 9/12/22 at 12:02 pm to
Jameis didnt know it was third down. He was surprised when he found out it was 4th down and we had to kick. We lost the down on grounding call. Prob why he was confused and thought he would have another play.
Posted by Weekend Warrior79
Member since Aug 2014
22282 posts
Posted on 9/12/22 at 12:06 pm to
quote:

I would understand at like 10 secs. But 23!?

Mentioned this in another thread. Clocking at or under 10 seconds is a hell of a lot bigger gamble than at 23 (in this scenario). If they try to milk it to 10 or under and there is a procedure penalty, 10 second run off and no FG try. Should have done it around 15 seconds, maybe 12; but definitely not under 10
Posted by Damone
FoCo
Member since Aug 2016
32966 posts
Posted on 9/12/22 at 12:09 pm to
All of this just makes me realize how much shite is going through the heads of a HC and QB at the end of a game.
Posted by goatmilker
Castle Anthrax
Member since Feb 2009
77199 posts
Posted on 9/12/22 at 12:18 pm to
Sure have
Posted by Lester Earl
3rd Ward
Member since Nov 2003
291701 posts
Posted on 9/12/22 at 12:20 pm to
Feel like the refs need to be more clear with the call on field. Still thought he was touched in bounds
Posted by Alt26
Member since Mar 2010
36226 posts
Posted on 9/12/22 at 12:59 pm to
quote:

I would understand at like 10 secs. But 23!?


I think in the heat of the moment Winston just forgot it was 3rd down...really because the series of downs started awkardly with him being penalized for spiking the ball on first down...resulting in an intentional grounding call and loss of downs. Usually when you spike the ball you are not getting a penalty. Particularly one that results in a loss of downs. So think Jamies just routinely thought the pass prior to the third down spike was 1st down...not 2nd down.

The officials ruling Landry out of bounds...when in the moment he looked like he was down in bounds kind of set the whole funky sequence in motion.
Posted by unctiger4
Member since Mar 2015
2483 posts
Posted on 9/12/22 at 12:59 pm to
quote:

Feel like the refs need to be more clear with the call on field. Still thought he was touched in bounds


It was clear as day. Landed a yard inbounds and defender made contact on the way down. Very weird missed call that I don’t see happen often.
Posted by GeauxldMember
Member since Nov 2003
5758 posts
Posted on 9/12/22 at 1:03 pm to
quote:

Jameis didnt know it was third down. He was surprised when he found out it was 4th down and we had to kick. We lost the down on grounding call. Prob why he was confused and thought he would have another play.


He had the “shite, man” look on his face and was holding up two fingers right after the spike, so I do think he thought it was only 2nd down. Either way, it worked out.
Posted by LSUgrad88
Member since Jun 2009
9424 posts
Posted on 9/12/22 at 1:34 pm to
quote:

Feel like the refs need to be more clear with the call on field. Still thought he was touched in bounds


Some of you need to get this straight. He absolutely was contacted by the defender on the way to the turf landing in bounds. He WAS NOT GIVEN (correctly so) the yardage after getting up and running. The ref just blew it by ruling he was out of bounds. Jarvis knew he landed in bounds and you can see him sprinting to the middle of the field to hand the ball to the official because he understandably thinks the clock is running. Jameis sees Jarvis running to give the ball to the official and thinks he needs to spike it. You can argue Jameis needs to see if the clock is running, but this is almost entirely on the refs for screwing this up.

Now the second spike is a little more on Jameis. Should have let more time run off.
This post was edited on 9/12/22 at 1:36 pm
Posted by SCLSUMuddogs
Baton Rouge
Member since Feb 2010
8607 posts
Posted on 9/12/22 at 1:39 pm to
I was less concerned about the time and more concerned that it was 3rd down. I thought there was time to at least try a quick slant or something. With Lutz missing one earlier I would have liked a few extra yards, but we won so I don’t care in the end
Posted by Starchild
Member since May 2010
13550 posts
Posted on 9/12/22 at 1:50 pm to
quote:

All of this just makes me realize how much shite is going through the heads of a HC and QB at the end of a game.


Truth! It’s real easy for we fans to sit back and watch the sky cam view of the whole field while eating snacks and drinking to make an accurate call in real time.

Much harder when you’re trying to manage personnel, assignments, get a play call every one is in place for, identify defensive alignment, not get crushed by 300 lb men, all while ensuring enough time is on the clock to give the FG unit a chance and you’re not committing a penalty.
first pageprev pagePage 1 of 2Next pagelast page

Back to top
logoFollow TigerDroppings for LSU Football News
Follow us on X, Facebook and Instagram to get the latest updates on LSU Football and Recruiting.

FacebookXInstagram