- 31/07/2011
Vitaly Petrov Post-Hungarian GP Video...
- 31/07/2011
A little drizzle out east
- 30/07/2011
Bruno Senna video diary - Budapest
TAGS CLOUD
-->We caught up with our technical director James Allison in order to discover what really went wrong on Nick's car last Sunday.
Four days after the incident on Nick's car, has the team identified the reason why it caught fire after the pitstop?
J.A.: As with most accidents, several incidents combined to cause the fire that Nick suffered in Hungary. First of all, we ran a slightly different engine mapping strategy in qualifying, which produced hotter than normal exhausts. We believe that this elevated temperature and caused a preliminary crack in the exhaust pipe. We presume that the crack then propagated during the laps to the pitstop - this was not evident to us as we believe that the failure occurred upstream of the place where we have a temperature sensor. We believe that Nick then came in with a partially failed exhaust. This pitstop took longer than normal, the engine was left at high rpm for 6.3 sec, waiting for the tyre change to be completed. Under these conditions, a lot of excess fuel always ends up in the exhausts and their temperature rises at around 100°C/sec. This temperature rise was enough to finish off the partially failed pipe and to start a moderate fire under the bodywork.
There was an explosion shortly after Nick got out of the car. What was it?
J.A.: This was caused by the air bottle which supplies the air valves in the engine. It has overheated in the fire and failed.
Will you have to modify the car before Spa and if yes, is the August factory shutdown a problem to do so?
J.A.: The incident was highly undesirable, as it has caused us to write off a chassis. We will take steps prior to the next race to reduce the likelihood of a further fire and to ensure that the air bottle cannot overheat. We are in touch with the FIA both to provide them with a full report of the incident and also to explain to them the actions we are taking to prevent a reoccurrence.
Please enable JavaScript to view the comments powered by Disqus. blog comments powered by Disqus
No comments:
Post a Comment