Advertisement
Advertisement
VeeKay runs up to sixth before pitlane crash ends day early

Paul Hurley/IMS Photo

By Marshall Pruett - May 25, 2025, 3:15 PM ET

VeeKay runs up to sixth before pitlane crash ends day early

Rinus VeeKay’s Indianapolis 500 lasted just 81 laps, but Lord, it was an amazing ride.

The young Dutchman had a terrible weekend in qualifying with the No. 18 Dale Coyne Racing Honda that left him starting 31st in the field of 33, but where he started was quickly forgotten.

VeeKay, who’s become one of the best performers at the Indy 500, went on a charge, carving through the pack until he reached sixth by the 80th lap, ahead of Josef Newgarden who started next to him on the last row, but it all unraveled on pit lane.

Pitting on lap 81, VeeKay reported a loss of brakes and spun, tagging the inside of pit wall at mostly unabated speed. Damage was extensive, with the right-rear suspension folded inward. His plus-25 day was over.

“No idea,” VeeKay said of what took him out of the race and left him 30th overall. “I pitted for tires and fuel. I already pitted at speed once and was fine. It really had no bite. I was doing, like, 120mph and I really had no response from the brakes, which at that point, I was just trying to hit the brakes as hard as possible and locked up the left rear, and it came around on me.”

Marshall Pruett
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

Crandon International Raceway announces first-ever vintage revival & reunion for 2026 Brush Run Speed Festival

Promo Image

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.