
PWC: Acura adds Pumpelly; Cunningham to NSX
developing the brand's 2017 NSX GT3
."To be a part of this progression of the NSX GT3 is a tremendous opportunity. Having been the test driver in North America for the first generation NSX race car, I feel a deep connection to this project," Cunningham said. "With the new NSX coming on line, it is a very important program for Acura and I'm honored to be able to contribute. As I focus my energies on the NSX, we knew that we needed to find a top-notch driver for the TLX to bring Acura the best possible result."
RTR found great success with the previous version of the NSX, with Cunningham earning 14 wins during its time in World Challenge. The addition of Pumpelly should make for a quick and easy fit within the team as he and Ryan Eversley, who pilots the No. 42 TLX, are close friends away from the track and bring an instant bond to the program, evidenced by his reveal on social media.
//platform.twitter.com/widgets.js
//platform.twitter.com/widgets.js
"I am thrilled to be joining RealTime Racing this weekend in Ohio and excited to become part of the Acura family," said Pumpelly, who will also race in Cunningham's place on Aug. 12-14 at the Utah Motorsports Campus (formerly known as Miller Motorsports Park). "The team and brand have achieved tremendous success in the series and it's an honor to be able to work with all the people involved. The Acura TLX is an amazing car which should do well around the tight turns of Mid-Ohio. The team has been a huge help in getting me comfortable in the car and I'm eager to get on track with it."
In addition to the driver change in the No. 43, Acura revealed Wednesday that the public debut of the NSX GT3 will take place today and Friday during practice for the PWC event at Mid-Ohio. Dutchman Peter Kox will drive the car both days before it is parked and put on display in the paddock.
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.




