The Denver Broncos fell to 2-1 with their loss to the Baltimore Ravens on Sunday. It was a strange game to say the least. It all started so promisingly. Bradley Chubb got his first full sack, and the special teams blocked a punt that led to a Royce Freeman touchdown. Oh, it was gonna be a good day.
It is only the third game of the #Broncos season and they are 2-1, but this doesn’t feel like one game. On the latest @MileHighReport Radio Podcast, @AdamMalnati16 and I dish out some hard truths. This feels like a bad sequel for #BroncosCountry. https://t.co/KbqPIjStHR— Ian St. Clair (@IanStClair) September 24, 2018
On the ensuing kickoff, there was a ticky tack unnecessary roughness penalty and things got a little hectic from their. The short field led to a Ravens touchdown, but the offense responded. Just eight plays later Emmanuel Sanders was rushing the ball 35 yards on an end around. It was his first career rushing TD and all was right with the world.
And then it wasn’t. As Ian St. Clair and I discussed on the MHR Radio Podcast, the Broncos looked awful in all phases. It was like the first quarter never really happened. After Justin Tucker blasted a 52-yard field goal through the rain, the score was 14-10 by the end of the quarter. Denver would hardly sniff the red zone the rest of the game.
That old 2017 feeling reared its ugly head. By the time the second quarter rolled around, the Broncos looked more like a Trevor Siemian-led team than a one with a true quarterback. Case Keenum was just not good, and that is putting it mildly. Here is the big issue: In the first two weeks of the season Keenum struggled at times, but always found a way to make up for his mistakes. Not so much on the third go around.
The Broncos learned today that Case Keenum is about like Trevor Siemian. Just Trevor Siemian you pay 17 million dollars a season to. What they also learned is that they can't afford mistakes. Like any at all... Mark of a team that isn't there yet.— Teej (@TJCarpenterShow) September 23, 2018
The big issue, as Ian mentioned in the podcast, was timing. His lone interception came late, as the Broncos were trying to get back in the game. In one of the rare occasions where Denver seemed to be in striking distance Keenum failed miserably. The pressure was in his face, and the offensive line wasn’t doing him any favors, but his decision to throw the ball while running backwards was the perfect example of all that is wrong with Keenum.
The Broncos QB isn’t the only one to blame in this befuddling game. The coaching staff continues to confuse the fans with what seems to be poor game-planning skills. Vance Joseph seems to be no better today than he was a year ago. His clock management and decision making skills remind me of a drunk 17-year-old out past curfew. The No Fly Zone is now the Frequent Flyer Zone. There were so many penalties I thought someone was trying to make a yellow quilt. Phillip Lindsay was ejected for throwing a punch? Weird game.
Can we get back to last year's Case Keenum? #Broncos @1043TheFan pic.twitter.com/tTnmB9XC1P— Cecil Lammey (@CecilLammey) September 23, 2018
But the big takeaway from the Broncos Week Three loss to Baltimore has to be about Case Keenum. It is painfully obvious that he is not the savior at QB that John Elway, and all of Broncos Country, thought he would be. Is it an overreaction? Sure, but it’s pretty valid. And with the Kansas City Chiefs putting up points like Clark Griswold hangs Christmas lights, does anyone think Denver’s offense will be able to keep up on Monday Night Football?