🤖 Made with AI
#Bengals WR Ja’Marr Chase says the Bengals-Steelers rivalry is a thing, but it’s not close to Bengals-Chiefs.
"They way higher than that."
2
175
Masyn definitely took down this dude’s wife at some point.
From ChatGPT
I watched the uploaded clip frame-by-frame. This is a much tighter calculation than I expected.
The overlay confirms Winn’s throw was 99.8 mph and the runner was moving 30.3 ft/sec. The important thing is that we don’t need to redo the runner’s entire home-to-first time—we can hold Winn’s release point and the runner’s position at release constant and ask how much additional flight time the throw could tolerate.
From the first-base replay, my estimate is that the ball beats the runner by roughly 0.10–0.15 seconds. There’s some frame uncertainty because the video is ~30 fps and the exact instant the runner touches first is partially obscured.
Using the actual 99.8-mph throw as the baseline, that puts the break-even velocity approximately in the low-to-mid 80s.
My best estimate: ~84–86 mph is the slowest he could throw it and still get the out.
At about 85 mph, I think it becomes essentially a bang-bang play. At 82–83, I think the runner is probably safe. At 90 mph, he should still be out with a little room.
So if the question is “what’s the lowest velocity where I’d still bet on the out?” I’d call it ~86 mph. If we’re looking for the mathematical break-even point where ball and foot arrive essentially simultaneously, I’d estimate ~84–85 mph.
And that really puts the 99.8 into perspective: he probably had ~14–15 mph of velocity to spare despite the runner going 30.3 ft/sec.
If you want, I can go one level deeper and calculate it frame-by-frame using the actual release frame, catch frame, estimated throw distance, and runner’s distance from first at release. That should get us within ~1–2 mph.
8
792
JT retweeted
Umpire Doug Eddings tells Cardinals rookie Hancel Rincón to fix his hat, a breakdown
















