Travis Kelce reveals why Secret Service agents at the White House were not happy with him

Kelce on White House visit: 'Secret Service told me they'd tase me if I approached the podium.'


Poppy Agha June 06, 2024
Courtesy: AFP

Travis Kelce, the Kansas City Chiefs tight end, revealed a startling encounter with the Secret Service during the team's recent visit to the White House to celebrate their Super Bowl victory. During a speech on the White House lawn, President Joe Biden invited Kelce to the podium, prompting the NFL star to recount a humorous yet serious warning he received from security.

"My fellow Americans, it's nice to see you all yet again. I'm not going to lie, President Biden, they told me if I came up here, I'd get tased so I'm going back to my spot alright," Kelce stated. This comment referred back to a previous attempt to speak, which was halted by his teammate, Patrick Mahomes. 

While many took his remark as a joke, Kelce confirmed on his and Jason Kelce's 'New Heights' podcast that the warning was genuine.

"That's real, the Secret Service that was all over the White House, um, they weren't too happy with me. They weren't too happy with me on my second time visiting," he explained. 

Kelce detailed how, upon his arrival with a valid passport in lieu of an expired ID like before, he was met by several agents who sternly advised him against approaching the podium.

"When I walked in we had about four or five Secret Service members come up to me and tell me, 'You know if you go up to that podium we are authorized to tase you," he shared on the podcast.

The interaction left an indelible mark on Kelce, who felt the weight of the taser's presence even as he briefly stood at the podium by Biden's side. 

Despite the intimidating warning, the visit was marked by lighter moments, including photo opportunities with the president, who held a Chiefs jersey emblazoned with the number 46.

 

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