I don't think it was overboard at the time because **** the refs.

Refs need to get it right.


Of course the league will send a letter of apologies to the Chiefs for their non call mistake.


I'm not even sure they got that call right from instant replay that the ball crossed the line when the ball carrier fumbled it and Chiefs recovered. Looked like the ball crossed the line but oh well right?

I'm happy for the win. Hope Kelce doesn't get suspended for pointing out Refs incompetence officiating.

He even apologized to the ref after doing so

ESPN http://www.espn.com/blog/nflnation/p...ections-record

Before you settled into your Barcalounger Sunday, two more NFL players had been ejected from games. And then, before the early games were complete, another player had been disqualified.

Add it all up, and NFL officials already have ejected more than twice the number of players as they did during all 17 weeks of the 2015 regular season. The total of 10 disqualifications puts them on pace to set at least a 15-year high and continues a two-pronged effort by the league to restrain what it considers to be unsportsmanlike player behavior.

NFL Ejections Per Season
YEAR EJECTIONS
2016 10*
2015 4
2014 13
2013 6
2012 7
2011 8
2010 5
*Through early Week 9 games
As the chart shows, NFL ejections typically have remained in single digits for a full season. Historically, the short season relative to other sports has made the league reluctant to use the ejection as a deterrent. There have not been more than 13 in any season since at least 2001, which is as far back as the ESPN Stats & Information database goes.

In 2016, however, the NFL turned to a pair of initiatives --- mostly in response to an ugly game last season between the Carolina Panthers and New York Giants. It added a rule that calls for an automatic ejection of players who receive two of a certain type of unsportsmanlike conduct penalties. And it also intensified efforts to make fighting and other non-football acts subject to immediate ejection if on-field officials believe it is warranted.

We saw one of each on Sunday afternoon.

First, referee Jeff Triplette's decision to eject Cleveland Browns center Cam Erving and Dallas Cowboys defensive end David Irving came as the result of a fight after a first-quarter play.

Second, Kansas City Chiefs tight end Travis Kelce was ejected after a fourth-quarter call by referee Gene Steratore for arguing about a penalty call and then throwing a towel at an official. He received separate unsportsmanlike conduct penalties for each, triggering the auto-ejection rule.

Triplette has led the way among NFL officials, accounting for five of the 10 ejections. Referee Bill Vinovich has ejected two players, while John Hussey, Ed Hochuli and Steratore have done it once each.

A fine I can understand but a suspension for a guy that has no history of this stuff is way over the top.

That was immature, but I understand his frustration. You know Gronk gets that call 150 times out of 100.

Yeah. And teams don't get stripped of a 3rd round pick for tampering and players don't get 3 game suspensions for something that happened before the rule changed to make it a suspension either. This is the Chiefs. The league always screws us.

He did do the jacking off gesture. They would assume he has character issues.

That might be the dumbest thing you have ever said.

I love Frasier, but I feel Crane-Cheers>Crane-Frasier


Kelce was 100% right to be furious, 100% wrong to give the refs a chance to make these calls. If the game was out of hand, fine, make a statement. But it cost us a chance at a TD and almost helped cost us a game.

<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">I apologize to everyone that had to witness my actions on the field today... it was unprofessional and unsportsmanlike...</p>&mdash; Travis Kelce (@tkelce) <a href="https://twitter.com/tkelce/status/795411111407480833">November 6, 2016</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>

<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">Depends what type of message the league wants to send. <a href="https://t.co/8TJbbNUWqh">https://t.co/8TJbbNUWqh</a></p>&mdash; Nick Jacobs (@Jacobs71) <a href="https://twitter.com/Jacobs71/status/795411233302347777">November 6, 2016</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>

<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">A missed call is just that... missed. No matter how much frustration builds on the field, the refs don&#39;t deserve that kind of response.</p>&mdash; Travis Kelce (@tkelce) <a href="https://twitter.com/tkelce/status/795411836061487106">November 6, 2016</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>

Well his Twitter response is opposite of what I thought he'd say.

And that's a good thing.

I figure he is just trying to get out in front of this thing so that maybe the league slaps him on the wrist instead of up side the head.

So it looked like he was sarcastically flagging the refs for being shitty. It's funny, but you know they aren't going to put up with that.

Well that's a smart move from a guy who I thought would run his mouth post game and make this worse. He's right. It was a missed call but he also needs to know the game. We almost lost the game and that play was a big reason.