backtop


Print 44 comment(s) - last by lagomorpha.. on Feb 21 at 2:28 PM

Boeing thinks the EA-18 Growler is the most likely version to be purchased by the US

One of the staples U.S. Navy for a number of years has been the F/A-18 E/F Super Hornet fighter. However, reports indicate that the new U.S. defense budget that is set to be unveiled next month has no allowance for purchasing new versions of the fighter.
 
New purchases of the electronic attack version called the EA-18G Growler are also nonexistent. Some in Washington want to continue to purchase the aircraft with a $75 million defense appropriations bill that would call for the purchase of 22 new aircraft. Boeing, the maker of the Super Hornet, also wants the military to purchase more EA-18G aircraft.

 
The Hornet has been around since the 1970's and replaced the F-14 Tomcat and A-6 Prowler. When the last orders are completed, the Navy will have 563 Super Hornets and 138 Growlers. The current orders will have production of the aircraft continuing through 2016.
 
Boeing says that 90,000 full time jobs around the country are dependent on Super Hornet production, and the company is currently shopping the jet to foreign nations now. Boeing had hoped to court Brazil with the purchase of 36 Super Hornets, but concerns over the NSA’s spying program led the Latin American country into the arms of Sweden and its Saab JAS-39 Gripen NG.
 
The existing Super Hornets will be supplemented by the troubled (and expensive) F-35 Lightning II for U.S. Navy duties.

Source: Defense News



Comments     Threshold


This article is over a month old, voting and posting comments is disabled

By gamerk2 on 2/18/2014 2:21:19 PM , Rating: 2
To be fair, only the last two models of the 52 (made in the 70's) are still flying; the older airframes are all retired.


"People Don't Respect Confidentiality in This Industry" -- Sony Computer Entertainment of America President and CEO Jack Tretton














botimage
Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki