← My Auto Racer All cars Panoz 0-60 Comparisons
The Panoz AIV Roadster reaches 60 mph in 4.41 s and covers a standing quarter mile in 12.79 s, tripping the lights at 107.5 mph. It clears the first 60 ft in 1.90 s and the eighth mile in 8.23 s, reaching 100 mph in 10.50 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.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Panoz AIV Roadster |
|---|---|
| 0–60 mph | 4.41 s |
| 0–100 mph | 10.50 s |
| 60 ft | 1.90 s |
| 1/8 mile | 8.23 s |
| 1/4 mile | 12.79 s |
| Trap speed | 107.5 mph |
The 2000 Panoz AIV Roadster is a rear-drive naturally aspirated roadster of 1,167 kg with 304 bhp, which works out at 261 bhp per tonne. Rear drive and 261 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.90 s. Against the 2,929 cars in the set it is the 1,048th quickest to 60 mph, and the 2nd quickest of the 3 Panozs here. Its 107.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 5 of 7 published acceleration figures for this car.
| Specification | Panoz AIV Roadster |
|---|---|
| Year | 2000 |
| Power | 304 bhp |
| Kerb mass | 1,167 kg |
| Power to weight | 261 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 253 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Porsche 718 Boxster | 2016 | 4.30 s | 12.92 s | 107.6 mph | 296 bhp |
| Mercedes-Benz S63 AMG W221 | 2006 | 4.49 s | 12.79 s | 110.0 mph | 518 bhp |
| Rolls-Royce Wraith | 2013 | 4.56 s | 12.70 s | 113.9 mph | 624 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.
Figures regenerated 2026-09-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.