Human Running Speeds of 35 to 40 Mph May Be Biologically Possible


Recommended Posts

ScienceDaily (Jan. 22, 2010) ? Jamaican sprinter Usain Bolt's record-setting performances have unleashed a wave of interest in the ultimate limits to human running speed. A new study published in the Journal of Applied Physiology offers intriguing insights into the biology and perhaps even the future of human running speed.

The newly published evidence identifies the critical variable imposing the biological limit to running speed, and offers an enticing view of how the biological limits might be pushed back beyond the nearly 28 miles per hour speeds achieved by Bolt to speeds of perhaps 35 or even 40 miles per hour.

The new paper, "The biological limits to running speed are imposed from the ground up," was authored by Peter Weyand of Southern Methodist University; Rosalind Sandell and Danille Prime, both formerly of Rice University; and Matthew Bundle of the University of Wyoming.

"The prevailing view that speed is limited by the force with which the limbs can strike the running surface is an eminently reasonable one," said Weyand, associate professor of applied physiology and biomechanics at SMU in Dallas.

"If one considers that elite sprinters can apply peak forces of 800 to 1,000 pounds with a single limb during each sprinting step, it's easy to believe that runners are probably operating at or near the force limits of their muscles and limbs," he said. "However, our new data clearly show that this is not the case. Despite how large the running forces can be, we found that the limbs are capable of applying much greater ground forces than those present during top-speed forward running."

In contrast to a force limit, what the researchers found was that the critical biological limit is imposed by time -- specifically, the very brief periods of time available to apply force to the ground while sprinting. In elite sprinters, foot-ground contact times are less than one-tenth of one second, and peak ground forces occur within less than one-twentieth of one second of the first instant of foot-ground contact.

The researchers took advantage of several experimental tools to arrive at the new conclusions. They used a high-speed treadmill capable of attaining speeds greater than 40 miles per hour and of acquiring precise measurements of the forces applied to the surface with each footfall. They also had subjects' perform at high speeds in different gaits. In addition to completing traditional top-speed forward running tests, subjects hopped on one leg and ran backward to their fastest possible speeds on the treadmill.

The unconventional tests were strategically selected to test the prevailing beliefs about mechanical factors that limit human running speeds -- specifically, the idea that the speed limit is imposed by how forcefully a runner's limbs can strike the ground.

However, the researchers found that the ground forces applied while hopping on one leg at top speed exceeded those applied during top-speed forward running by 30 percent or more, and that the forces generated by the active muscles within the limb were roughly 1.5 to 2 times greater in the one-legged hopping gait.

The time limit conclusion was supported by the agreement of the minimum foot-ground contact times observed during top-speed backward and forward running. Although top backward vs. forward speeds were substantially slower, as expected, the minimum periods of foot-ground contact at top backward and forward speeds were essentially identical.

According to Matthew Bundle, an assistant professor of biomechanics at the University of Wyoming, "The very close agreement in the briefest periods of foot-ground contact at top speed in these two very different gaits points to a biological limit on how quickly the active muscle fibers can generate the forces necessary to get the runner back up off the ground during each step."

The researchers said the new work shows that running speed limits are set by the contractile speed limits of the muscle fibers themselves, with fiber contractile speeds setting the limit on how quickly the runner's limb can apply force to the running surface.

"Our simple projections indicate that muscle contractile speeds that would allow for maximal or near-maximal forces would permit running speeds of 35 to 40 miles per hour and conceivably faster," Bundle said.

Science Daily

i read that entire thing, and it all just seemed like babble. No real useful information.

It reads like a scientific report. It can't really be all that much simpler without becoming misleading.

In any case, if you do need a summary, it's this: we may have access to more running power than we think. They tried different gaits and found that full speed running wasn't using all the available power.

I'll believe someone can run 40 miles per hour when I see it.

But if it IS possible, it's likely to be Bolt who does it! Even he reckons he can go faster, and who but the fastest man alive would know better about his limits?

it sounds like they are measuring only how much force is hitting the ground from the foot, and how quickly the force is applied... not once did they mention anything about how fast the foot is actually moving? as in, the degrees of joint rotation / second ... i would have thought that is the main factor on how fast humans can run...

