Roadtrip635
Well-Known Member
- Messages
- 14,758
- Reaction score
- 28,034
Play clock is ticking, but the game clock is not. It's still not a hurry-up situation though.No it was not.
Play clock is ticking, but the game clock is not. It's still not a hurry-up situation though.No it was not.
Detroit also could have got the reporting player correct too by letting the officials know it was 68 who was eligible when he announced 70 was for the world to hear on the PA system. They did not, or chose not to.When it happened the announcers immediately began examining the chain of events. Troy very clearly said clock was stopped when the Lions players were meeting w ref. Sure at some point the refs started the play clock but it wasn't a factor in the ref being able to get the reporting player correct.
That all sounds good in theory. When was the announcement made in regard to the play clock? What would a ref do? Stop the play clock & communicate everything to both sides? Or result in delay of game which would negate the whole effort?Detroit also could have got the reporting player correct too by letting the officials know it was 68 who was eligible when he announced 70 was for the world to hear on the PA system. They did not, or chose not to.
He was very clear in the post game that 68 reported. Didn't mention the announcement.What is Jared Goff's position in this? How can he justify throwing to 68 when he had to hear number 70 called.