BYU - Washington

[IceGator8]

I was at the game and knew instantly that there would be a flag. The ball went 30-40 feet in th air. When Locker threw it he had enough time to high five, chest bump, and attempt another high five before the ball came back down and hit him.

Seriously, the throw was high enough it gets called 100 times out of 100. Locker as a team leader needs to know this stuff and not commit the infraction.

[Camron Rust]

Originally Posted by IceGator8

I was at the game and knew instantly that there would be a flag. The ball went 30-40 feet in th air. When Locker threw it he had enough time to high five, chest bump, and attempt another high five before the ball came back down and hit him.

Seriously, the throw was high enough it gets called 100 times out of 100. Locker as a team leader needs to know this stuff and not commit the infraction.

Exactly. That is completely clear on the video.

I mentally counted approximately 3, maybe 4 seconds, between the release and when it hit him in the head. 3 seconds equates to 36 feet. 4 seconds, 64 feet. Even it my count was fast and it was really only 2 seconds, it would have been 16 feet above his head. If that is not high, I don't know what is. Simply put, Locker was guilty of an act that drew the flag. Whether or not you like the fact that the official called it, Locker unnecessarily took that risk by throwing the ball.

And even more interesting was the fact that the PAT was blocked, not missed. It's not like the extra distance is what made the block possible. Kicking from the 35 is a pretty basic FG distance. The PAT would have been blocked even in absence of the penalty. So, the penalty is essentially irrelvant.

[JugglingReferee]

Originally Posted by Camron Rust

Exactly. That is completely clear on the video.

I mentally counted approximately 3, maybe 4 seconds, between the release and when it hit him in the head. 3 seconds equates to 36 feet. 4 seconds, 64 feet. Even it my count was fast and it was really only 2 seconds, it would have been 16 feet above his head. If that is not high, I don't know what is. Simply put, Locker was guilty of an act that drew the flag. Whether or not you like the fact that the official called it, Locker unnecessarily took that risk by throwing the ball.

And even more interesting was the fact that the PAT was blocked, not missed. It's not like the extra distance is what made the block possible. Kicking from the 35 is a pretty basic FG distance. The PAT would have been blocked even in absence of the penalty. So, the penalty is essentially irrelvant.

Camron,

I see your formula: 4•t², but how did derive that formula? My physics days are more behind me than I thought, or it truly is 7am on Sunday morning...

To the OP: good call. The officials hands were tied! As for the rule, I don't care either way.

[mu4scott]

Game Management.

[TonyT]

Did you hear him say the official probably cost Ty Willingham his job. How about working on your kicking game and having control of your players so these penalties don't happen. The official didn't throw the ball up in the air. Which Mark May says "HE DIDN"T THROW IT THAT HIGH" The guy is a IDIOT!!!!!

[kdf5]

This whole ESPN mess is just a very small example of what's wrong in our country today. Some old bag spills a cup of coffee between her legs and it's McDonald's fault for making hot coffee. This kid commits a foul and it's the officials fault for costing the head coach his job. Someone step up and say the kid screwed up and we'll be on our way to a better world.

[Camron Rust]

Originally Posted by JugglingReferee

Camron,

I see your formula: 4•t², but how did derive that formula? My physics days are more behind me than I thought, or it truly is 7am on Sunday morning...

My calculation is based on the fact that at the peak, the velocity of the ball is 0 and that, for these distances/speeds, it takes essentially half the time to go up and half the time to go do down.



I use the following:

v_y0 = 0...velocity at the peak of the throw
g = 32.2 (gravity at sea level)
t = 1, 1.5, and 2 (half of the observed time estimates, T)

So, the equation simplifes to 16.1 * t² (fall time) or 4.025 * T² (total time),

Someone could pull out a stopwatch and time it exactly if they wish and calculate it to the exact inch if they want.

[TXMike]

Originally Posted by Camron Rust

My calculation is based on the fact that at the peak, the velocity of the ball is 0 and that, for these distances/speeds, it takes essentially half the time to go up and half the time to go do down.

I believe this was a foul and do not question that Just trying to be straight on the math. Wouldn't the ball go up faster than it comes down, i.e. it would have to be moving faster than gravity in order to continue upwards?
Therefore, shouldn't the equation take that into account?

[JugglingReferee]

Originally Posted by Camron Rust

My calculation is based on the fact that at the peak, the velocity of the ball is 0 and that, for these distances/speeds, it takes essentially half the time to go up and half the time to go do down.





I use the following:

v_y0 = 0...velocity at the peak of the throw
g = 32.2 (gravity at sea level)
t = 1, 1.5, and 2 (half of the observed time estimates, T)

So, the equation simplifes to 16.1 * t² (fall time) or 4.025 * T² (total time),

Someone could pull out a stopwatch and time it exactly if they wish and calculate it to the exact inch if they want.

I recall now - thanks! We were taught that the imperial value for the acceleration due to gravity is 32.2 ft/s². We used 9.80665 m/s².