What's the point? That the future humans are going to be quicker? That's what it sounds like. To me, it would seem they plan on generating genetics for future humans and plan on injecting it into vaginas so babies will be born with with new features.

If it is possible the person doing it he would wish he hadn't after a short time of wearing his cartilage down to nothing due to the enormous stresses generated. Not to speak of his spine. Every disk in it will herniate.

If it is possible the person doing it he would wish he hadn't after a short time of wearing his cartilage down to nothing due to the enormous stresses generated. Not to speak of his spine. Every disk in it will herniate.

Herniate... I've a new favourite word!

This is the solution we've been waiting for to one area of the energy crisis - no more cars in future, we run everywhere!

If it is possible the person doing it he would wish he hadn't after a short time of wearing his cartilage down to nothing due to the enormous stresses generated. Not to speak of his spine. Every disk in it will herniate.

I'm curious... What makes you come to such a conclusion?

I'm curious... What makes you come to such a conclusion?

Simple logic. In order to generate the necessary momentum to produce such speeds the loadstress in all articulations increases exponentially. The increased momentum will transfer to the ground via the legs, the back takes a increased weight impact. Since the spine in it's design is not yet fully evolved for proper bipedal motion (it's basically just quadriped spine moving on two legs) it'll suffer the loads badly.

As increased wear and tear speed up the celldivision your reserves of telomeres run out quickly resulted in speeded degeneration.

In other words: you can run your car at full speed all the time, but the changes you'll end up in the repairshop are higher than if you just keep it at it's cruising speed.

As far as the human body is concerned, "simple logic" is usually not sufficient. Sure, for athlete's, injuries to joints and ligament are common when they are too long at the high end of their capability; but that doesn't happen to ALL athlete's. The human body is a remarkable machine, and it continues to evolve. Just take Usain Bolt as an example. 10 years ago, no one would have thought it possible for a human to achieve the speeds he's capable of. 10 years from now, he might be seen as an average runner, who knows.

Right now, this theory of there's is nothing but that, a theory. They have seemingly shown that the previously thought of speed limit being caused by the level of impact with the ground and the duration of that impact is incorrect, and instead its determined by the "twitch" response time of the muscles involved. That doesn't mean a practical answer exists, or ever WILL exist, to speeding humans up. Merely that it's theoretically possible to go faster.

Maybe one day we will, maybe not. I suspect though, that if we DO, it's at the tail end of some further evolutionary steps which will no doubt take care of the incumbent bodily stresses.

As far as the human body is concerned, "simple logic" is usually not sufficient.

Yes it suffices largely. It's a very fragile sac of bones and tissue. A particle as small as a virus can destroy it within 48 hours.

Cells have a limited DNA repair facility. After the DNA repair mechanism fails you start to age. The more you make your body divide (in order to heal and reenforce structures/muscles) cells the faster you start to age.

Some people with extraordinary genetic makeup have more DNA repair reserves, but the overwhelmingly biggest part doesn't which is why there's an average age of death with a few exceptions to the higher numbers.

But if you prefer to believe a body is perpetual motion mechanism.........who am i to tell it's just not remotely realistic?? :rofl:

Sorry mate. You might be widely educated in a broad range of topics (or read Wikipedia a lot), but I'm gonna go with a family history of several generations of doctors and nurses. Not me specifically, but I've been around the medical profession all my life from assorted relatives. ;) The human body is capable of all sorts of incredible things.

Simple logic. In order to generate the necessary momentum to produce such speeds the loadstress in all articulations increases exponentially. The increased momentum will transfer to the ground via the legs, the back takes a increased weight impact. Since the spine in it's design is not yet fully evolved for proper bipedal motion (it's basically just quadriped spine moving on two legs) it'll suffer the loads badly.

As increased wear and tear speed up the celldivision your reserves of telomeres run out quickly resulted in speeded degeneration.

In other words: you can run your car at full speed all the time, but the changes you'll end up in the repairshop are higher than if you just keep it at it's cruising speed.

