← My Auto Racer All cars Acura 0-60 Comparisons Answers

Acura MDX 3.7 V6 300 (2006)

The Acura MDX 3.7 V6 300 (2006) reaches 60 mph in 6.75 s (100 km/h in 7.37 s) and covers a standing quarter mile in 15.40 s, tripping the lights at 91.5 mph. It clears the first 60 ft in 2.62 s and the eighth mile in 10.02 s.

Simulated, not measured — computed from published kerb mass, rated power, gearing and drivetrain, then fitted to this car’s own published acceleration figures. Dry asphalt, 20 °C, sea level, 1 ft rollout.

Acura MDX 3.7 V6 300 (2006) Chrysler Aspen 5.7 V8 2WD 335

Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.

Down the strip

Standing start Acura MDX 3.7 V6 300 (2006)
0–60 mph6.75 s
0–100 km/h7.37 s
0–100 mph—
60 ft2.62 s
1/8 mile10.02 s
1/4 mile15.40 s
Trap speed91.5 mph

About the MDX 3.7 V6 300

The 2006 Acura MDX 3.7 V6 300 (2006) is an all-wheel-drive naturally aspirated SUV of 2,059 kg with 300 bhp, which works out at 146 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.62 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 4,240th quickest to 60 mph, and the 16th quickest of the 25 Acuras here. Its 91.5 mph trap speed sits about where its 0-60 puts it, so it launches and pulls in roughly equal measure. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Acura MDX 3.7 V6 300 (2006)
Year2006
Power300 hp (224 kW)
Kerb mass2,059 kg
Power to weight146 bhp/t
DrivetrainAll-wheel drive
Gears5
EngineNaturally aspirated
Top speed130 mph (209 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Chrysler Aspen 5.7 V8 2WD 33520066.77 s15.32 s90.5 mph335 bhp
Cadillac SRX 3.0 V6 26520096.75 s15.33 s92.7 mph266 bhp
Lexus LX 570 V8 38320126.76 s15.28 s90.7 mph384 bhp

Picked for a fair race, not just a matching 0-60: pace, power-to-weight and body shape all count, and at most one is from the same maker.

Where these times sit

0-60 under 7 seconds4,651 cars0-100 km/h under 8 seconds5,602 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Acura 0-60 timesevery modelFastest SUVs2,049 carsFastest cars of the 2000s5,138 cars
Put this race on your own page

Free to use anywhere, no attribution required beyond the credit line included above. How to embed →

Questions

What is the Acura MDX 3.7 V6 300 (2006) 0-60 time?
The Acura MDX 3.7 V6 300 (2006) reaches 60 mph in 6.75 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 4,240th quickest of the 14,946 cars in the set.
What is the Acura MDX 3.7 V6 300 (2006) quarter mile time?
15.40 s at 91.5 mph. It reaches the eighth mile in 10.02 s and clears the first 60 ft in 2.62 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Acura MDX 3.7 V6 300 (2006) have?
300 bhp and 2,059 kg, which is 146 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 5 gears and a quoted top speed of 209 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Acura MDX 3.7 V6 300 (2006)?
Closest here on pace: Chrysler Aspen 5.7 V8 2WD 335 (6.77 s), Cadillac SRX 3.0 V6 265 (6.75 s), Lexus LX 570 V8 383 (6.76 s). Each one can be raced against the Acura MDX 3.7 V6 300 (2006) in the panel at the top of this page. These are theoretical times from a physics simulation, not measured runs.
Are these real measured times?
No. Every figure on this page is produced by a physics simulation, not by a stopwatch at a drag strip. The Acura MDX 3.7 V6 300 (2006) is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 2 of its 2 published acceleration figures. Conditions are the same for every car in the set: dry asphalt, 20 °C, sea level, 1 ft rollout.

Figures regenerated 2026-10-12. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.