Chevrolet confirms cause of Malukas's engine issue in Milwaukee

Gavin Baker/Getty Images

By Marshall Pruett - Sep 1, 2026, 8:54 PM ET

Chevrolet confirms cause of Malukas's engine issue in Milwaukee

Chevrolet has responded to RACER's request for an explanation of what caused the engine in the No. 12 Team Penske Chevy driven by David Malukas during the Sunday closer to Snap-On's doubleheader at the Milwaukee Mile.

“David Malukas experienced an engine sensor issue that led to a plenum event during an upshift on the final restart near the conclusion of Sunday’s race at Milwaukee Mile," a Chevy spokesperson said.

"Chevrolet’s twin-turbo 2.2L V6 operates on a razor’s edge to give our drivers the best opportunity to win, and the top-seven and top-four finishes in the weekend’s two races reflect how hard our teams are pushing. We certainly understand David’s frustration at not securing the win he was pursuing. Racing is a constant balance between maximizing performance and reducing risk. We will apply the learnings from this past weekend to the season finale at Laguna Seca.”

The manufacturer's report aligns with the belief shared by Malukas after the race where, after being passed by eventual race winner Pato O'Ward of Arrow McLaren, the Penske driver pointed to multiple plenum events as the root cause of the temporary interruption of power delivery.

Malukas went from leading to eventually finishing second.

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

From Dakar to Vegas… Ford Raptor T1+ takes on a new challenge

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.