Advertisement
Advertisement
11 cars sent to rear of Kansas field for inspection failures

Image by Gavin Baker

By Kelly Crandall - May 11, 2019, 6:33 PM ET

11 cars sent to rear of Kansas field for inspection failures

Eleven cars, including five that had qualified in the top eight spots, failed inspection at Kansas Speedway. All 11 drivers had their qualifying times disallowed and will start at the rear of the field for tonight's race. Each team also lost their pit stall selection.

The cars that failed once included those of Aric Almirola, who had qualified second, and his Stewart-Haas Racing teammate Daniel Suarez, who had qualified fourth. Sixth-place qualifier Martin Truex Jr. – who won from the rear last weekend at Dover – also had his car fail.

The rest of the one-time failures were Ty Dillon (had qualified 15th), Michael McDowell (23rd), Landon Cassill (25th), Joey Gase (39th), and Timmy Hill (39th).

Three cars failed twice, which resulted not only in having their times disallowed and lose of pit stall selection but the ejection of their car chiefs.

The cars that failed were: Chase Elliott’s (had qualified fifth), Kyle Larson (eighth), and Joey Logano (20th).

Under the enhanced weekend schedule, inspection for the Digital Ally 400 was held Saturday afternoon, serving as both post-qualifying and pre-race inspection.

Kevin Harvick and Clint Bowyer will now start on the front row. The race is scheduled to go green after 7:30 p.m. ET.

Kelly Crandall
Kelly Crandall

Kelly has been on the NASCAR beat full-time since 2013, and joined RACER as chief NASCAR writer in 2017. Her work has also appeared in NASCAR.com, the NASCAR Illustrated magazine, and NBC Sports. A corporate communications graduate from Central Penn College, Crandall is a two-time George Cunningham Writer of the Year recipient from the National Motorsports Press Association.

Read Kelly Crandall'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.