{"id":70264,"date":"2008-10-09T16:19:33","date_gmt":"2008-10-09T16:19:33","guid":{"rendered":"https:\/\/new.dedefensa.org\/index.php\/2008\/10\/09\/lus-navy-fait-elle-partie-du-complot-anti-jsf\/"},"modified":"2008-10-09T16:19:33","modified_gmt":"2008-10-09T16:19:33","slug":"lus-navy-fait-elle-partie-du-complot-anti-jsf","status":"publish","type":"post","link":"https:\/\/new.dedefensa.org\/index.php\/2008\/10\/09\/lus-navy-fait-elle-partie-du-complot-anti-jsf\/","title":{"rendered":"L&rsquo;U.S. Navy fait-elle partie du complot anti-JSF?"},"content":{"rendered":"<p><p>Manifestement, l&rsquo;U.S. Navy  ne croit pas que le JSF est un chasseur universel, suffisant pour rencontrer ses besoins en mati\u00e8re d&rsquo;avion de combat embarqu\u00e9 dans les trois ou quatre d\u00e9cennies \u00e0 venir. Des d\u00e9clarations du Chief of Naval Operations, l&rsquo;amiral Gary Roughead, faites \u00e0 <em>Navy Times<\/em> et \u00e0 <em>Defense News<\/em>, montrent que la Nacvy entend bien disposer de <strong>deux<\/strong> types d&rsquo;avion de combat, y compris apr\u00e8s le retrait des actuels <em>Hornet<\/em> et <em>Super Hortnet<\/em> (F\/A-18 et F\/A-18E). C&rsquo;est le type de situation que d\u00e9testent les crois\u00e9s du programme JSF, car ce programme est b\u00e2ti sur l&rsquo;id\u00e9e qu&rsquo;il n&rsquo;y a pas d&rsquo;alternative \u00e0 lui-m\u00eame (ou TINA: <em>There Is No Alternative<\/em>, ce qui pourrait donner en fran\u00e7ais, INAPA, acronyme dont on avouera qu&rsquo;il a un \u00e9cho significatif: Il N&rsquo;y A Pas d&rsquo;Alternative). Ils voient donc des <a href=\"http:\/\/www.dedefensa.org\/article-un_complot_contre_le_jsf_23_09_2008.html\" class=\"gen\">complots<\/a> partout et rien ne dit qu&rsquo;ils aient tort.<\/p>\n<\/p>\n<p><p>\tDans ses d\u00e9clarations, Roughead annonce que la Navy va entreprendre l&rsquo;\u00e9tude et le d\u00e9veloppement d&rsquo;un avion de combat de la 6\u00e8me g\u00e9n\u00e9ration (le JSF \u00e9tant \u00e9tiquet\u00e9 dans la 5\u00e8me g\u00e9n\u00e9ration), vaguement pr\u00e9sent\u00e9 pour les ann\u00e9es 2020. Selon <em>Defense News<\/em> du <a href=\"http:\/\/defensenews.va.newsmemory.com\/default.php?type=&#038;token=528bfbc690487ae8d374df84e85a0e2d&#038;pSetup=defensenews_intl&#038;goTo=001&#038;date=20080929\" class=\"gen\">29 septembre<\/a>:<\/p>\n<\/p>\n<p><p>\t\u00ab<em>The U.S. Navy&rsquo;s top officer is committed to keeping 11 aircraft carriers in service and ultimately stocking them with a mix of Su per Hornet and Joint Strike Fighter aircraft. What I envision in the future is to have a mix of F-18 Super Hornets and [F-35] Joint Strike Fighters, Adm. Gary Roughead, chief of naval operations (CNO), told a group of Defense News and Navy Times editors and reporters Sept. 26.<\/em><\/p>\n<\/p>\n<p><p>\t\u00bb<em>When Super Hornets phase out, they will be replaced with sixth-generation fighters to be developed in the 2020s, Roughead said. We need to position ourselves so we always have a mix of airplanes. The Navy is working to address a so-called fighter gap beginning in 2015, when older model F\/A-18 Hornet aircraft will be retiring faster than new F-35C carrier strike fighters will arrive to replace them. The shortfall occurs from 2015 to 2025, with the gap at its widest  69 planes  in 2017.<\/em><\/p>\n<\/p>\n<p><p>\t\u00bb<em> Roughead said the Navy continues to study its options on how to solve the shortage, which essentially consist of speeding up F-35 production or buying more Super Hornets.  There have been some that have said that if we continue with<\/em> [Super] <em>Hornet produc tion, Roughead said, we would be block ing the way for the Joint Strike Fighter. That is not the case at all. I really do want our air wings to have more than one airplane. Flying fewer than the current 10 carrier air wings would also reduce the impact of the fighter gap, but Roughead said that option is not being considered.<\/em>\u00bb<\/p>\n<\/p>\n<p><p>\tL&rsquo;U.S. Navy fait-elle partie du complot, avec sa suspecte affaire de 6\u00e8me g\u00e9n\u00e9ration? Bien s\u00fbr que oui, puisque nous l&rsquo;\u00e9crivions m\u00eame en toutes lettres, le <a href=\"http:\/\/www.dedefensa.org\/article-le_complot_anti-jsf_de_la_sixieme_generation_03_04_2008.html?admin=1\" class=\"gen\">3 avril<\/a>: \u00ab<em>Le complot anti-JSF de la sixi\u00e8me g\u00e9n\u00e9ration.<\/em>\u00bb Disons que les choses se pr\u00e9cisent, et le complot avec.<\/p>\n<\/p>\n<p><p>\tCe que dit le CNO, c&rsquo;est qu&rsquo;il faut \u00e0 la Navy au moins deux mod\u00e8les d&rsquo;avions de combat diff\u00e9rents. (Chose peut-\u00eatre un peu surprenante si l&rsquo;on consid\u00e8re qu&rsquo;aujourd&rsquo;hui, l&rsquo;U.S. Navy n&rsquo;a que des <em>Hornet<\/em> et des <em>Super Hornet<\/em>,  \u00e0 moins que le CNO consid\u00e8re qu&rsquo;il s&rsquo;agit de deux mod\u00e8les, ce qui serait l&rsquo;objet de d\u00e9bats sans fin.) Cela implique que le <em>Super Hornet<\/em> reste certainement en service et plus ou moins en production en attendant l&rsquo;arriv\u00e9e du JSF et qu&rsquo;un autre avion devra entrer en production dans les ann\u00e9es 2020 pour compl\u00e9ter le JSF. On observera, ce qui est l&rsquo;essentiel du propos et du complot, que ces beaux projets permettraient ais\u00e9ment \u00e0 la Navy de se passer du JSF, en prolongeant la production du <em>Super Hornet<\/em> et en avan\u00e7ant celle du nouvel avion de combat, avec des solutions interm\u00e9diaires possibles comme celle, d\u00e9j\u00e0 mentionn\u00e9e dans un texte du <a href=\"http:\/\/www.dedefensa.org\/article.php?art_id=4886\" class=\"gen\">6 f\u00e9vrier<\/a>, d&rsquo;un <em>Super Hornet<\/em> de 4,75\u00e8me g\u00e9n\u00e9ration<\/p>\n<\/p>\n<p><p>\t\u00ab<em>Nous \u00e9voquons ici le d\u00e9but (d\u00e9veloppement, entr\u00e9e en service) de la cha\u00eene d&rsquo;ores et d\u00e9j\u00e0 calamiteuse du JSF. D&rsquo;autres \u00e9voquent la fin de cette cha\u00eene, pour avancer implicitement l&rsquo;argument que le JSF,  \u00e0 cause des d\u00e9boires du d\u00e9but de la cha\u00eene, justement,  est d\u00e9pass\u00e9 et qu&rsquo;il serait pr\u00e9f\u00e9rable d&rsquo;aller directement \u00e0 un successeur. Il s&rsquo;agit d&rsquo;une offre Boeing pour un avion de sixi\u00e8me g\u00e9n\u00e9ration (le JSF \u00e9tant labellis\u00e9 cinqui\u00e8me g\u00e9n\u00e9ration) qui permettrait de faire l&rsquo;\u00e9conomie du JSF, dans tous les cas pour l&rsquo;U.S. Navy.<\/em>\u00bb<\/p>\n<\/p>\n<p><p>\tEn d&rsquo;autres mots, la Navy est pr\u00eate \u00e0 tout, notamment \u00e0 se passer du JSF. C&rsquo;est une situation que le programme JSF d\u00e9teste par-dessus tout.<\/p>\n<\/p>\n<p><\/p>\n<p><p>\tMis en ligne le 9 octobre 2008 \u00e0 16h20<\/p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Manifestement, l&rsquo;U.S. Navy ne croit pas que le JSF est un chasseur universel, suffisant pour rencontrer ses besoins en mati\u00e8re d&rsquo;avion de combat embarqu\u00e9 dans les trois ou quatre d\u00e9cennies \u00e0 venir. Des d\u00e9clarations du Chief of Naval Operations, l&rsquo;amiral Gary Roughead, faites \u00e0 Navy Times et \u00e0 Defense News, montrent que la Nacvy entend&hellip;&nbsp;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","footnotes":""},"categories":[2],"tags":[7841,4926,4481,4711,250,3319,3487,7833],"class_list":["post-70264","post","type-post","status-publish","format-standard","hentry","category-bloc-notes","tag-6eme","tag-complot","tag-generation","tag-hornet","tag-jsf","tag-navy","tag-super","tag-tina"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/new.dedefensa.org\/index.php\/wp-json\/wp\/v2\/posts\/70264","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/new.dedefensa.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/new.dedefensa.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/new.dedefensa.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/new.dedefensa.org\/index.php\/wp-json\/wp\/v2\/comments?post=70264"}],"version-history":[{"count":0,"href":"https:\/\/new.dedefensa.org\/index.php\/wp-json\/wp\/v2\/posts\/70264\/revisions"}],"wp:attachment":[{"href":"https:\/\/new.dedefensa.org\/index.php\/wp-json\/wp\/v2\/media?parent=70264"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/new.dedefensa.org\/index.php\/wp-json\/wp\/v2\/categories?post=70264"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/new.dedefensa.org\/index.php\/wp-json\/wp\/v2\/tags?post=70264"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}