The Chicago Bears’ Justin Fields entered Sunday’s game with the Atlanta Falcons as the arguably hottest player in pro football. Led by Fields’ unique multifaceted talents, the Bears’ offense had scored over 120 points in their last four games. But aside from a few key players, Chicago has very few other game-changing talents on offense — especially up front on the offensive line. That means asking Fields to play superhero every single week probably wasn’t always going to be the best idea.
In the final minutes of a 27-24 Falcons win, we saw this come to fruition in an awful way for the Chicago quarterback and offensive coordinator Luke Getsy. With the Bears looking to at least tie matters up after the two-minute warning in the fourth quarter, Chicago gave Fields a now trademark designed run on first down. It resulted in just one yard but even worse — Fields appeared to seriously hurt his left shoulder.
Rather than protect Fields and go back to the passing game on second down (which, to be fair, still kind of puts him in danger behind a terrible line), Getsy called another designed run. It went for a solid four yards, but it was clear that the OC got a little overzealous with his young quarterback’s legs when he probably should’ve been protecting his health on a team already well out of playoff contention.
After the game, Fields acknowledged that the first designed run was where he hurt his shoulder:
Justin Fields said he did hurt his shoulder on the first play of the last drive. pic.twitter.com/uVAXaRp9yh
— Nicholas Moreano (@NicholasMoreano) November 20, 2022
Naturally, folks who realized the Bears had unleashed a real gem in Fields — one of the league’s more exciting young quarterbacks — weren’t happy with Getsy’s questionable play-calling. While the status of his injury is unclear, the Chicago signal caller seems likely to miss at least some time before the end of the season.
NFL fans ripped Getsy for his questionable play-calling that might have led to Fields' injury
I have no clue what Luke Getsy is trying to accomplish with these play calls knowing Fields isn’t at 100%. #Bears
— Aaron Leming (@AaronLemingNFL) November 20, 2022
The offense scoring 33, 29, 32, 30, and 24 in consecutive weeks outweighs some baffling play calls late. I'll stay impressed with Luke Getsy given the talent. But that was nonsensical and risky and if he robs us of Justin Fields next week or longer it'll be tough to get over.
— Danny Parkins (@DannyParkins) November 20, 2022
Luke Getsy was calling plays like it was the playoffs. You do not need *that many* designed runs in what's really a meaningless game, especially when your stud QB is clearly suffering from shoulder and hamstring pain.
Can we get the short passing game going? Please?
— Ricky O'Donnell (@SBN_Ricky) November 20, 2022
re-watching the Bears final drive
Fields appeared to injure his left shoulder on the opening play, fell on it out of bounds on a designed run with 1:45 left
very slow to get up
Luke Getsy immediately called another designed run
stupid playcalling
— Josh Norris (@JoshNorris) November 20, 2022
Fields confirms he got hurt on the first play of the final drive. Luke Getsy then proceeded to call another designed QB run. Inexcusable. https://t.co/fvDxN4S9b8
— Harrison Graham (@HGrahamNFL) November 20, 2022
I don’t know what Luke Getsy was doing
— VP of Wu Tang Financial (@BarbChairScott) November 20, 2022
Luke Getsy needs to stop abusing Justin’s legs.
WHY ARE YOU DOING DESIGNED RUNS IN THE 2 MINUTE DRILL.
— Alberto Castillo Jr (@AlbertoJr1114) November 20, 2022
Ya know what, after that play call if any teams want Luke Getsy they can have him. Your QB is injured and you run two designed QB runs?
— Chicago Football Connection (@CFCBears) November 20, 2022
With 1:47 to go, Luke Getsy dials up a designed QB run from #DaBears OWN 25.
Then, after #JustinFields is clearly in pain, they RUN IT AGAIN?!
Horrible. Protect your QB!
— Jon Zaghloul (@JonZSports) November 20, 2022
1st down: Justin Fields takes a designed run, seems to re-injure his left shoulder; Bears forced to use a timeout.
2nd down: Fields scrambles, takes a hit towards the head, doesn't get a penalty flag.
3rd down: Fields appears to be in pain and misfires on a pick.
Yikes.
— Chris Emma (@CEmma670) November 20, 2022
