The defender is trailing your WR with 4.3 speed, the defender reaches out and grabs him, the ball falls about 4 yards in front of your WR in-bounds and refs pick up flag because pass was "uncatchable". Hell. I might have been able to get a hand on it if the defender didn't pull me back.

If folks know me, they know *I'm not one to "blame refs" and at the end of the day; it didn't matter, but a call like that HAS to get the crew downgraded.

Yes, that was a headscratcher without being grabbed by the defender, Chase is easily catching that ball.
The holding call on Volson was BS too. His hands were inside the framework of the defender's shoulder pads and the jersey was never stretched out...

The PI on the Bengals that led to a Browns TD was also BS

If you go back and watch the replay, you can see Chase talk shit to the ref who didn't throw the flag. That ref immediately runs over to the ref who threw the flag and I bet told him to pick it up. It was clear as day.

I swear I don't know what PI is these days,

Hmm. I know I have seen PI called the last two years where the ball landed outside the white sideline or beyond the end zone.. so much so that I wondered if "catchable" was still a requirement.

(10-20-2024, 06:23 PM)bfine32 Wrote: The defender is trailing your WR with 4.3 speed, the defender reaches out and grabs him, the ball falls about 4 yards in front of your WR in-bounds and refs pick up flag because pass was "uncatchable". Hell. I might have been able to get a hand on it if the defender didn't pull me back.

If folks know me, they know *I'm not one to "blame refs" and at the end of the day; it didn't matter, but a call like that HAS to get the crew downgraded.

Sounds pretty bad. Need to see the game on Gamepass once they get their shit together. I know you hardly ever blame the zebras.

What's even worse is there was a play in the KC/SF game very similar to this except Purdy pass was more uncatchable and DPI was called. If we would have got the DPI call i wouldn't have cared as much about this one.

(10-20-2024, 08:56 PM)cinci4life Wrote: What's even worse is there was a play in the KC/SF game very similar to this except Purdy pass was more uncatchable and DPI was called. If we would have got the DPI call i wouldn't have cared as much about this one.

I saw that, the 49ers were just owned in that game and even got calls going their way. The Chiefs have no respect for them, namely Purdy.

I’ve seen far worse throws deemed “catchable” before. These referees are just grossly inept, which is really on the NFL at this point since they’re not even full-time employees

(10-20-2024, 08:55 PM)Nate (formerly eliminate08) Wrote: Sounds pretty bad. Need to see the game on Gamepass once they get their shit together. I know you hardly ever blame the zebras.

Refs throw a flag for pass interference. They pick up the flag saying the ball was uncatchable. Hard to say if Chase would've gotten there but it would've been close. #CINvsCLE pic.twitter.com/H8m5pQ0XQr

— Rate the Refs App (@Rate_the_Refs) October 20, 2024

I’ve seen the ball go out of bounds and the flag upheld. .

Not catchable now has to be headed to the upper decks, not landing five yards away because the defender slowed him down. That was most likely a TD.

The Browns have unlocked a new kind of defense. All passes are uncatchable if the receiver is on the ground!

I may be in the minority here but I didnt think it was catchable either. While he was grabbed(and not really that aggressively) IMO i dont think he had a chance in hell in catching that. I think it was a good no call.

(10-20-2024, 06:23 PM)bfine32 Wrote: The defender is trailing your WR with 4.3 speed, the defender reaches out and grabs him, the ball falls about 4 yards in front of your WR in-bounds and refs pick up flag because pass was "uncatchable". Hell. I might have been able to get a hand on it if the defender didn't pull me back.

If folks know me, they know *I'm not one to "blame refs" and at the end of the day; it didn't matter, but a call like that HAS to get the crew downgraded.

I, too, found their reasoning to be absurd. Every ball would be uncatchable if the DB was allowed to just hold the guy running by him.

I also hated the PI call in the endzone on Turner where the WR initiates contact & grabs/shoves him to get position. That was a goofy call to me since the WR stuck his arm out to shove Turner 1st.

(10-20-2024, 10:58 PM)Browns Town Bengal Wrote: I may be in the minority here but I didnt think it was catchable either. While he was grabbed(and not really that aggressively) IMO i dont think he had a chance in hell in catching that. I think it was a good no call.

Unless you see all the other passes that are not deemed uncatchable. That ball landed five yards from him.

I didn't see live, and the tweet posted above is kind of blurry. Seems like the ball may have been sailing past far past Chase when the grab happened. Don't think he catchs that even if he was alone. A bit overthrown. That said, I say there was not enough to pick up the flag if you threw it.

I saw this play live, it did look like Chase slowed up (probably from being impeded).

My conclusion at the game was the lack of DPI was on Burrow because he threw it just literally a foot too far.

(10-20-2024, 10:58 PM)Browns Town Bengal Wrote: I may be in the minority here but I didnt think it was catchable either.  While he was grabbed(and not really that aggressively) IMO i dont think he had a chance in hell in catching that.  I think it was a good no call.

The NFL rulebook does not define the term "uncatchable,", however it has typically been invoked when the ball is out of the field of play or way above the receiver's head. In this case, is it not likely that Chase would have caught it? Perhaps. But the ball landed in play and within approximately 5 yards of where the receiver ended up at the time the ball hit the ground. I think 99% of receivers get that call.

Unfortunately for us, Chase seems to have gained a bit of a reputation with the refs and I think it negatively affects how many calls he gets in his favor.