I said that it can be good, but I don't think so in this instance. There's no benefit to having it bounce around, the clock doesn't start until someone touches it. Squibbing it there adds a lot more bad that can happen (gets covered by an up man, goes out of bounds, etc.) than any benefit it gives them.Right, a squib kick has a lot of unpredictability which can be good. As I said this should have been reversed in practice multiple times. If there were concerns about placement then they should have mortar kicked. The objective is to run clock.
In a vacuum it is easy to say "they should have stopped them" but the Bills were not stopping Mahomes. The Chiefs moved down the field very easily prior to the Bills last TD. There was nothing to suggest that was going to change. In fact, as soon as the Bills kicked the ball deep I was convince the game was going to OT.
Oh come on. Prior to the 64 yd TD from Tyreek the Chiefs gained 17 yards on their previous 7 plays.
Well the term has a meaning. I already said I would have tried to have a "normal" kickoff that came down inside their 10, but if they would have busted off a long return and kicked a FG people would have been saying that was the wrong choice too. Classic Monday Morning QBing.People are getting lost in the term squib kick. The intent isn't a short kick; rather the intent is to run clock. The ball needed to be kicked to force a return. Whether it was a squib kick (down to teh 20) or mortar kick made little difference as a long as it forced the Chiefs to return it. That would have run a minimum of 6 seconds off the clock.
Bottom line, they should not have played such soft defense and allowed them to gain 44 yards in 10 seconds. It's not like they were super tough throws or catches either, just simple pitch and catch. Pathetic.