Caught short – Investigations launched over Hobart Cup distance bungle
Multiple investigations have been launched into a blunder which saw one of Tasmania’s biggest races, the Hobart Cup, run short of its advertised distance on Sunday.

Tasracing has called on the newly formed Tasmanian Racing Integrity Commissioner to investigate how Sunday’s feature Group 3 Hobart Cup was run short of its advertised distance.
Tasmanian racing’s governing body sent out an industry notice, conceding that an error was made with the barriers not placed in the intended position within the starting chute. Multiple investigations have been launched into the matter.
As a result, Tasracing has conceded the race was held “marginally short” of the stated 2400-metre distance. It hasn’t revealed the distance difference, but The Straight understands it was approximately 40 metres less than it should have been.
There was no mention of the incident in the stewards’ report on the race.
However, the fact that the winner Blonde Star broke the track record when the going was rated a Soft 5 did raise eyebrows. The mare ran 2min 29.67secs, more than 0.5s faster than the previous fastest time in the race since it was switched back to 2400m in 2014.
The locally trained stayer edged out Ziryab in a photo, with the fast-finishing Distrustful Award, less than 0.25l away in third.
It was the 152nd running of the Hobart Cup.
In the other “fast-class” races of the day, the 1200m Mystic Journey was won in a time more than a second outside the track record, while the Thomas Lyons over 1400m was won by Steparty in a time around a length outside the track record.
Tasracing has said it will issue a further statement, but will not be revising the results.
“While the result of the race stands, no objections were lodged following the running of the Hobart Cup and correct weight was declared,” it said.
“Tasracing is conducting its own inquiry and has also referred the matter to the Tasmanian Racing Integrity Commissioner for investigation.”
“Tasracing will provide a further statement in due course, including details of steps it will implement to ensure the error does not occur again.”
