
INDYCAR: Firestone clarifies Texas tire allotment
Firestone has clarified the allotment of tires to all teams for Saturday night's conclusion of the Firestone 600 at Texas Motor Speedway.
All teams will have the original allotment of six sets of tires at their disposal for the race, which was stopped June 12 after 71 of the scheduled 248 laps due to heavy rain. Each set will be made of the exact sticker sets that were in the teams' possession in June. For teams that do not still have six sticker sets left from June, new sets will be provided – no scuffed tires will be used.
Each team will also receive one new set of tires for the practice sessions on Saturday afternoon.
Related Stories
"We decided to go back to the exact sets for a number of reasons, all in an effort to make life easier for the teams," said Dale Harrigle, Firestone's chief engineer and manager of race tire development. "The first is, we did not want to remove any of the team markings, so all the tires are still marked by the teams' specific set numbers, position and so on.
"The second reason is, on the ovals, the teams meticulously measure every tire and build their sets based on exact tire measurements. By giving them the same exact sets back, they do not have to go through the process a second time."
The full field of original starters will resume the race with the exception of Josef Newgarden and Conor Daly, who were involved in a heavy crash on lap 42 before the race was red-flagged for rain. Newgarden sustained a fractured right clavicle and fractured right hand in the incident, but did not miss any of the five races in the interim. Both Newgarden’s and Daly’s cars would not have been able to continue at Texas that day, so IndyCar ruled them ineligible to rejoin the field for Saturday’s race completion.
NBCSN will telecast the conclusion of the Firestone 600 live at 9 p.m. ET Saturday.
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)
