Recommended Posts

Wheldon dies from injuries

Two-time Indianapolis 500 winner and 2005 IndyCar Series champion Dan Wheldon has died from his injuries sustained in a crash at the IndyCar Series finale at Las Vegas Motor Speedway, it has been confirmed. He was 33.

Wheldon was moving his way through the 34-car field after starting from the back of the field, which was part of his $5 million challenge to win the race. His was one of the last cars to get involved in the crash, and was sent flying from the bottom of the racetrack into the wall on the outside.

Wheldon's Sam Schmidt Motorsports car suffered severe damage to the topside, including its rollhoop structure, and once he was extracted and other drivers were treated at the scene, his car was quickly covered with tarpaulin.

Wheldon was airlifted from the circuit's infield care centre to University Medical Centre in Las Vegas, but all medical efforts were to no avail.

Series chief Randy Bernard confirmed the news at 3pm, local time, and said: "IndyCar is very sad to announce Dan Wheldon passed away from unsurvivable injuries.

"Our thoughts and prayers are with Dan and his family. IndyCar, its drivers and teams have decided to end the race."

The race was red-flagged on lap 12 and was abandoned some two hours later. The drivers instead returned to their cars and performed a five-lap salute in Wheldon's honour.

Source: Autosport

R.I.P.

Link to comment
https://www.neowin.net/forum/topic/1032811-dan-wheldon-dies-from-injuries/
Share on other sites

Here's his blog about today's race: http://www.usatoday.com/sports/motor/indycar/story/2011-10-15/Dan-Wheldon-frustrated-with-car-in-Las-Vegas/50786654/1 . I don't watch racing much but it's still sad to hear. Apparently some drivers were concerned about the speed of track.

I remember him winning the Indy 500 this year... Its a shame he died. I actually had a ton of respect for the guy. He was an excellent driver and had a bright career ahead of him. One thing is for sure they will not be driving 225 at that track anymore. I wouldn't be suprised if they capped it at 180...That was too fast for such a small track to be honest and the drivers had every reason to worry. I'm not sure if all the prevention in terms of padding for the wall and fence would have helped in this situation. At least 3 cars went airborne out of the 15 that crashed from what i saw.

