.jpg?environment=live)
Ferrari’s Daytona
Ferrari
«
»
The Ferrari Daytona wasn’t given its name by Ferrari. Officially, this Ferrari model is called the 365 GTB/4 to signify its displacement per cylinder (365 cc), its body style (Grand Touring Berlinetta) and its number of camshafts.
However, when the car was shown for the first time at the 1968 Paris Auto Salon, the motoring press nicknamed it the ‘Daytona’ in honor of Ferrari’s 1-2-3 result at the previous year’s Rolex 24 at Daytona – a name which has stuck with the car ever since. And, in another way, a fitting name as examples of the model were fixture at the Rolex 24 at Daytona from 1970 until 1982.
The Daytona was both a revelation and a throwback when it was first unveiled to the public. It’s Pininfarina-designed bodywork was captivating from every angle, and offered great aerodynamics. However, at a time when other companies were moving to mid-engine designs, the Ferrari Daytona continued to use a front-engine layout with a 4.4-liter V12 engine under its long hood. With the power and torque offered by the big V12, it was no surprise that the Ferrari couple became a stalwart on Daytona’s high banks.
A Daytona first appeared at the 24 Hours in 1970, with an example entered by Luigi Chinetti’s North American Racing Team (NART) car retiring before the finish. The first success came in 1972, in the shortened six-hour race, with a class victory by a Daytona entered by the Ring Free Oil Racing Team and driven by Charles Reynolds and Clive Baker.
The 1973 race saw a high water mark for the Daytona during the 24 Hours. A NART-entered Daytona driven by Francois Migault and Milt Minter finished a strong second overall, taking class honors as well. Production of the car ended that year, but Daytonas continued to appear for the twice-around-the-clock contest.
Another NART Daytona took class victory in 1975, driven by Jon Woodner and Fred Phillips. That year, the replacement for the Daytona, the 365 GT4 BB, took part in its first 24 Hours.
Daytonas continued to pound around Daytona’s high banks – actor Paul Newman even raced one, in 1977, finishing fifth overall in a Ramsey Ferrari / Modena entry he shared with Elliot Forbes Robinson and Milt Minter. But 1979, four years after the model’s production had ended, would bring its finest performance at the 24 Hours.
By this point, Ferrari had developed the 512 BB LM as its GT racer, developed to take on the overwhelming numbers of Porsches 935s. The lone Daytona that year, entered by Modena Sports Cars for drivers Tony Adamowicz and John Morton, was considered a mere field-filler after qualifying in 24th position overall. In fact, the Ferrari nearly didn’t take the green flag after team manager Otto Zipper passed away the night before the race in his hotel room. After nearly withdrawing from the race, the team opted instead to race with a black band across the hood honoring Zipper.
While no threat for high honors based on its pace, the Ferrari Daytona – which was once owned by actor Bobby Carradine – ran reliably throughout the 24 hours except for one trip to the garage to replace a damaged oil line. While much faster GTX-class cars encountered a host of terminal problems, Adamowicz and Morton guided the Ferrari higher and higher through the running order – up to second place overall and first in the GTO class, where it took the checkered flag. It was a stunning result for the aging car – and perhaps the best way for the team to have honored Zipper.
Zipper’s Modena Sports Cars, which prepared the car, was based in Los Angeles – not far from where Scuderia Corsa, which has claimed the last two IMSA GT-Daytona drivers championships, is based.
That same Ferrari Daytona returned for two more Rolex 24 at Daytonas, but didn’t come close to repeating its 1979 result. 1981 would be the last time a Daytona would be seen in the endurance race.
here
.Read full article on Press Room IMSA
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.


