.jpg?environment=live)
Wolff hits out at DTM stewards' calls
Mercedes chief Toto Wolff has called for DTM stewarding decisions to be "in the best interests of the sport and of exciting racing", in an open letter to series bosses.
somewhat confusing drive-through penalty
for unsafe release.It is still not clear if the penalty was meant for Wickens, or if stewards confused the Canadian's car with the similar-looking Mercedes of Pascal Wehrlein, who made contact with race winner Marco Wittmann's BMW during the stops.
In the letter Wolff argued that Wickens release was not unsafe, and that the interest of the sport and the race should be taken into account by stewards when making decisions on penalties.
"We remain convinced that the decision was wrong in principle, particularly on close reading of the precise definition of what constitutes an 'unsafe release'," wrote Wolff.
"Having completed his pitstop on lap 22, Robert Wickens was 'released' from his box.
"There is clear video and photo evidence that the driver behind him was not even in the outside lane at this point in time. Wickens's exit from his box may not have been optimum, but there is no way that the pit crew could have foreseen this, and they cannot therefore be held liable for an 'unsafe release'.
"We regard the case of Pascal Wehrlein as a more clear-cut example of 'unsafe release'.
"The initial decision was to take no further action, but he was then penalised after the race. Not only was the consistency of the decision making questionable but also the severity of the punishment.
"Quite apart from the case under discussion, we believe that there is a need in the DTM for a more consistent and accountable procedure for potential offences and the penalties they incur.
"When in doubt, decisions must be made in the spirit of the sport and in the interests of exciting racing."
Originally on Autosport.com
Latest News
Comments
Comments are disabled until you accept Social Networking Cookies. Update cookie preferences
If the dialog doesn't appear, ad-blockers are often the cause; try disabling yours or see our Social Features Support.

.jpeg?environment=live)



