Jump to content

Recommended Posts

Posted (edited)

I am sure this is an obvious question, has been asked before but I cannot find it.

 

How come planes like the F/A-18, F/A-22, A-10 have the A because they can do attack, but what about the F-16? It can do attack really well (in Falcon 4 anyway) so why do they not call it the F/A-16?

 

Thanks for any replies.

Edited by Sceptre

RTX 2070 8GB | 32GB DDR4 2666 RAM | AMD Ryzen 5 3600 4.2Ghz | Asrock X570 | CH Fighterstick/Pro Throttle | TM MFDs | TrackIR 5

Posted

And I wonder about the F-117.

Asus Prime Z-370-A

Intel core I7-8700K 3.70Ghz

Ram g.skill f4-3200c16d 32gb

Evga rtx 2070

Ssd samgung 960 evo m.2 500gb

 

Syria, Nevada, Persian Gulf, Normandy 1944

Combined Arms

A-10C, Mirage-2000C, F-16C, FC3

Spitfire LF Mk. IX

UH-1H, Gazelle

Posted
I am sure this is an obvious question, has been asked before but I cannot find it.

 

How come planes like the F/A-18, F/A-22, A-10 have the A because they can do attack, but what about the F-16? It can do attack really well (in Falcon 4 anyway) so why do they not call it the F/A-16?

 

Thanks for any replies.

Bureaucracy and military politics really. The only active aircraft ever refer to "F/A" is the F-18. The F-22 was designated that way when the USAF was asking congress for more aircraft, when congress said not, they re designated the aircraft.

There is also

DOD directive 4120.15L

To whom it may concern,

I am an idiot, unfortunately for the world, I have a internet connection and a fondness for beer....apologies for that.

Thank you for you patience.

 

 

Many people don't want the truth, they want constant reassurance that whatever misconception/fallacies they believe in are true..

Posted

Thanks for clearing that up!

RTX 2070 8GB | 32GB DDR4 2666 RAM | AMD Ryzen 5 3600 4.2Ghz | Asrock X570 | CH Fighterstick/Pro Throttle | TM MFDs | TrackIR 5

Posted

NP

To whom it may concern,

I am an idiot, unfortunately for the world, I have a internet connection and a fondness for beer....apologies for that.

Thank you for you patience.

 

 

Many people don't want the truth, they want constant reassurance that whatever misconception/fallacies they believe in are true..

Posted

Over 20 years ago, the USAF looked at a modified F-16 called the A-16 to replace the A-10. Obviously, for once, the higher ups realized a 16 couldn't replace an A-10 for every mission and it was scrapped.

 

Interesting article at http://www.f-16.net/f-16_versions_article18.html although the last paragraph isn't correct.

 

A-16 Close Air Support

In the 1980's, the USAF started setting aside F-16s for the planned A-16 modification, a dedicated close air support version of the F-16. In 1989, the designation block 60 was reserved for the A-16. The A-16 Block 60 was to be equipped with a 30 mm cannon and provided with a strengthened wing structure for anti-tank weapons such as 7.62 mm min pods. This project failed because the 30 mm gun would heat up and senge the inner components of the left fuselage.

 

There were two block 15's that were converted to this modification; they were based at Shaw airforce base. The Block 60 did not go into production and the A-16 became wrapped up in the debate about close air support. The supporters of the A-16 project wanted the USAF to replace its A-10A Thunderbolt IIs with A-16's, arguing that the A-10 was too slow to survive above a high-tech battlefield. Detractors argued that the A-16 had insufficient range and load-carrying capability to make an effective attack aircraft, and, in addition, it would be too vulnerable to enemy anti-aircraft fire.

 

The Army argued that the Key West agreement of 1948 (under which they were prohibited from operating fixed-wing combat aircraft) was now obsolete, and that the USAF's A-10's should be turned over to them for use alongside AH-64 Apache helicopters. In 1990, Congress decreed that some USAF A-10A's and OV-10 Broncos be turned over to the Army and Marine Corps beginning in 1991.

 

However, all of these plans came to naught on November 26th, 1990, when the USAF was ordered to retain two wings of A-10 aircraft for the CAS mission. No order for the A-16 was ever placed.

 

F/A-16 block 30

On the same November 26th, 1990, when the USAF was forced to opt for the A-10 in stead of the A-16, the decision was made to retrofit up to 400 existing Block30/32 F-16C/D's with new equipment to perform the CAS (close Air Support) and BAI (Battlefield Air Interdiction) missions, effectively killing the A-16 program. Modifications would include a Global Positioning System (GPS), Digital Terrain System (DTS), system hardening, modular mission computer, and an Automatic Target Handoff System (ATHS).

 

A prototype Block 30 (although still with the A-model HUD and the slim tail base) was based at Shaw AFB and went through numerous physical adjustments. Official designation, much like the Hornet, was to be F/A-16. In January 1992, this plan too was abandonned in favor of using LANTIRN-equipped Block40/42 F-16C/D's.

 

F/A-16A & F/A-16C

The USAF was rather reluctant to let the idea of a dedicated CAS F-16 go, and planned to replace its A-10's with F-16s fitted with a version of the Warthog's Avenger cannon. In November 1988, the 174th TFW of the New York ANG began transitioning from the A-10A Thunderbolt II to the F-16A/B block 10, becoming the first unit to operate the F-16 in a close air support role.

 

During Desert Storm, their 24 F-16A/B aircraft were equipped to carry the General Electric GPU-5/A Pave Claw pod on the centerline station. The pod houses a 30mm GAU-13/A four-barrel derivative of the seven-barrel GAU-8/A cannon used by the A-10A, and 353 rounds of ammunition. The aircraft received the new designation F/A-16, and were the only F-16s ever to be equipped with this weapon, intended for use against a variety of battlefield targets, including armor.

 

If the tests were successful, there were plans for a fleet of F/A-16C's with the same armament. To demonstrate the concept, the AF installed Pave Penny avionics, 30mm gun pods and European One paint jobs on 7 F-16C's (#83128, -129, -130, -131, -132, -144, -2??). F-16B no. 2 (#75752) was given similar treatment except for a Falcon Eye system. These aircraft flew from Nellis with the 'WA' tailcode.

 

The F-16s from the 174th were deployed to the Persian Gulf during Desert Storm, but the project proved to be a miserable failure. Precision aiming was impossible for several reasons:

 

· The pylon mount isn't as steady as the A-10's rigid mounting;

· The F-16 flies much faster than an A-10, giving the pilots too little time approaching the target;

· Firing the gun shook the aircraft harshly and made it impossible to control;

· Essential CCIP (continuously computed impact point) software was unavailable.

 

Pilots ended up using the gun as an area effect weapon, spraying multiple targets with ammunition, producing an effect rather like a cluster bomb. It took only a couple of days of this before they gave up, unbolted the gun pods, and went back to dropping real cluster bombs - which did the job more effectively.

 

The F/A-16C plan was quietly forgotten. The USAF still has plans to replace the A-10 with F-16s, but they no longer involve 30mm gun pods (or, apparently, a designation with an "A" in it).

  • Like 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...