
Barry Cantrell/Motorsport Images
Kellett returning with Foyt
Dalton Kellett will remain with A.J. Foyt Racing. The 28-year-old Canadian returns to the No. 4 Chevy and welcomes 2021 Indy Lights champion Kyle Kirkwood to the team in the sister No. 14 Chevy.
"I'm very excited to be back with AJ Foyt Racing for the 2022 season," Kellett said. "We are looking forward to the year and continuing to build on the momentum from 2021. I'm grateful for the opportunity to be back in the number 4 Chevrolet. A.J., Larry, our team partners, and K-Line have made this a possibility, so I am very thankful for them.
“Looking back at 2021, we had moments of promise and some encouraging results, we need to enter the 2022 season on that trajectory. The schedule looks very exciting this year, some familiar tracks returning and I can't wait to be racing in front of the hometown crowd in Toronto."
With the recent roster changes, Kellett becomes Foyt’s most tenured driver after joining the four-time Indy 500 winner’s outfit in 2020.
"It's great to have Dalton continuing with the team in 2022," said team president Larry Foyt. "He made some solid progress in his first full season in the NTT IndyCar Series, and I'm looking forward to seeing what he can accomplish next season. He is a true team player and a great ambassador for AJ Foyt Racing."
In 24 IndyCar starts, the Road To Indy veteran’s best finish came in August at World Wide Technologies Raceway where he placed 12th on the 1.25-mile oval.
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.


