The Summary of Changes document, under Significant changes, point 6,
says:
> If a call during or after the throwing motion did not affect possession, then it should be ignored. For example, if
> a thrower is fouled in the act of throwing, but the disc flies perfectly to the receiver who then drops it on their
> chest, the turnover should stand.
Furthermore, in the 2009 Interpretations document, under 16.1, it
says:
> What: The thrower calls a fould against the marker during the act of throwing. The throw comes out fine and
> heads straight for its intended target - an unguarded offensive player. The offensive player drops an easy catch.
> Result: The turn over stands. Play restarts with a check.
> Why: Rule 16.1.3.2. ...
I have two questions regarding this.
1. First of all, I cannot find rule 16.1.3.2 in the 2009 rules. Am I
missing something?
2. How easy does the throw have to be in order for this rule to apply?
What if the thrower attempts a hard throw, there is a foul, the throw
nevertheless goes as intended, but the receiver drops it simply
because it was a hard throw to catch?
Best Regards,
Henrik Jernevad
To me the rule makes it clear that the idea of being able to get the disc back after a foul during a throw is that the receiver doesnt get the benefit of not causing a turnover on a catching mistake. As such I expect the thrower to say "play on" ASAP .. possibly while the disc is still in the air. Furthermore a turnover relies a lot on the honestly of the thrower here, except for obvious fumbles on an _easy_ catch. However I think its close to impossible for the defense to enforce this rule unless the thrower concedes that the disc took the intended course.
So in conclusion the purpose of the rule is to just clarify the fact that a foul on the thrower does not mean the receiver gets a free pass for a catching mistake, but there is only the sprit of the thrower determining if the fumble was caused by the foul on the throw or via a receiver fumble.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
This should refer to rule 16.1.2.2.2.
All references have been changed
Cheers
Rueben Berg