Falcons fans are unhappy waking up on Monday morning after a controversial ending to "Sunday Night Football."
Kirk Cousins and Atlanta were once again in the bright lights of prime-time football. After pulling off a stunning comeback in Week 2 over the Eagles on "Monday Night Football," the Falcons were unable to recreate the same magic against Patrick Mahomes and the Chiefs, falling 22-17 on Sunday night.
There was a play late in the game where it appeared as though Falcons tight end Kyle Pitts was on the receiving end of pass interference. On third down, Cousins attempted to hit Pitts in the end zone when early contact occurred, resulting in an incompletion.
However, there was no flag thrown on the play, leaving Pitts, Cousins and the rest of the Atlanta brigade steaming.
So why was no flag thrown on the play? The officials gave their side of the story in the aftermath of "Sunday Night Football."
MORE: Raheem Morris declines to comment on pass interference no-call
Why Chiefs pass interference wasn't called vs. Falcons
With 4:12 left in regulation and the Falcons down 22-17, Cousins and Co. were in the red zone, threatening to score. On third-and-5 from the Kansas City 5-yard line, Cousins took a shot at the end zone, targeting Pitts in the middle.
Chiefs safety Bryan Cook was covering Pitts on the play. The smaller defensive player seemed to engage in quite a bit of contact before the football was in Pitts' area, but no flag was thrown on the play.
Ultimately, the tight end was unable to come up with the catch, resulting in a fourth down.
Refs let the Chiefs get away with a lot of contact on this pass to Pitts. Falcons end up turning it over on downs. #KCvsATL pic.twitter.com/rSFnM2tIb8
— Rate the Refs App (@Rate_the_Refs) September 23, 2024
MORE: Chiefs fans, fantasy owners express concern for Travis Kelce
Cousins attempted to hit Drake London on the next play, but the two did not connect on the throw, resulting in a turnover on downs.
After the game, referee Tra Blank explained to the Atlanta Journal-Constitution what the officials thought process was on the play and why there was no call on the field.
"That is a real-time call that officials have to make a judgment on," Blank said, who was the official for the pool report. "From the angle that they had at the time, they did not feel that there was a foul committed."
Since pass interference is non-reviewable by replay, the officials could not go to the footage to see the play from another angle that may have shown the contact before the ball reached Pitts.
The Falcons went on to get another possession deep into Kansas City territory in the final minutes of the game, but they once again were stumped by the Chiefs defense, leading to the loss.
SN's NFL HQ: Live NFL scores | Updated NFL standings | Full NFL schedule
While speaking to the media after the defeat, Falcons head coach Raheem Morris declined to comment on the no-call for his own best interests.
"I like my money," Morris said, referencing a potential fine. "I'm smart enough to be aware not to dunk on officials. They made the call, or didn't make the call, it is what it is. We had a chance to win on the last play."
Full quote:
— Austin (@AustinPlanet) September 23, 2024
"I like my money. I'm smart enough to be aware not to dunk on officials. They made the call, or didn't make the call, it is what it is. We had a chance to win on the last play."
The Falcons head coach also pointed out that his team had a chance to win. Atlanta had another possession after the missed call in the end zone, and the group was the beneficiary of three Chiefs penalties, including a pass interference and a horse-collar tackle.
Ultimately, the Chiefs defense did enough to keep the Falcons out of the end zone on multiple possessions, hanging on for the win. However, the missed pass interference call is going to leave a bitter taste in the mouths of the Atlanta faithful.
