Lundgaard, Malukas entries handed engine penalties for Nashville IndyCar race
By Mark Glendenning - Jul 18, 2026, 9:24 AM ET

Lundgaard, Malukas entries handed engine penalties for Nashville IndyCar race

INDYCAR Officiating has issued nine-position starting grid penalties to Arrow McLaren's No. 7 entry, driven by Christian Lundgaard, and the No.12 Team Penske entry of David Malukas ahead of Sunday's NTT IndyCar Series race at Nashville Superspeedway.

The penalties are for unapproved engine changes following a team test at Milwaukee Mile on July 8.

The entries were determined to be in violation of Rule 16.1.2.3.2: A fifth (5th) Engine is eligible to earn Engine Manufacturer points and will be considered an Approved Engine Change-Out if a Full Season Entrant has completed the Full Season Entrant Engine Mileage with its first four (4) Engines. Otherwise, a fifth (5th) or more Engine does not earn Engine Manufacturer points and will be considered an Unapproved Engine Change-Out.

The penalty for breaches of Rule 16.1.6.1.2 is a six-position starting grid penalty on road and street course events and nine positions at oval events, to be served at the series’ next event.

Mark Glendenning
Mark Glendenning

During his long career in racing, Mark has been placed into a headlock by a multiple grand prix winner, escaped a burning GT car, ridden a Ferris wheel with Ari Vatanen and almost navigated a rally car into a pond. He’s also had the good fortune to have reported on hundreds of races around the world, first while working for a national publication in his native Australia, and later during his years with Autosport in the UK. He moved to the U.S. in 2012, and after a serving as a contributor to RACER he joined the publication full-time in 2015. Mark now serves as Editor of RACER.com, and is also involved in the production of the magazine.

Read Mark Glendenning'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.