
NASCAR XFINITY: Ryan Reed wins as Kyle Busch hospitalized
Opening the 2015 NASCAR XFINITY Series season with a win in the Alert Today Florida 300 at Daytona International Speedway was Roush Fenway Racing driver Ryan Reed.
Reed piloted his No. 16 Ford to victory after leading for a total of 14 laps using a late surge to get past Brad Keselowski for the lead. This is Reed's first win at Daytona and his first in the XFINITY Series.
Coming up short to Reed was his RFR teammate Chris Buescher finishing second.
Ty Dillon, Austin Dillon and Brad Keselowski completed the top-five finishers on the leaderboard.
Reigning XFINITY Series champion Chase Elliott finished 28th after a wreck on Lap 112 caused major damage to his No. 9 NAPA Auto Parts Chevrolet. Kyle Busch was involved in that wreck and was taken on a stretcher in an ambulance to hospital. NASCAR revealed Kyle was awake and alert but had an injury to his right leg.
VIDEO: Race highlights
2015 XFINITY rookie Darrell Wallace Jr. started the race 28th and quickly made his way into the top five. Wallace first saw the lead on Lap 30 and held it for a total of 18 laps. The Roush Fenway Racing driver finished 12th.
Elliott's JR Motorsports teammate Regan Smith went flipping down the backstretch on Lap 93 when rookie Daniel Suarez got loose and sent Smith airborne. Brendan Gaughan, Scott Lagasse Jr., Elliott, John Wes Townley and Chad Boat were also involved in the wreckage. Smith's car was too far damaged to rejoin the race and he ultimately finished 35th. Smith will be piloting the No. 41 Stewart-Haas Racing Chevrolet tomorrow for Kurt Busch who was suspended indefinitely by NASCAR on Friday.
The XFINITY Series returns to the track Saturday, Feb, 28 (2 p.m. ET, FS1) at Atlanta Motor Speedway for the Hisense 250.
Tune in tomorrow as the Sprint Cup Series kicks off its season with the Daytona 500 at 1 p.m. ET with TV coverage on FOX.
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.





