Ferrari takes "Scorching Performance" a little too literally...

May 19, 2008
ShareThis

It's always a little sad to see a mega-dollar supercar engulfed in flame, but for some reason you can never really look away. This 599 GTB Fiorano was the unfortunate victim of an as-yet unexplained engine bay fire, which occurred as a showroom driver was shuttling the vehicle to a workshop for some repairs. The driver swears the car wasn't being subjected to any hardship prior to the fire, but the sad fact is that Ferrari or not, engine fires are a more common occurence than you'd think.

Thankfully nobody was hurt and while this horse ain't gunna prance no more, the damage should still be covered under warranty. The moral of this story: Always carry a fire extinguisher.

[Source: The Sun]

Comments

  • Dr Strange [reply]
    2 years ago 0 points
    Hahah damn oh well one less ugly Fezza on the road! Bring back the style of the f40!!!
  • Dr Strange [reply]
    2 years ago 0 points
    Hahah damn oh well one less ugly Fezza on the road! Bring back the style of the f40!
  • Axehead [reply]
    2 years ago 0 points
    Haha who cares, it's just another boring looking Fezza off the streets. Bring back the F40!
  • Mason Dix [reply]
    2 years ago 0 points
    Dude, the latest range of Ferraris are some of the nicest that have been made. A hell of a lot classier than older models. Now they look worth the money!
  • Axehead [reply]
    2 years ago 0 points
    lol r you serious?? They look like grandpa cars now! The Murcielago is an example of a seriously hot car!!
  • adam [reply]
    2 years ago 0 points
    "HOT" !!

Post new comment

Want to join the discussion, or start one off?

Before you can get started, you'll need to log in to the TMR comments system via one of the services below (TMR Hub, Facebook, OpenID). If you don't have an account with any of those three, we'd recommend a TMR Hub account, so that you can take advantage of the great features that are just around the corner.

OR OR

(optional)
(not shown to others)


To comment, you must be logged in via one of the above methods.