
Joe Skibinski/IMS photo
Schumacher 'blown away' by first Indy 500 experience
Mick Schumacher’s first Indianapolis 500 was a long journey of discovery for the driver of the No. 47 Rahal Letterman Lanigan Racing Honda.
Starting 27th, the newcomer to oval racing rose as high fifth during pit stop exchanges and finished 18th after glancing off the wall to close the 200-lap contest. Despite the brief meeting with the wall, Schumacher was able to continue racing and crossed the finish line at the top rookie performer.
“I understand where people come from when they say this is the greatest spectacle in racing,” Schumacher told RACER. “It definitely is insane, amazing to be a part of this, and yeah, simply blown away by this event.”
RLL teammate and two-time Indy 500 winner Takuma Sato led the effort home in 10th, and Schumacher was RLL’s second-best driver on the day as Graham Rahal was 20th and Louis Foster finished 21st.
“We're a bit unfortunate with the yellows,” Schumacher added. “I think without them, we would have been right in there. I think top 10 was definitely on the cards; we kept it clean, that's what we wanted to do, and obviously, yes, the last bit there, when we hit the wall…hey, how many can say they finished the Indy 500 and hit the wall, right?”
The sheer intensity of the Indy 500 left its mark on Schumacher, who was dealing with a significant adrenalin dump right after the race.
“Yeah,” he said, “I'm ready to go and have a nap.”
Presented by:

For making every mile more exhilarating
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.




