From Comcast SportsNetCHICAGO (AP) -- Chicago Bears quarterback Jay Cutler acknowledged Tuesday that he was wrong to shove teammate J'Marcus Webb on the sideline during the loss at Green Bay last week.He has no second thoughts about yelling at him, however."I probably shouldn't have bumped him, I'll go with that," Cutler told WMVP-AM in Chicago. "As far as me yelling at him and trying to get him going in the game, I don't regret that. I shouldn't have bumped him, I'll stick to that."Cutler drew widespread attention for berating and bumping Webb, the starting left tackle, on the sideline and for making some pointed postgame comments after the 23-10 loss to the Packers on Thursday. National analysts such as Terry Bradshaw and Bill Cowher spoke out, and so did Bears defensive back D.J. Moore this week, saying the quarterback was wrong to go after Webb like that.Cutler looked great in a season-opening blowout over Indianapolis, finding new receiver Brandon Marshall often, but it was a different story last week. He threw four interceptions and got sacked seven times, an all-too-familiar sight for a quarterback who took a beating the previous two years under former offensive coordinator Mike Martz. His tirade against Webb and lack of remorse he showed in the postgame interview brought back questions about his leadership and demeanor.As for why the outburst happened at that particular moment, Cutler wasn't sure."I can't put a definite reason why it happened," he said. "It happened. It's an emotional game. I put a lot into playing quarterback, and I take it seriously. It's just one of the things that happened during the game. Since then, we've talked about it, and it's really behind us."Cutler discussed the incident "with the powers that be" and with the linemen individually. Did he apologize to Webb?"That's between me and J'Marcus," Cutler said. "We've talked. It's in the past. We're moving on. He's our left tackle. He's my left tackle, and I expect him each and every week to play at a certain level. And I think he expects himself to play that way, too."Webb will certainly have to do better, considering Clay Matthews went off for 312 sacks, but he wasn't the only Bears player who had problems. Marshall had just two catches and dropped a potential touchdown pass, yet Cutler consoled him after that.So why didn't Webb get similar treatment?"Everyone's different," Cutler said. "Everyone reacts differently. I've known Brandon for a long time. I've played a lot of football with Brandon (in Denver). I know what Brandon's capable of at a high level, and I know no one was more disappointed in that stadium or as a Bears fan than Brandon Marshall for dropping that touchdown. I know that genuinely in my heart."He also said the offense as a whole needs to improve, including himself. But if there are any lingering issues surrounding the incident, Cutler doesn't see any."We went out there (for practice on Monday), started preparing for St. Louis, had a crisp practice, put in some good stuff," he said. "I think in our building internally, we kind of circle the wagons. I don't care if you win, you lose, there's going to be criticism. There's always going to be something that someone's picking on, someone's trying to make a story out of."He was asked if he can lead the Bears. To that, Cutler said, "Without a doubt. Without a doubt."He was also asked about Moore's comments."He's entitled to his opinion and whatever he wants to say is up to him," Cutler said.Cutler disputed the idea that he lost his composure against the Packers, saying, mistakes by him and other players derailed the Bears. He said he knew what he was doing "as we were calling plays, and everything was going smoothly."In fact, he insisted he wasn't rattled."I'm actually proud of that game," he said. "I thought I fought. I thought I competed hard, made a few errant throws. But whenever we got what we were looking for, I put the ball on the money for the most part."
KANSAS CITY, Mo. – Derek Carr has made 44 starts as Raiders quarterback. They all haven’t been pretty. Most of them have, but the 25-year has hit a few bumps during what is generally considered a sterling start to his career.
He threw some costly interceptions in 2015, and was learning on the job as a rookie. He’s been nothing short of awesome this season. Until Thursday night, certainly one of his worst as a professional.
Ponder this stat line: 17-for-41, 117 passing yards, no touchdowns, no picks. His 49.1 passer rating was career low.
That’s un-Carr-like, to say the least.
While his receivers dropped four passes, there were many others not in the tally that should’ve been caught. Special teams made some costly mistakes and the defense had some first-half lapses.
Carr wasn’t afraid to say quarterback play had a huge impact on a 21-13 loss to the Kansas City Chiefs, a nationally televised game that dropped the Raiders to 10-3 and into second-place in the AFC West.
“It was definitely a bad night, no way of getting around that,” Carr said. “I hate to have a bad night coming on this one, out of all the games we’ve had. Obviously, we didn’t do enough.
“I feel very responsible for that because of being the leader of the offense and the team. I feel sick to my stomach when we put something like that out there on film. It hurts, I can promise you that. I put too much time into this to go do something like that.”
Carr didn’t want to make excuses after this loss. He didn’t blame his right pinky, which he dislocated in two places against Carolina, which still causes discomfort.
“It definitely wasn’t the finger’s fault,” Carr said.
He didn’t blame frigid temperatures, or whether that had an effect on his grip or his ailing digit. It certainly might have, but the Raiders quarterback never plays the blame game.
Despite the passing game’s struggles, Latavius Murray ran well and the defense clamped down in the second half. That kept the Raiders down one score most of the second half, but they couldn’t cross the goal line.
The Raiders had more than eight minutes to put a game-trying drive together, but stalled at the Kansas City 19-yard line and turned it over on downs.
Carr put one touchdown drive together, late in the first half that made it 21-10. The defense forced two turnovers in the red zone early in the third quarter, but the Raiders only got three points from those opportunities.
That, much like everything else that happened in the passing game, was uncharacteristic of an explosive unit.
“Everything about tonight was unusual, to be honest,” Carr said. “To have our defense step up for us and make plays, and for us to go out there and not execute, do things we don’t do… That’s why it’s frustrating. That why I promise you I’m not worried.
“We played awful. It wasn’t good enough, but I’m not worried because I know the guys in the locker room. I’m not worried one bit, but it just sucks. We have to take it. We have to take the punch, but I’m not worried. I think we’re going to bounce back.”
So the Oakland Raiders are good, but not magical, let alone soaked in destiny. So they can make every game a hard slog for the opponent, but they are not invulnerable. So they can be inefficient, and too sure of themselves, and terribly wasteful when they’re cold.
In other words, they are part of the National Football League – no longer too good to be true.
Their performance against the Chiefs in Kansas City was a pyramid of blown opportunities, opportunities made necessary by a terrible start. A week ago, against a borderline playoff team, they could get away with it. Thursday, on hostile ground, against a team that has lost three of its previous 23 regular season games and has a defense that specializes in standing on your chest until you whistle Yankee Doodle through your navel, they couldn’t.
The result of the 21-13 loss in a game with 12 more points than degrees of temperature is that the Raiders are now the fifth-best team in the American Football Conference rather than the first-best team with four more chances to change that position.
In other words, Thursday’s defeat only provided this much wisdom: The Raiders are a good team vulnerable to other good teams with an iron-plated sense of purpose, stubborn defenses that can apply and maintain a chokehold for hours on end, and offenses that don’t feel compelled to imitate Oakland’s offense by getting into a shootout.
And also this: There is nothing that would necessarily prevent them from beating the Chiefs in case of a third match, even though Kansas City held them to fewer points in two games than they scored in every other game save one. They are still, as the pedants say, “in the argument.”
But they have flaws to be exposed against the right team in the right situation. Kansas City has been that team twice, and New England probably is, but there the list probably stops. Nobody in the AFC North or South seems terribly capable of matching them in neutral conditions, but here’s the other bone spur:
The playoffs are not about neutral conditions.
The Raiders have come a long way in what most people think is a long time, but in fact in terms of team construction, you can throw out everything before 2013, and almost everything before 2015. They are just now getting a full understanding of the hardest part of becoming a Super Bowl contender – the other Super Bowl contenders.
Yes, Kansas City has an indifferent playoff history under Andy Reid, but it is clear that under current conditions the Chiefs are serious players. And while we have no link to how the Raiders would fare against new England, we are pretty sure that they wouldn’t want to play the second weekend of January arse-deep in snow in Foxborough.
The point? Now they get how hard this contender stuff really is. They could not have learned that lesson any other way – not anyone they’ve played yet save Kansas City.
Their next lessons come in Weeks 16 and 17, when they face the frantically desperate Indianapolis Colts in Oakland and then the Broncos in Denver the week after. Desperate teams can be very difficult indeed, especially to teams that are safe and dry and home, playoff-wise.
And then there are the actual playoffs, which if they were played today would have the Raiders traveling to Houston for a very winnable game against the stultifying Texans. The week after, they could be either in Kansas City again or in New England, getting a gut full of visiting field disadvantage.
But as a learning experience, the Raiders may have come out very well indeed. They now know in very real and personal ways the real difference between where they think they should be and where they are, as well as how many ways this can go terribly wrong between now and then.
And also how well it can go, if they learn what the Chiefs taught them again Thursday.