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

Chrysler Aspen 4.7 V8 2WD 303

The Chrysler Aspen 4.7 V8 2WD 303 reaches 60 mph in 7.59 s (100 km/h in 8.05 s) and covers a standing quarter mile in 16.00 s, tripping the lights at 86.2 mph. It clears the first 60 ft in 2.62 s and the eighth mile in 10.29 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.

Chrysler Aspen 4.7 V8 2WD 303 Infiniti QX60 3.5 V6 CVT 265

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 Chrysler Aspen 4.7 V8 2WD 303
0–60 mph7.59 s
0–100 km/h8.05 s
0–100 mph—
60 ft2.62 s
1/8 mile10.29 s
1/4 mile16.00 s
Trap speed86.2 mph

About the Aspen 4.7 V8 2WD 303

The 2006 Chrysler Aspen 4.7 V8 2WD 303 is a rear-drive naturally aspirated SUV of 2,224 kg with 303 bhp, which works out at 136 bhp per tonne. Rear drive and 136 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.62 s. Against the 14,946 cars in the set it is the 5,721st quickest to 60 mph, and the 25th quickest of the 76 Chryslers here. It leaves better than it pulls: 86.2 mph at the lights is only the 6,719th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Chrysler Aspen 4.7 V8 2WD 303
Year2006
Power303 hp (226 kW)
Kerb mass2,224 kg
Power to weight136 bhp/t
DrivetrainRear drive
Gears5
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Infiniti QX60 3.5 V6 CVT 26520167.61 s15.98 s84.6 mph261 bhp
Land Rover Freelander - LR2 2.0 Si4 GTDi 24020097.67 s15.98 s84.3 mph237 bhp
Dodge Nitro 4.0 25820067.67 s16.07 s85.7 mph255 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 8 seconds6,514 cars0-100 km/h under 10 seconds9,062 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Chrysler 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 Chrysler Aspen 4.7 V8 2WD 303 0-60 time?
The Chrysler Aspen 4.7 V8 2WD 303 reaches 60 mph in 7.59 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 5,721st quickest of the 14,946 cars in the set.
What is the Chrysler Aspen 4.7 V8 2WD 303 quarter mile time?
16.00 s at 86.2 mph. It reaches the eighth mile in 10.29 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 Chrysler Aspen 4.7 V8 2WD 303 have?
303 bhp and 2,224 kg, which is 136 bhp per tonne. It is rear-drive, naturally aspirated, with 5 gears and a quoted top speed of 180 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chrysler Aspen 4.7 V8 2WD 303?
Closest here on pace: Infiniti QX60 3.5 V6 CVT 265 (7.61 s), Land Rover Freelander - LR2 2.0 Si4 GTDi 240 (7.67 s), Dodge Nitro 4.0 258 (7.67 s). Each one can be raced against the Chrysler Aspen 4.7 V8 2WD 303 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 Chrysler Aspen 4.7 V8 2WD 303 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.