OT - Sour Brian Kelly Disputes Late Penalty That Cost Irish Game

Submitted by clarkiefromcanada on

Per the World Wide Leader

Brian Kelly indicates his disagreement with the referees at the conclusion of last evening's 31-27 loss to Florida State.

According to Coach Kelly:

"Actually I have less clarity," Kelly said during his Sunday teleconference. "I guess it was actually called on Will Fuller, not C.J. (Prosise). So [it] just adds more uncertainty as to the final play.

"But again, the play itself, in terms of what we ask our kids to do, it was pretty clear what happened on the play: Florida State blew the coverage and they got rewarded for it. It's unfortunate."

As per the play itself; Kelly saw no issue with the ND player but rather the Florida State player initiating the contact (that saw him blocked 4 yards into the end zone):

"All right, so he was on the point, we were in a bunch situation," Kelly began. "First of all, it's my understanding now that Will Fuller was called for the penalty, not C.J. So C.J.'s job is to get into the end zone and turn around and be a big target. He was immediately grabbed at the line of scrimmage. He's trying to get depth into the line of scrimmage, into the end zone so Corey can clear a path. And so as that contact was being made, it was seen, I guess -- I don't know who saw it as interference -- but you've got two guys that are trying to fight for space. We saw it as such.

Brian Kelly: "We don't coach illegal plays"

Never change Brian Kelly, never change.

http://espn.go.com/college-football/story/_/id/11728483/brian-kelly-not…

johnthesavage

October 19th, 2014 at 11:20 PM ^

I mean, you can watch any college football game this year, and the same thing happens five times. I've never seen it called. You can say it was a penalty, and maybe it was, but like I said.. it is never called. I didn't like seeing it called there, in such a critical moment.IMHO, Notre Dame got robbed.

Blue In NC

October 20th, 2014 at 1:04 PM ^

Yes you have a point but to take this to an extreme, you have no problem with someone being ticketed for jay walking then?  People have a problem with the call because it's hardly ever flagged.  Yes, techically it's a penalty but if you only choose to call it on a game deciding play, then it smells a bit.  I am no Notre Dame fan at all but I can understand Kelly being sour about the call.

mgeauxblu85

October 21st, 2014 at 2:14 AM ^

Note Dame blocked the play like it was a run, wr screen or some other lateral play. Kelly tried to pull a fast one and got a caught he should stop crying and take it like a man. If those receivers run forward turn around and use backs to block the flag isn't thrown. Glad that cheating fuck lost. Return to glory? Nope return to blowing big games. Enjoy the ACC cunts. Maybe your soccer team can enjoy acc championships while your football team never will. Who wants to play for a team that can't be a conference champion/

glewe

October 19th, 2014 at 11:24 PM ^

Every expert says it was a penalty. The calling it is the discretion of the refs...if you ask me, it was questionable at best. But I was disappointed. I wanted ND to win. I mean to hell with them but I wanted them to win to make me feel better about the fact that we out gained them.

yvgeni

October 19th, 2014 at 11:27 PM ^

this same penalty just got called in the Denver/SF sunday night game and Chris Collinsworth commented that he saw the same thing during the ND/FSU game.  his point was that if you at least try to be a bit subtle, turn your head around once contact is made, or at least don't just start pushing the guy down the field, the refs won't call it.

ND did not execute the pick play correctly and got caught.  As they deserved.  End of debate.

BornSinner

October 19th, 2014 at 11:30 PM ^

You never see it called because usually when running pick plays, WRs don't make it so damn obvious. 

It was so obvious on their scoring drive in the 1st half when the refs didn't call it that Jimbo Fisher pointed out that play specifically so the refs could call it next time! 

And lo and behold, Kelly calls the same play, the WRs are too obvious in the pick and don't even act like they want to "catch" the ball... so it got flagged. 

 

Lou Holtz even said the call was warranted and he's the biggest ND homer there is. 

johnthesavage

October 19th, 2014 at 11:54 PM ^

This is fine. But you said yourself it went uncalled earlier in the game. You know, and I know, that it happens, literally in every game, without being called.

If it's a penalty, then freaking call it whenever it happens. Don't no-call it, over and over again, and then call it the one time it decides the game between two top-five teams. That may be the right call, by the book, but it's still 100% horseshit. It wouldn't have been called in South Bend, I promise.

