← My Auto Racer All cars Ford 0-60 Comparisons
The Ford Mustang Boss 302 LS reaches 60 mph in 4.01 s and covers a standing quarter mile in 12.55 s, tripping the lights at 113.9 mph. It clears the first 60 ft in 1.99 s and the eighth mile in 8.13 s, reaching 100 mph in 9.97 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 | Ford Mustang Boss 302 LS |
|---|---|
| 0–60 mph | 4.01 s |
| 0–100 mph | 9.97 s |
| 60 ft | 1.99 s |
| 1/8 mile | 8.13 s |
| 1/4 mile | 12.55 s |
| Trap speed | 113.9 mph |
The 2012 Ford Mustang Boss 302 LS is a rear-drive naturally aspirated muscle car of 1,652 kg with 437 bhp, which works out at 265 bhp per tonne. Rear drive and 265 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.99 s. Against the 2,929 cars in the set it is the 802nd quickest to 60 mph, and the 5th quickest of the 109 Fords here. Its 113.9 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 8 of 10 published acceleration figures for this car.
| Specification | Ford Mustang Boss 302 LS |
|---|---|
| Year | 2012 |
| Power | 437 bhp |
| Kerb mass | 1,652 kg |
| Power to weight | 265 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 293 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Chevrolet Camaro SS Mk VI | 2016 | 4.10 s | 12.45 s | 114.9 mph | 447 bhp |
| Hsv Coupe GTO VZ | 2004 | 4.15 s | 12.73 s | 112.1 mph | 398 bhp |
| Benarrow PB5 | 2010 | 4.07 s | 12.56 s | 113.9 mph | 499 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.