It's funny how the researchers say it's possible, but the "experts" here are saying it's not.

If the common acceptance was that the force required to run at top speed for athletes was already at the limit and they proved it is not, then how can you be so sure that the same is true for the spine. How do you know that the spine can't handle more than you "think" it can?

Telomere: the segment of DNA that occurs at the ends of chromosomes.

How exactly would running affect your DNA? You use a bunch of big words to sound smart, but in reality, what you say makes no sense.

Sprinters don't run at full speed all the time, so your car analogy is worthless as well. You should have compared it to a drag car. That would work, except drag cars need to be built in preparation to run, just like runners train for their meets months in advance. Do drag cars have problems after a race, some do, but the majority are ready to go for the next heat an hour later. Same thing with sprinters.

Sorry mate. You might be widely educated in a broad range of topics (or read Wikipedia a lot), but I'm gonna go with a family history of several generations of doctors and nurses.??Not me specifically, but I've been around the medical profession all my life from assorted relatives. ;)??The human body is capable of all sorts of incredible things.

You go wherever you want, i'll just go with simple statistics of injuries and mortality rates associated with sports. I've had this discussion in my blog already if you want i can show you were to start reading the comments so i don't have to repeat it here but the gist of it is that emergency hospital intake is overrepresented by sports injuries.

It's funny how the researchers say it's possible, but the "experts" here are saying it's not.

If the common acceptance was that the force required to run at top speed for athletes was already at the limit and they proved it is not, then how can you be so sure that the same is true for the spine. How do you know that the spine can't handle more than you "think" it can?

Telomere: the segment of DNA that occurs at the ends of chromosomes.

How exactly would running affect your DNA? You use a bunch of big words to sound smart, but in reality, what you say makes no sense.

Sprinters don't run at full speed all the time, so your car analogy is worthless as well. You should have compared it to a drag car. That would work, except drag cars need to be built in preparation to run, just like runners train for their meets months in advance. Do drag cars have problems after a race, some do, but the majority are ready to go for the next heat an hour later. Same thing with sprinters.

Well i can say it in less smart words if you want:

The repair capacity of the mammal body is limited. DNA damage gets repaired with the aid of pieces of building kit to repair it. It's the bodies way of compensating for the inevitable loss of information when cells divide. This building kit is not that well stocked. The more you call on its resources the less the loss of information gets compensated until when it is empty the cell dies off.?

Nature has no use for your body after you procreated, since you'd be only using resources to the cost of the offspring leading to smaller chances of survival of the species. So bodies are made to last for a limited time. This regulated via the mechanism of DNA repair.?

Consequently, if you live 'faster' you die 'faster' since the allowed count of cell division gets used up in a shorter time frame.

<snip>

I think the main issue people have with your argument is that sprinters aren't doing so all the time. Most of the time they're about as active as other people.

They might run a few times a week, but it's not continuous. Certainly athletes have issues with wear and tear, but I don't expect it would suddenly become widely catastrophic once we reach some arbitrary point. 50 years ago you might have thought Bolt-like speeds would have surpassed this point, but evidently he has not.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
    • Tor Browser 15.0.17 by Razvan Serea Protect your privacy. Defend yourself against network surveillance and traffic analysis. Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. The Tor software protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody from watching your Internet connection and learning what sites you visit, it prevents the sites you visit from learning your physical location, and it lets you access sites which are blocked. The Tor Browser Bundle lets you use Tor on Windows, Mac OS X, or Linux without needing to install any software. It can run off a USB flash drive, comes with a pre-configured web browser to protect your anonymity, and is self-contained. Tor Browser 15.0.17 changelog: All Platforms Updated Tor to 0.4.9.11 Updated NoScript to 13.6.25.1984 Build System / All Platforms Bug tor-browser-build#41821: Update gpg subkeys for boklm Bug tor-browser-build#41827: Update morgan's keychain with renewed key Download: Tor Browser (64-bit) | Tor Browser (32-bit) | 109.0 MB (Open Source) View: Tor Browser Website | Other Operating Systems Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      530
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      148
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!