
Ford Performance Racing School backs Briscoe for NXS
Ford Performance Racing School will sponsor Chase Briscoe in 16 NASCAR Xfinity Series races this season, Stewart-Haas Racing announced Saturday morning.
Briscoe's No. 98 Ford Mustang will carry Ford Performance Racing School for the first time at Las Vegas Motor Speedway on Feb. 22. The complete list of races where the company will be a primary sponsor was not released.
"When you have a racing school featuring the latest Ford Mustang GTs, there's no better way to market our performance driving instruction with a professional driver who races Mustangs," said Dan McKeever, president, Ford Performance Racing School.
"Chase Briscoe speaks the same language as our customers and demonstrates the capabilities of his race car in every race he enters. His knowledge of how to operate his Ford Mustang didn't happen overnight. It came with instruction and repetition, giving him confidence and understanding of his car's features. That's what we do for attendees of the Ford Performance Racing School, whether it's with a new Ford Mustang on the racetrack or a Ford F-150 on the trails."
The Ford Performance Racing school is based in Tooele, Utah, and also has an operation at Charlotte Motor Speedway.
Briscoe is back for a second season in the Xfinity Series after winning Rookie of the Year in 2019. In addition to Ford Performance Racing School, Briscoe will also have sponsorship support (in 10 races) from HighPoint.
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
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.




.png?environment=live)