Have you ever wondered how expensive supercars get crash-tested? After all, many of these cars can cost millions of dollars apiece, so even crashing a single car can be absurdly expensive. Therefore, it’s no surprise that supercar manufacturers have developed some neat tricks to keep costs down.

A video by APEX ONE goes behind the scenes at supercar manufacturer Koenigsegg, and shows all the tricks and techniques the company uses to test its cars while keeping costs down:

This content is imported from YouTube. You may be able to find the same content in another format, or you may be able to find more information, at their web site.

In order to be sold in the U.S., Koenigsegg’s cars need to pass a bevy of crash tests, starting with front, rear, and side collisions. On top of that, the test car has to suffer a wide range of smaller impacts everywhere else. For a typical car manufacturer, this would cost a little over a dozen cars, for a total price of a few hundred thousand dollars. For Koenigsegg, a dozen cars is almost its entire yearly production and costs tens of millions.

So instead of throwing away more than a dozen cars on tests, Koenigsegg instead allocates only one car for testing, and simply repairs it after every test. Most of the damage sustained to the cars is only to the exterior panels, which are relatively cheap compared to other components. The most expensive part is the car’s chassis, which the team ensures survives every test.

Koenigsegg supplements this method with a series of crash simulations, where it uses real data from the tests it does run to predict the results of future tests, ensuring it only runs tests when the team is sure their cars will pass. The end result is that the company only smashes a single car for every production model, allowing Koenigsegg to stay in business.

Source: Jalopnik

This content is created and maintained by a third party, and imported onto this page to help users provide their email addresses. You may be able to find more information about this and similar content at piano.io