
Brandon Badraoui/IMSA
United Autosports USA names refreshed driver line-up for Rolex 24
United Autosports USA will defend its LMP2 victory at the 64th Rolex 24 At Daytona with a refreshed driver line-up in its two ORECA 07-Gibsons.
Reigning Daytona LMP2 class winners Dan Goldburg, Paul di Resta, and Rasmus Lindh will be back behind the wheel of the No. 22 ORECA, and will be joined by Gregoire Saucy for this year's edition of the Rolex 24.
Saucy has spent the last two seasons at United Autosports' WEC LMGT3 program with McLaren, finishing a close second in this year's Qatar 1812km. The Swiss driver also has two seasons of LMP2 experience in the European Le Mans Series, and drove for United last year alongside Ben Hanley and Manuel Maldonado.
Hanley, the 2020 LMP2 winner at Daytona, will join Phil Fayer in the No. 2 United ORECA.
Also driving the No. 2 car are two new additions to United Autosports: Mikkel Jensen and Hunter McElrea, the two-time and defending IMSA Michelin Endurance Cup LMP2 champions.
Jensen and McElrea spent the last two seasons together at TDS Racing where, along with Steven Thomas, they combined for four wins – back-to-back wins at Indianapolis and Petit Le Mans – and two additional Sebring podiums in 10 races together.
“Winning the 24 Hours of Daytona is a monumental achievement, and one which we are extremely proud of,” said United Autosports CEO Richard Dean.
“Going for back-to-back victories is bold but with two driver line-ups that combine proven, race-winning United Autosports names and formidable new additions to the team, we are putting ourselves in the strongest possible position to lift that trophy once again in 2026.”
United Autosports will announce its full season and Endurance Cup drivers at a later date; Fayer and Goldburg have already been confirmed to run the full season.
RJ O’Connell
Read RJ O’Connell'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.



