
Michael Levitt/Lumen
Blomqvist inching ahead slowly but surely on IndyCar debut in Toronto
Most rookies would be thrilled to start 20th out of 27 cars for their first NTT IndyCar Series race, especially on three days' notice, on a track they hadn't driven before Friday, and while it was raining. But not Tom Blomqvist.
The reigning IMSA DPi champion, who also starts third among the five rookies in the field, was visibly disappointed after earning 20th for Meyer Shank Racing, which speaks to the Briton’s high expectations for himself in even the most daunting circumstances.
Frustrated by his inability to transfer into the Firestone Fast 12 as his group searched for traction on the wet, gripless street circuit, Blomqvist wanted more from the session and struggled to find satisfaction after stepping from the No. 60 Honda normally occupied by Simon Pagenaud.
“It’s a shame we didn’t get a dry session, in a way, because I think we were making a step in the right direction,” Blomqvist said. “That was obviously another challenge with the wet. I didn’t know what to expect. I just need some more laps, which is the story of the weekend. But we kept it on the black stuff.”
Although he wasn’t impressed with his qualifying result, Blomqvist eventually managed to smile and did concede that things are looking up after his first two days as an IndyCar driver.
“Nonetheless, it’s the first weekend,” he said. “And every little bit, it's been getting better and better, slowly.”
Marshall Pruett
The 2026 season marks Marshall Pruett's 40th year working in the sport. In his role today for RACER, Pruett covers open-wheel and sports car racing as a writer, reporter, photographer, and filmmaker. In his previous career, he served as a mechanic, engineer, and team manager in a variety of series, including IndyCar, IMSA, and World Challenge.
Read Marshall Pruett's articles
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.






