ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

2012 Daytona 500 - A NASCAR race with Fire, Rain, Racing and Crashes

Updated on June 10, 2013

Matt Kenseth

Matt Kenseth racing his #17 around the track at a NASCAR race
Matt Kenseth racing his #17 around the track at a NASCAR race | Source

Stock Car Racing

I am what I would describe to be a casual fan of NASCAR races. If I have some free time I will probably watch some of a race but I do not plan my day around them or try to record them for later viewing. Initially I was drawn to the sport because of the wrecks; yes I was one of those fans. Over the years I have matured as a fan of the sport and have grown to understand, and appreciate, the drivers for their skill in operating these powerful machines at the speeds they reach.

Every season NASCAR begins with their biggest race, the Daytona 500. Unlike other sports that have their biggest event at the end of the season (like the Super Bowl or World Series) NASCAR gets their big one out of the gate on day one.

Being the casual fan I really don’t have a favorite driver so my personal vehicle isn’t littered with stickers reflecting a drivers’ name or car number. I’m not knocking the fans that do have these stickers, it just isn’t for me.

Even though I am not a NASCAR diehard I still have drivers that I do not like, just like I have baseball and football teams I do not root for. My public enemy number one is Kyle Busch and his #18 car. Kyle is an incredibly talented driver but the rest of what he does drives me nuts. I guess that is part of the attraction for fans, you can cheer for one driver to win the race while hoping another one blows an engine on lap one.

Kyle Busch

Kyle Busch, the driver of the #18 car, signing autographs.
Kyle Busch, the driver of the #18 car, signing autographs. | Source

Daytona 500 Weather

The 2012 Daytona 500 had a memorable weekend for quite a few reasons. I guess the main reason would be that the race couldn’t be contained to the weekend. Storms running through Florida postponed the original early Sunday start until later on in the day. After waiting for the clouds to pass NASCAR made the decision, a first for the Daytona 500, to delay the race and wait until Monday to drop the green flag.

Early Monday the rain problems continued for the race and it had to be moved to an evening start. From a television rating standpoint this was a positive move because more fans could watch the game in the evening than in the middle of the day. I felt really bad for all of the fans that purchased tickets to the event. Having the race move a day probably messed up their schedules and might have soured them on the whole experience; at least they were treated to a good race, if they stuck with it.

NASCAR Races

Are you a fan of NASCAR?

See results

Car Drafting

Regarding the race, kudos to NASCAR for making the changes needed to stop the two car racing that dominated last year’s race. Seeing a bunch of two car tandems flying around the track last year was boring and wasn’t conducive to the exciting racing that many fans wanted to see.

Daytona 500 Crash

I am certainly no NASCAR expert but I saw something at the race this year I never thought I would see on a racetrack. During a caution the number 42 car, driven by Juan Pablo Montoya, exited the pits and made his way back to the track. Montoya had been complaining about something not feeling right in his car and that feeling was confirmed when a part failed, causing him to lose control of the vehicle. Many racetracks have vehicles that they deploy to help dry out a wet track or blow excess debris off of the racing surface. One of these drying trucks (they are regular trucks towing a trailer that has a jet engine mounted on it) was doing its job, a short distance in front of Montoya’s out of control vehicle.

You can probably figure out what happened next, Montoya’s sideways car plowed into the back of the trailer immediately igniting the full tank of jet fuel creating a massive fireball and red flagging the race forcing all racecars to stop on the track. Both Montoya, and the driver of the blower vehicle, exited and were OK but the jet fuel started pouring down the angled track. Fire was quickly spreading and it took about ten minutes before fire crews finally got the fire under control.

After additional cleanup the track was finally cleared and the race resumed. Matt Kenseth, who drives the number seventeen car, eventually won the race that was delayed by rain and fire, all in the same day.

The open track racing that I enjoy was evident during this year’s race and I appreciated seeing it again. Sure they had some wrecks, which took out quite a few previous winners and contenders, but overall it was enjoyable to watch and I hope NASCAR continues to allow the drivers to do their thing and thrill their fans.

Juan Pablo Montoya

Juan Pablo Montoya's #42 machine excluding damage from wrecking into a jet dryer.
Juan Pablo Montoya's #42 machine excluding damage from wrecking into a jet dryer. | Source

Daytona 500 Fire

Comments

    0 of 8192 characters used
    Post Comment

    • profile image

      joshua 

      6 years ago

      bull cazy

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)