Advertisement
Advertisement
Ahead of IndyCar opener, Palou already focusing on 500

Chris Owens/Penske Entertainment

By Marshall Pruett - Mar 8, 2024, 8:06 AM ET

Ahead of IndyCar opener, Palou already focusing on 500

Alex Palou has achieved almost all of his IndyCar goals since joining the series in 2020. With two championships to his credit and pole position at last year’s Indianapolis 500, the Chip Ganassi Racing has trophies and all manner of keepsakes from his trips to victory lane.

Earning that Indy 500 winner’s ring is the last major accomplishment left for the Spaniard, and with the start of a new season just days away, the next chance to drink the milk and be crowned as the winner of IndyCar’s most important race will be here in May.

“Obviously the 500, it's the first big target that we can achieve. We'll fight for it. It's the main goal, but it's not the only goal,” Palou said Friday morning at St. Petersburg.

The 26-year-old has become an annual threat to win the Indy 500, all despite being an oval racing novice when he arrived in IndyCar. He’s won plenty of road and street course events, but his first oval win is another goal for Palou. He has an opportunity to accomplish both on May 26 in the No. 10 CGR Honda.

“It's the main goal because it's in May, coming up quick, and it's our biggest race of the year,” he added. “But yeah, I'll keep knocking on that door. I know we'll have fast cars. It's just if everything fits on that day.”

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

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.