jojo a écrit :Un moteur qui fait cramer l'avion c'est pas juste un problème logiciel.
De plus ils étaient assez charette pour développer l'avion. Une des solutions étaient de faire grandir la flotte pour pouvoir mener plus de tests simultanément. Alors là que tous les F-35 soient cloués au sol ça ne fait pas leurs affaires du tout. C'est vraiment sérieux.
Pour la mise en service en 2016 on est d'accord (s'ils ne prennent pas trop de retard avec le moteur)
Mais comme les autres, ce sera incrémental.
Des défaillances moteurs graves il y'en a eut aussi avec le F-16 .
Comme le moteur du F-35 est une nouvelle conception, pas étonnant de voir réapparaitre des problèmes
Nov 1989 [i/a] 78002 78-0002 [USAF] USAF 310 TFTS F-16A Block 1 Details
Engine turbine failed during a take-off roll sending pieces of the turbine blades through the fuel cell. Pilot aborted take off after seeing the fire light and shut down the engine. After the pilot opened the canopy and jumped out found the entire tail of the F-16 on fire. The aircraft was sent to depot but was never repaired.
26 Mar 1980 [w/o] 78023 78-0023 [USAF] USAF 16 TFTS F-16A Block 5 Details
Destroyed in a fire due to an engine failure that sent some turbine parts through the main fuel cells. The pilot, who's last name as Bell, was from the Operational, Test & Evaluation squadron but using 388th TFW aircraft ejected safely after trying to restart the engine. The fact that the aircraft did not blow up was a relief to some early pilots as they were not convinced that the new designed fuel cells would perform as advertised. The fuel cells are sealed partitions in the fuselage. However, the major concern was about the fly by wire flight control system and what happened if the power was totally lost if the flight controls went "stupid". It was well understood that loss of flight controls could cause 20 Gs in less than a quarter of a second. Pilot DW Bells ejected safely.
http://www.f-16.net/aircraft-database/F ... force/USAF
