Estimate 1/4-mile elapsed time and trap speed
Use vehicle weight and power to predict drag race performance with Huntington, Fox, or Hale empirical equations.

This Quarter Mile Calculator estimates two drag racing staples: Elapsed time (ET) and Trap speed over a 1/4-mile (402.3 m) run. You provide a vehicle’s Weight and Power, and the calculator returns a first-order performance estimate using one of three well-known empirical formula families.
🎯 What it helps with: planning a target Elapsed time, estimating the impact of a power upgrade, and seeing how weight reduction might translate into faster runs — without needing a full vehicle dynamics model.
Who typically uses this?
If you’re browsing other tools, the “Related Calculators” section on this page is a handy way to chain calculations (for example: unit conversions, physics calculators, and other performance estimators).
You can use this calculator in two directions: predict Elapsed time + Trap speed from Weight + Power, or estimatePower from a measured run (Elapsed time or Trap speed) and a known Weight.
Pick an equation (Huntington, Fox, or Hale)
If you’re unsure, Fox is a solid default. Huntington is the classic early version, and Hale tends to predict slightly quicker Elapsed times for the same power-to-weight.
Enter vehicle Weight (include the driver)
Use the weight you actually race at. A quick way to be “close enough” is curb weight + driver + fuel + any track-day gear.
Enter Power
Use horsepower (hp) if you have it, or enter kilowatts (kW) and let the calculator convert. For best results, use the power available during the run (drivetrain losses, heat soak, and tune all matter).
Read the results (Elapsed time + Trap speed)
Example input: 3,400 lb and 450 hp (Fox)
Output (estimate): Elapsed time ≈ 12.30 s and Trap speed ≈ 117 mph
How to interpret the numbers
The core of drag racing performance lies in the relationship between Power and Weight. This is expressed as the Power-to-Weight Ratio (PWR).
Power-to-Weight Ratio measures how much power is available to move each unit of the vehicle's mass. In our calculator, we display this in two common formats:
A higher PWR means the engine has less weight to push, leading to faster acceleration (lower Elapsed time) and higher top speeds (Trap speed). All the formulas used in this calculator (Huntington, Fox, Hale) are essentially different mathematical models of how PWR translates into 1/4 mile performance.
All three options use the same basic shape: Elapsed time scales with the cube root of Weight-to-Power, and Trap speed scales with the cube root of Power-to-Weight. These formulas are mathematical models of how the Power-to-Weight Ratio (PWR) translates into acceleration over a fixed distance.
Core form used by all three
ET = k × (W / P)1/3
Trap Speed = c × (P / W)1/3
Where W is Weight (lb), P is Power (hp), ET is in seconds, and Trap speed is in mph. The term P / W is your Power-to-Weight Ratio.
Variables, in plain English
The equations are traditionally expressed in lb and hp, but this calculator accepts metric units too and converts internally.
Huntington’s approach is the classic “fit the data” method: measure many real cars, plot performance versus power-to-weight, and capture the trend with a simple curve. It’s old-school, but still useful as a baseline.
Huntington
ET = 6.290 × (W / P)1/3
Trap Speed = 224 × (P / W)1/3
✅ When it’s handy: quick comparisons between vehicles or “before vs after” checks when you change only one thing (Power or Weight).
Fox revisited the same idea with a more physics-minded lens: weight and power dominate the story, but traction, aero drag, gearing, and drivetrain losses can move the real result around — especially ET.
Fox
ET = 6.269 × (W / P)1/3
Trap Speed = 230 × (P / W)1/3
A practical takeaway
If you’re trying to “back-calculate” Power from a real run, Trap speed is often less sensitive to launch technique than Elapsed time. That’s why many people treat Trap speed as the more reliable indicator of Power.
Hale’s work is associated with more detailed software models, but the simplified equations are popular because they stay easy to use. Compared to the other two, Hale often predicts a shorter Elapsed time for the same power-to-weight.
Hale
ET = 5.825 × (W / P)1/3
Trap Speed = 234 × (P / W)1/3
⚠️ Sanity check: if Hale’s Elapsed time looks “too quick to be true,” it may be because your real-world setup is traction-limited or Power falls off before the finish.
Let’s run the same car through all three formulas so you can see the “spread.” The goal isn’t to crown a single winner — it’s to understand the range these estimates can produce.
Example inputs
| Equation | Elapsed time (s) | Trap speed (mph) | How it tends to feel |
|---|---|---|---|
| Huntington | ≈ 12.35 | ≈ 114 | Classic baseline |
| Fox | ≈ 12.30 | ≈ 117 | Good modern default |
| Hale | ≈ 11.43 | ≈ 119 | Often the “optimistic” ET |
If all three are clustered, your estimate is probably stable. If they spread apart (especially Elapsed time), treat the result as a range and lean on Trap speed for a power-focused check.
Background: you’re aiming for a 12-second slip.
Inputs: 3,000 lb and (reverse) Elapsed time = 12.0 s (Fox).
Result: power estimate ≈ 428 hp.
Use it to decide whether you need more power or less weight.
Background: adding a tune and intercooler.
Inputs: 3,400 lb; power from 380 → 450 hp.
Result: Elapsed time and Trap speed both improve.
Use it to check if the upgrade is “worth it” for your goal.
Background: removing 150 lb (wheels, seats, spare tire).
Inputs: same power; weight 3,300 → 3,150 lb.
Result: quicker Elapsed time and slightly higher Trap speed.
Use it to compare “pounds saved” versus “hp gained.”
Background: dyno says 520 hp, but the slip feels slow.
Inputs: race weight + measured trap speed.
Result: reverse-solved power may highlight drivetrain loss or heat soak.
Use it as a quick reality check.
Background: two cars have very different weights.
Inputs: both cars’ weight + power.
Result: Elapsed time / Trap speed estimates on the same scale.
Use it to compare “potential” before launch skill and traction enter the picture.
Use race weight, not brochure weight
Driver weight, fuel, wheels/tires, and gear can add up. If you’re off by 200 lb, the estimate won’t be “wrong” — it will be answering a different question.
Prefer trap speed for “power checks”
ET is very sensitive to launch. Trap speed usually reflects sustained acceleration and power more consistently.
Be honest about usable power
Peak dyno power is great — but if the car can’t hold it (heat, boost taper, shift points), real Elapsed time may be slower.
Treat results as a range
Different equations and real-world conditions can move the outcome. If two formulas disagree, that’s a useful signal — not a bug.
Key terms you’ll hear at the track
🧠 A good mental model: Trap speed answers “how hard did the car pull overall,” while Elapsed time answers “how cleanly did everything happen, especially at the start.”
If you want a simple default, start with Fox. Then toggle Huntington and Hale to see the range. If your build is traction-limited, Hale’s Elapsed time may be optimistic.
Either can work — just be consistent. If you enter crank hp (advertised power), results can look faster than reality because drivetrain losses aren’t explicitly modeled.
Common reasons include traction limits, conservative shifting, heat soak, altitude/weather, or using a weight that’s lighter than your real race setup.
Yes. Enter your vehicle Weight, then enter either Elapsed time or Trap speed and let the calculator solve for Power. Trap speed is often a smoother signal than Elapsed time.
Definitely. The formulas assume total moving Weight. Driver, fuel, and anything in the car during the run all count.
They use the same cube-root relationship but different fitted constants. Think of them as slightly different “calibrations” from different eras and datasets.
It depends on the class and the vehicle. Use this calculator to compare your build against your own goals (before/after mods) rather than chasing a universal number.
Not explicitly. That’s the tradeoff for a quick estimator. Those factors are why real runs can differ from the prediction.
External references (for deeper reading)
Note: These formulas are widely circulated in motorsport contexts. The calculator uses the published constants as implemented in the equation selector.
Have a look at the flight path of the object with this trajectory calculator.
Calculate free fall parameters including gravitational acceleration, drop height, fall duration, and impact velocity. Supports bidirectional LRU solving with unit conversions.
Calculate free fall with quadratic air drag, including terminal velocity, fall time, maximum velocity, and drag force. Supports air resistance coefficient calculation from object properties.
Calculate the horizontal range of a projectile based on velocity, angle, and initial height. Supports bidirectional calculation with multiple unit systems.
Calculate projectile trajectory parameters including launch velocity, angle, distance, maximum height, and flight time with bidirectional solving.
Use this maximum height calculator to figure out what is the maximum vertical position of an object in projectile motion.