Magnus

October 20th, 2014 at 9:06 AM ^

Are you perfect at your job? If you work at McDonald's, have you ever forgotten to put ketchup on a cheeseburger? If you work at a bank, have you ever forgotten to have someone authorize a check? If you work as a camp counselor, have you ever forgotten the mosquito spray when you went out for a hike?

Since you forgot the ketchup that one time, I guess McDonald's should just forget the ketchup for the rest of the day.

Trebor

October 20th, 2014 at 7:43 AM ^

I liked one of the analogies I saw: It's like speeding. If you've gone past a cop doing 5 over the limit 99 times and he's never pulled you over, you still don't get to be pissed if he pulls you over the 100th time you do it. You broke the rule/law. Sure, you'd like the official to be more consistent, but not calling it one time doesn't mean you can't ever call it.

M-Dog

October 20th, 2014 at 4:54 PM ^

If Notre Dame would just have gone 5 over, they would have been OK.

But they went 35 over, laid on the horn, stuck their heads out the window, threw the finger, grabbed their crotches, and yelled "I got yer justice, right here!" to the trooper on the side of the road.

Kinda deserved to get caught.

 

Blue In NC

October 20th, 2014 at 3:43 PM ^

okay but (1) a pick play almost always affects the play (that's why it's run), and (2) your position ignores many holds that are called away from the play on a run.  I agree that a pick play should not be called on the other side of the field but assuming the ball is caught on the pick side, it should be called whenever it impacts the defense in any way.  And that just isn't the case currently.  On the other hand, there are many holds that are called (or blocks in the back) that never really impact the play.  How many times do the announces call out a player's penalty where "there was no need to commit that penalty" but it's called anyway?

big10football

October 20th, 2014 at 10:52 AM ^

I thought it was an obvious penalty until watching it in the light of Kelly's explanation and now I think he's right.  The db's were locking onto the receivers, not the other way around.  The dbs weren't trying to get to Corey Robinson at all.  That's why both of the FSU dbs were arguing with eachother after the catch, because neither of them covered Robinson.

Wolfman

October 20th, 2014 at 8:22 PM ^

In the first half they ran a well disguised pick that normally doesn't get called. Fisher got the ref's ear as he should.

On the play in question, the offensive player never tried to disengage from the defender. He didn't shield any one,i.e., a pick, but as a receiver he has to run a pattern. He simply can't drive block a db like an OL, and an OL gets only 3 yds on a pass play. If they had run the play like they did in the first half, it might have been called, but I doubt it after Fisher complained. However, they could have run the bunch formation with all receivers running legit routes to clear the area and have the RB merely hit the DE or blitzer and then receive the toss from Golson and walk into the vacated area. Yes, Brian you teach illegal plays, but everyone in football does, so don't feel bad. Just imagine a db riding a receiver from the l.o.s. four yards into the end zone. The flag would have been tossed on about the second step, no argument no matter where the ball was thrown. Obvious offensive interference, but extremely difficult to admit he designed play that way or his receivers failed to execute as instructed which would have been totally contrary to his claim. No win situation for him. Should have left it alone. Great game, however.

carlos spicywiener

October 19th, 2014 at 11:31 PM ^

I would've said the same thing. Beats hearing welll we didn't execute. 

Brian Kelly may be a jerk but Notre Dame has clearly surpassed Michigan with him. They're 5-1, with a narrow loss to FSU on the road. Meanwhile, let's hope Hoke and the gang don't get rocked by 25 this weekend

glewe

October 19th, 2014 at 11:34 PM ^

This will be unlikely to be a popular opinion, but I think the points differential in the State game narrows from last year to this. We're likely to lose, of course, but I think it looks more like 24-17 than 29-6.

PSU and ND are both ranked considerably higher in defensive FEI than MSU; it stands to reason that the current state of our offense can score at least as many points against MSU that we did against PSU, which was 16.

LJ

October 20th, 2014 at 8:42 AM ^

So, the only thing that matters in whether a team/coach has "surpassed" the other is the current record?  If Alabama has a down year next year and we end up with a better record than them, have we surpassed them?

Not saying I disagree with your point that Kelly is better than Hoke.  Just pointing out that this is really stupid logic.