| 142 Beiträge - Gelegenheitsposter
|
|
|
elers Twitter had a lot of love to show for Kansas City Chiefs quarterback Patrick Mahomes Sunday http://www.thechiefsfootballauthentic.com/dustin-c...-authen tic , and who can blame them? Mahomes finished the day 23 of 28 for 322 yards and six touchdowns, tying the franchise record for most touchdowns in a game and breaking the NFL record for most touchdowns in the first two games of a season.The first tweet, from AP lobbyist Peter Schrager, is a doozy:A game like that calls for some updated QB rankings:Heâs even getting compared to some of the NFL greats at just 22 years old:And...God?Geoff, Geoff. There are children present:Flames were a common theme:Mahomes has entered a league of his own:And is living up to all the hype:Itâs like a sweet melody, and everybody is singing along:There may still be some questions on defense, but, with Mahomes leading the offense, none of it matters:WARNING: Itâs unknown whether or not his phone will blow up due to the high volume of tweets, texts, emails, airdrops, DMâs and more heâs probably receiving right now:Wait. Mahomes slept on a twin bed last night?The idea that Mahomes will be a Pro Football Hall of Famer doesnât seem too far off:As far as fantasy goes, some people are feeling really good right now:Others, not so much: More than a few Kansas City Chiefs fans were scratching their heads at this one.Just before the end of the first half in Sundayâs 37-21 victory over the Cleveland Browns, the Chiefs were penalized for intentional grounding when Patrick Mahomes spiked the ball the stop the clock.At first glance, this defied all common sense.Weâve seen it hundreds of times.The quarterback spikes the ball.The clock stops because there are less than five minutes remaining in the half, and itâs an incomplete pass.The team gives up a down in exchange for stopping the clock.So how could this have been intentional grounding?If you were watching on TV Womens Sammy Watkins Jersey , this was further confused by the commentators initially thinking that the penalty was called because Mahomes snapped the ball before the officials were ready.Nor did it help that nobody in the booth had ever seen anything like it.And if you were there in person, youâre probably still trying to figure it out.So letâs break it down.With 14 seconds remaining in the half, the Chiefs are at their own 35-yard line.They have one timeout left.The Chiefsâ intent is clear: leading 21-15, they want to get at least a field goal on the board before the half.So if possible, they need to hang on to their last timeout, so they can use it to stop the clock and get the field goal team on the field.Mahomes completes a 23-yard pass to Chris Conley near the right hash mark at the Cleveland 42. From that spot, it will be a 59-yard field goal for Harrison Butker.Conley is tackled on the field, and there are just nine seconds left.Normally, the Chiefs would use their final timeout to stop the clock, and then decide if they should try a field goal from there, or run a play to the sideline and get out of bounds, getting a few yards closer to the goal posts for the try.But the clock is already stopped because there is a flag on the play.To their credit, the Chiefs realize that Clevelandâs Myles Garrett has jumped offsides, and they donât need to use their timeout; Garrett has essentially gifted them a timeout.The penalty is declined, and the Chiefs line up for the next play.The play clock is running, but the game clock is not; it wonât start until the ball is snapped.When the ball is snapped, Mahomes spikes the ball, giving up the down and taking one second off the clock. Thereâs no way to characterize this as anything but a mental mistake by Mahomes.Thereâs no need to stop the game clock because it is already stopped.So it was clearly a mistake.But was it intentional grounding?No.And yes.The NFL rulebook says that it is intentional grounding to throw a pass to the ground with no obvious receiver nearby when a quarterback is âfacing an imminent loss of yardage because of pressure from the defense.âObviously http://www.thechiefsfootballauthentic.com/laurent-...-authen tic , that wasnât the case here.But the rulebook also says that a quarterback may only spike the ball âto stop a running game clock.âSo while the spike wasnât intentional grounding per se, it was still in violation of the rules.And as sometimes happens in these situations â where referees have to call some kind of penalty on a play that falls in a gray area between two rules â they picked one to enforce.And that penalty calls for 10 yards, a loss of down â and when it occurs past the two-minute warning, a 10-second runoff.It would have ended the half right then and there, but Andy Reid wisely reminded the officials that the Chiefs had the option to give up a timeout instead of the 10 seconds.So play continued.Photo by Jason Miller/Getty ImagesStill, in the immediate aftermath, it mystified Chiefs coach Andy Reid.âListen, I take pride in knowing the rules, and this one must have been in the archives,â he said after the game. âWhoever created it, I need to talk to him. Iâm not sure I understand the logic behind it. [Line Judge] Mark [Steinkerchner] would know it, heâs been around, he did our Super Bowl game a long time ago, and heâs a pretty sharp guy.But he pulled that one out of left field on me.âBut despite what you may have heard, it has happened before.In a 2016 Monday Night Football game between the Buffalo Bills and Seattle Seahawks, Buffalo spiked the ball because their field goal kicker Dan Carpenter had been injured on a field goal attempt.Since the injury occurred with less than two minutes remaining, the Bills were charged with an injury timeout, and by rule Youth Travis Kelce Jersey , Carpenter had to leave the field for at least one play.So the Bills spiked the ball on a stopped clock, so that Carpenter could come back on the field and try again.No intentional grounding penalty was called on the Bills.But itâs easy to see why there should have been some kind of penalty, because the Bills essentially skirted the rules.It would be reasonable to think that after the 2016 game, NFL referees were instructed that in such a situation, teams should be penalized.So if Sunday's game was a situation where the referees just picked a penalty to enforce, they probably did it at the direction of the league.We could argue that the NFL should have an âimpermissible spikeâ rule with a different penalty to be assessed â maybe just five yards, for example.Or we could argue that it shouldnât be a penalty at all.If teams make this mistake, theyâre already giving up a down and a second of game clock time in a situation where â by definition â both of those are critical losses.But as we see in the case of the 2016 game, there is potential for abuse in a spike play.For example... if thereâs no penalty for a spike when the game clock is stopped, what would stop a quarterback -- with no timeouts available -- from spiking the ball when he sees that the opposing defense is lined up in a way that will crush the offensive play thatâs been called?Thatâs just one example that occurs to me.There are undoubtedly others.In the final analysis, Mahomes just made a mistake.As it turned out, it wasnât a very costly one.The Chiefs still won the game easily.And Mahomes is unlikely to ever make that mistake again.Note: After this article was published, I received an e-mail from a reader who pointed out a reference in the casebook section of the official 2018 NFL rules. The casebook has 93 pages of examples to help officials know how to interpret the rules in specific game situations. Think of it this way: the NFL rulebook is the law (voted on by the owners), but the casebook shows how the NFLâs head of officiating thinks the law should be interpreted â the same way Congress writes laws, and the Supreme Court decides how those laws should be interpreted.Hereâs the reference, which is A.R. 8.90 on page 38 of the casebook:You can check it out for yourself here:2018 NFL Rule BookMany thanks to Neil for providing this reference.In his e-mail, Neil also said this:
|
Usermap
co.uk/url?q=http://128.199.79.6/ 
Seitenanfang: