Now let's address your latest comment. The Army is not interested in the A10. Please now defend to me why if the Army feels that the A10 is not worth the cost of the A10 to protect ground troops in their own budget why the AF should keep it in their inventory?
Honestly, you just proved the argument of why the A 10 should be boneyarded. The Army that calls in CAS has faith in the 35. They aren't fighting for the A10 and will not invest in it. It is the Army that will have troops at risk, not the AF.
I'm not sure why you've decided to go on one of your trademark pointed diatribes toward me, but I'll gladly answer the question.
You're conflating two very different issues. You assume that the Army is not interested in the capability. That is not true. What the Army is not interested in is a program that it could in no possible way afford. The Army, thanks to sequestration and ongoing budget reductions, cannot afford the aircraft it currently owns. Hence the massive Aviation Restructuring Initiative (ARI) through which the Army is currently suffering. Add to that, the Army currently must find a way to divest an additional 70,000 troops. You speak as though this is a matter of two rich misers arguing over who should pick up the check. That is hardly the case.
Furthermore, you also speak as though this is some simple case of a child demanding a toy, and the parent saying "if you want it, you pay for it." This is not just an issue of a piece of equipment. Legalities aside, even if the Army could accept the A-10, what would the Army do with it? The Army has no hangar space for A-10s. The Army has no maintenance facilities for A-10s. Nor maintenance units. Nor a fixed-wing jet pilot school. Nor a logistics chain for the A-10. In short, the Army lacks every single element of the DOTMLPF domain required to support the integration of the A-10. To create such an architecture would cost many multiples of what it would cost the Air Force to keep the A-10, plus the Army would still have an aging air fleet on its hands.
The question is a two-part issue, and that's what you're failing to recognize. If you ask the Army "Should we keep the A-10?", that is a capabilities question and the Army will approach it from a capabilities standpoint. The Army will likely say yes, because the Army needs the CAS capability (a capability for which the Air Force is the executive agency, but more on that in a minute). If you ask the question "Should we keep the A-10 or replace it with something else?" the question will likely be answered with "it depends what that something else is and what it can do for troops in contact."
If the question is "how should we pay for the A-10?" the Army will respond "that's your problem, not ours, we don't manage your budget." Fortunately that is not the question at hand, but it does bring us to the dichotomy of the great A-10 question:
Is it worth having, and how does the Air Force pay for it if it is worth having? The former is a resounding yes. The latter half is much murkier. The issue the Air Force is facing, as we all know, is whether the famed replacement will actually deliver.
To illustrate the point, consider it from the other perspective. Say the Army was planning to mothball the M1 Tank. "But we have a replacement!" the Army says. "It's the Stryker MGS. It's not as survivable, lethal, or reliable as the M1, but that's the choice we made because it's newer and a jack of more trades." If we were to ask GEN Breedlove, the EUCOM commander, whether the Army should have the M1 tank, his answer would be a resounding yes. If we were to ask him how the Army should pay for it, he'd likely say "not my problem, but they need to." The Army's answer should not be the one you just gave, i.e. the petulant "well if you want that capability on the battlefield so badly, why don't YOU pay for it?" That ain't how it works. Similarly, if the Army said it was mothballing the Blackhawk, it should not expect the Air Force to suddenly become the executive agent billpayer for a new CSAR helicopter platform (though admittedly helicopters are slightly more muddled territory).
The Army is the Executive Agency and PM for armored vehicles. As such, the Army is the armored
capability provider to the joint force by developing and funding the M1 tank for the Army and the tiny USMC armored force. (Remember, one team, one fight, as you like to remind us). The Army cannot abdicate that role. Nor can the Army just abandon the M1 without a suitable replacement for the capability, lest it put the joint force at risk. And joint force commanders would be right to chastise the Army for attempting to do so.
The Air Force demanded to be the Exec. Agency for all land-based/non-naval fixed wing offensive capability. That includes CAS. The Air Force's real problem in this situation is that they have not sufficiently convinced the joint community that the F-35 will be a viable CAS platform replacement for the A-10. I can't say whether it will turn out to be or not, but that's the issue among the services.
The answer is for the Air Force to maintain the same high quality of CAS they've provided with the A-10, and to do so without interruption. The answer is not to demand that the Army do the Air Force's job and create A-10 squadrons in the Army.