
IMSA: Lamborghini questions Daytona penalty
Lamborghini has responded to the penalties imposed on the five Huracan GT3s racing in the Rolex 24 At Daytona by stating that the cars were in full compliance with the regulations.
Huracans have each had a penalty of five minutes added to their final race times
from last month's opening round of the IMSA WeatherTech SportsCar Championship after officials invoked a clause in its rule book devised to punish sandbagging.A statement from Lamborghini Squadra Corse stressed that the five GT Daytona class Huracans run by four different teams "always complied with the technical regulations," passing both post-race scrutineering and then completing additional dyno testing.
It also pointed out that they "respected the Balance of Performance [the means by which different cars are equalized] imposed by IMSA before the race."
"Lamborghini Squadra Corse has always collaborated with IMSA with maximum transparency in order to achieve the correct BoP," Lamborghini motorsport boss Giorgio Sana said. "We are and will be available to IMSA technicians to achieve the performance required. However, we hope more FIA components and technical parameters will be used in the the future to ensure a correct BoP."
The last point is a reference to IMSA setting its own BoP despite adopting FIA GT3 rules for the GTD class in 2016. The Lamborghini's BoP was changed between the official pre-race "Roar Before the 24" test at the beginning of January and the 24 Hours. It received a 20kg weight increase and a smaller-diameter engine air-restrictor.
The Lamborghini still set significantly faster times in the race than at the Roar: the best Huracan lap from the test of 1m47.852s compared with its GTD fastest lap of 1m45.873s.
The penalties mean that the best-placed of the Lambos, the #28 Konrad Motorsport entry, drops from fifth to 10th in class.
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.





