What’s in the Air Force A-10’s Future?
Posted on March 16, 2017
One of the most contentious issues in the defense budget debates over the last three years has been the fate of the Air Force’s A-10 attack jet—a.k.a “the warthog.”
Will (or should) the A-10 survive to fight another day? Today’s WatchBlog looks at the trade-offs involved in divesting from the A-10.
Tough questions for the Air Force
The A-10 was originally built in the late 1970s to provide close air support—direct support to ground troops—and defeat enemy forces.
Today, the A-10 is not the only aircraft that can provide close air support for friendly forces (as shown in the figure).
(Excerpted from GAO-16-816)
Given these alternatives, and facing a lower-than-expected budget level, the Air Force argued that retiring the A-10 to prioritize modern aircraft—though not optimal—was the best option. In the Air Force’s view, an earlier-than-planned A-10 retirement was the best way to cut costs, and the least risky.
However, A-10 proponents have argued that it is the most effective and least expensive aircraft for the job. Moreover, the A-10 capabilities stand out in bad weather, when enemy forces are close or moving, and when targets are armored, according to Air Force and other officials familiar with the A-10. In addition, A-10 pilots are considered the Air Force’s close air support experts due to the amount and depth of their training in this mission, which significantly exceeds that of other Air Force pilots. Current uses of the A-10 DOD also uses the A-10 for more than just close air support missions. For example, Air Force analysis indicates that the A-10 is the best Air Force aircraft for countering swarming boats. Further, the A-10 is currently the only DOD aircraft assigned to the “Sandy” role in Combat Search and Rescue (CSAR) missions. When personnel are trapped behind enemy lines, CSAR-Sandy qualified pilots- coordinate and lead the rescue mission,
- escort the rescue helicopters, and
- suppress enemy forces during the mission.
(Excerpted from GAO-16-816)
- Questions on the content of this post? Contact John Pendleton at PendletonJ@gao.gov.
- Comments on GAO’s WatchBlog? Contact blog@gao.gov.