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

Honda Accord Aerodeck 2.2 145

The Honda Accord Aerodeck 2.2 145 reaches 60 mph in 10.10 s (100 km/h in 10.62 s) and covers a standing quarter mile in 17.88 s, tripping the lights at 83.4 mph. It clears the first 60 ft in 3.17 s and the eighth mile in 11.94 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.

Honda Accord Aerodeck 2.2 145 Chrysler Saratoga 3.0 V6 141

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 Honda Accord Aerodeck 2.2 145
0–60 mph10.10 s
0–100 km/h10.62 s
0–100 mph—
60 ft3.17 s
1/8 mile11.94 s
1/4 mile17.88 s
Trap speed83.4 mph

About the Accord Aerodeck 2.2 145

The 1993 Honda Accord Aerodeck 2.2 145 is a front-drive naturally aspirated saloon of 1,400 kg with 143 bhp, which works out at 102 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.17 s — so most of what it has to give arrives once it is already moving. Against the 14,946 cars in the set it is the 10,343rd quickest to 60 mph, and the 120th quickest of the 191 Hondas here. It traps higher than its 0-60 suggests — 83.4 mph, the 8,127th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Honda Accord Aerodeck 2.2 145
Year1993
Power143 hp (107 kW)
Kerb mass1,400 kg
Power to weight102 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed122 mph (196 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Chrysler Saratoga 3.0 V6 141198910.07 s17.91 s81.8 mph139 bhp
Chrysler Concorde 3.3 V6 153199310.06 s17.91 s81.6 mph153 bhp
Saab 9-3 2.3 150199810.12 s17.86 s84.3 mph148 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

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Honda 0-60 timesevery modelFastest saloon cars3,808 carsFastest cars of the 1990s2,649 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 Honda Accord Aerodeck 2.2 145 0-60 time?
The Honda Accord Aerodeck 2.2 145 reaches 60 mph in 10.10 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,343rd quickest of the 14,946 cars in the set.
What is the Honda Accord Aerodeck 2.2 145 quarter mile time?
17.88 s at 83.4 mph. It reaches the eighth mile in 11.94 s and clears the first 60 ft in 3.17 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Honda Accord Aerodeck 2.2 145 have?
143 bhp and 1,400 kg, which is 102 bhp per tonne. It is front-drive, naturally aspirated, with 4 gears and a quoted top speed of 196 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Honda Accord Aerodeck 2.2 145?
Closest here on pace: Chrysler Saratoga 3.0 V6 141 (10.07 s), Chrysler Concorde 3.3 V6 153 (10.06 s), Saab 9-3 2.3 150 (10.12 s). Each one can be raced against the Honda Accord Aerodeck 2.2 145 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 Honda Accord Aerodeck 2.2 145 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.