RIP :(

Racing's a tough sport with little margin for error - been there.

Thing is Michigan International can be even faster than Homestead-Miami Speedway - the record at MIS is a 234.949 mph (378.1138 kph) lap.

Side note: this was Danica Patrick's last Indy race - she's moving on to NASCAR.

RIP :(

Racing's a tough sport with little margin for error - been there.

Thing is Michigan International can be even faster than Homestead-Miami Speedway - the record at MIS is a 234.949 mph (378.1138 kph) lap.

Back in the day, they'd hit 235 and 240 at Indy...they've slowed down in recent years but that was in the 90s. Still it's sad and these things do happen, i think the lesson to be learned here is that if the drivers have concerns about going 225+ on a 1 mile track than maybe the IRL should have considered maybe restricting the speeds on the engines to no more than 200 .

Back in the day, they'd hit 235 and 240 at Indy...they've slowed down in recent years but that was in the 90s. Still it's sad and these things do happen, i think the lesson to be learned here is that if the drivers have concerns about going 225+ on a 1 mile track than maybe the IRL should have considered maybe restricting the speeds on the engines to no more than 200 .

there is no really big difference between 200 and 235

About 18%, just shy of the difference between 45 and 55 mph. Enough to miss someone if things go wonky. The difference between a collision and a scrape or near miss.

I've long thought there should be a lower turbocharger pressure allowed according to the length of the track. It's just crazy to be going that fast on a 1.0 - 1.5 mi straight oval track, but perfectly reasonable at a 2.0 mi (3.2 km) tri-oval like MIS.

percents are not matter. 200mph is still 90 meters per second speed with no room for reaction. it won't help unless you limit speeds to 100mph or just forbid ovals.

you can't do anything no matter if it's 90 meters per second or 110 meters per second. 160kmph would give you a one second to react, so you can slow down to 100kmph, which would be relatively safe for impact.

but would it be racing then?

The biggest problem isn't the speed, though that is, of course, a factor, it's also a race.

Indy, by design, is just dangerous.. It's fragile cars racing in generally large numbers at high speeds.. ****'s gonna happen every now and again..

F1 is similar, but generally there are fewer cars in such a small area, just by the nature of F1 races..

Nascar on the other hand has their safety come from the car, it can take a beating, also just touching Indy cars together does serous damage, not as much in Nascar, unless you send them into a wall.

Not saying there aren't things that could be done, safer barriers like Nascar is adding to most if not all the tracks they race on, and the like.. But racing cars is and will always be Dangerous.. Personally I'd get the drivers together and ask them what they think needs to be changed at the track/in general.. Did they feel the speed was okay, but this was just a freak accident, or did they feel unsafe from the beginning, etc.

there is no really big difference between 200 and 235

Actually theres a huge different - Nascar on its fastest tracks can hit 196 easily...tack on another 40mph and you're now at indy car speeds.

The biggest problem isn't the speed, though that is, of course, a factor, it's also a race.

Indy, by design, is just dangerous.. It's fragile cars racing in generally large numbers at high speeds.. ****'s gonna happen every now and again..

F1 is similar, but generally there are fewer cars in such a small area, just by the nature of F1 races..

Nascar on the other hand has their safety come from the car, it can take a beating, also just touching Indy cars together does serous damage, not as much in Nascar, unless you send them into a wall.

Not saying there aren't things that could be done, safer barriers like Nascar is adding to most if not all the tracks they race on, and the like.. But racing cars is and will always be Dangerous.. Personally I'd get the drivers together and ask them what they think needs to be changed at the track/in general.. Did they feel the speed was okay, but this was just a freak accident, or did they feel unsafe from the beginning, etc.

So what do yo want... a 50 foot high wall so they don't die? Or maybe you'd prefer them to drive 60 around the track. Nascar isn't that much safer...ask Dale Earnhardt Sr. or Davy Allison who both died from wreaks that looked far less fatal than the one today. Dan Wheldon died because his car got launched into the fence cockpit first and impacted the fence...no safer barrier in the world could have saved him from that. It's a freak accident but it happens when you have a car get launched 20+feet in the air going at 200mph. What you fail to realize is these people know the risk they take...they do it anyway because they love doing it. It's rare moments like this that you never see coming.

This topic is now closed to further replies.
  • Posts

    • I feel like Surface devices were popular about 10 years ago but have fallen off hard. I can't remember the last time someone talked about a new model Surface with excitement. The fact that the headline here is a new wallpaper and not the device is a bit telling.
    • Weirldy, in Texas the age of consent is 17, not 18.
    • DXVK generally performs better on Linux (using Wine/Proton) than on Windows. Because Linux utilizes highly optimized, open-source Vulkan drivers (like RADV/ACO) that were specifically built for AMD Radeon hardware, the translation of Direct3D 9/11 to Vulkan is highly efficient. But if you take the trouble to watch my video, you can see that there are also advantages for Nvidia users. You see that I run Assassin's Creed Odyssey on 4GB RAM and on an i3-3240. What do you think are the minimum system requirements for windows11? For CPU-based rendering, Linux is generally faster than windows11 by about 15% due to lighter background overhead and efficient kernel scheduling.
    • NetSpeedTray 1.3.2 by Razvan Serea NetSpeedTray is a lightweight, open-source Windows network monitor that shows live upload and download speeds directly on the Taskbar. Designed for efficiency, it quietly sits in the system tray, conserving CPU and battery with dynamic updates. It blends seamlessly with Windows 10/11, adapts to light/dark themes, and auto-positions to avoid overlaps. Features include accurate interface detection, customizable display, optional mini-graph, color coding, granular font and unit control, detailed per-interface history graphs, safe data management, and easy CSV export—bringing the network monitoring Windows forgot. NetSpeedTray key features: Lightweight & Efficient Runs quietly in your system tray without consuming resources. Features a "Dynamic Update Rate" that lowers refresh frequency when the network is idle to save CPU and battery life. Native Look & Feel Blends seamlessly with Windows 10/11 UI. Smart detection for light and dark taskbar themes ensures text is always visible. Intelligent & Adaptive Positioning Automatically finds empty space next to your system tray and shifts to make room for new icons, preventing overlaps. Seamless OS Integration Behaves like a native Windows component. Hides instantly with auto-hiding taskbar Hides when a fullscreen app is active Smart Network Monitoring Accurate by Default: Auto mode identifies your main internet connection and ignores noise from VPNs or virtual adapters. Easy Interface Selection: Switch effortlessly between Auto, All, or Selected network interfaces via intuitive radio buttons. Total Visual Customization Free Move Mode: Unlock and place the widget anywhere on your screen. Optional Mini-Graph: Real-time graph of recent network activity with adjustable opacity. Color Coding: Customize colors and speed thresholds to quickly see network status. Granular Display Control Text & Font: Adjust font family, size, weight, and alignment. Units: Automatic (B/s, KB/s, MB/s) or fixed Mbps display. Precision: Set decimal places and always show them for uniform appearance. Detailed & Intelligent History Graph Smart Scale: Logarithmic scale shows low-level traffic and large spikes clearly. Per-Interface Filtering: View speed history for specific adapters (Wi-Fi, Ethernet, VPN). Safe & Efficient Data Management: Adjustable retention, automatic cleanup, optimized database. Easy Data Export: Export raw data to .csv or save high-quality graphs for reports. NetSpeedTray v1.3.2: Smaller, Lighter, Better Multi-Monitor NetSpeedTray v1.3.2 focuses on being smaller, lighter, and more reliable, with major memory savings, better multi-monitor support, stronger privacy protections, and easier troubleshooting. Changes 24% smaller installer (106 → 81 MB) 28% smaller portable ZIP (127 → 91 MB) 45–70% lower idle RAM usage (~135 MB → ~40–75 MB) Preferred Monitor setting for multi-monitor setups (#72) Export Support Bundle for one-click bug-report packaging Live Windows Light/Dark theme detection (#62) Lazy loading of matplotlib & numpy for faster, lighter startup Improved multi-monitor widget position restore after reboot (#133) Windows 10/11 stylesheet and font compatibility fixes (#149) Support Bundle includes sanitized logs, config, and system info PII obfuscator hardened to cover IPv6, MACs, hostnames, GUIDs, and paths (#141) Unified log redaction across file and console logging Better diagnostic logging included by default in support bundles Korean translation improvements and updated translator credits (#139) Test suite expanded from 146 → 191 passing tests (+45) [full release notes] Download: NetSpeedTray 1.3.2 | 81.6 MB (Open Source) Download: NetSpeedTray Portable | 91.1 MB View: NetSpeedTray Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Reluctantly..bs. In this day and age(pun intended) information is more valuable then apps; big tech worked with the GOP and in dem states like California to add this crap so they can agro better marketing data.
  • Recent Achievements

    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      473
    2. 2
      PsYcHoKiLLa
      237
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      69
    5. 5
      Michael Scrip
      59
  • Tell a friend

    Love Neowin? Tell a friend!