Jax Ulbrich, the 21-year-old son of Falcons defensive coordinator Jeff Ulbrich, has apologised after admitting he prank-called Shedeur Sanders during the 2025 NFL Draft, disrupting one of the most important moments of Sanders' young career.
In a statement posted on Instagram on Sunday, April 27, Jax described his actions as a “tremendous mistake” and revealed he personally apologised to Sanders, the newly drafted Cleveland Browns quarterback.
“On Friday night I made a tremendous mistake," Jax wrote.
"Shedeur, what I did was completely inexcusable, embarrassing and shameful. I’m so sorry I took away from your moment, it was selfish and childish. I made a terrible mistake and messed with that moment.”
The prank, which occurred during the second day of the draft, involved Jax impersonating New Orleans Saints general manager Mickey Loomis, falsely telling Sanders he would be selected soon.
In a now-viral video, a confused Sanders responds, “What does that mean?”
Fox Sports reported that Sanders had taken measures to avoid prank calls, including getting a new phone number distributed only to NFL executives.
However, according to a statement by the Falcons, Jax accessed Sanders' private number via his father’s open iPad while visiting home.
The Falcons were quick to distance themselves, confirming Jeff Ulbrich had no knowledge of the prank or the data breach.
"The Atlanta Falcons do not condone this behaviour and send our sincere apologies to Shedeur Sanders and his family," the team said in a statement.
Despite the incident, Sanders took the high road during a post-draft press conference, telling reporters, "It didn't really have an impact on me... Of course, it was a childish act, but everybody does childish things here and there."
Shedeur Sanders, who starred at Colorado under the coaching of his father Deion Sanders, was eventually selected in the fifth round, 144th overall, by the Cleveland Browns.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