Bell diagnosed with wrist fracture after Michigan crash; cleared to race at Pocono

David Jensen/Getty Images

By Kelly Crandall - Jun 9, 2026, 7:10 PM ET

Bell diagnosed with wrist fracture after Michigan crash; cleared to race at Pocono

Christopher Bell suffered a fractured left wrist after being involved in a violent crash Sunday at Michigan International Speedway.

Bell, however, has been cleared to race and will compete this upcoming weekend at Pocono Raceway. Joe Gibbs Racing announced that the injury was confirmed by X-rays upon Bell’s return to North Carolina.

“Thank you to each and every one who reached out to check on me, I truly feel the love,” Bell posted on social media. “I’m grateful for my team of doctors, JGR, NASCAR, and all of the previous drivers who have helped pave the way for the safety standards in our sport. See you in Pocono!”

The crash occurred in Turns 3 and 4 on lap 148 when Chase Elliott got loose underneath Bell as the two battled for the second position. Elliott collided with Bell’s car, which shot it to the outside wall. And then Elliott, whose car also went to the outside wall, bounced off Bell’s again before the incident came to an end.

Both drivers climbed from their cars under their own power and were cleared from the infield care center. Elliott took responsibility for the crash.

Bell did not speak to the media on Sunday. The social media post was the first time he addressed the incident.

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.