Talk:U.S. helicopter armament subsystems

Unheard
very good work here, but I think we need to make this article more prominent, otherwise all the effort here will be wasted.--Ariedartin 14:28, 30 April 2006 (UTC)

AH-64 Subsystem To Be Added
we'll need to add a section detailing the armament subsystem of the AH-64 Apache. its younger brother the AH-1 Cobra has a section, but the big brother and main actor doesn't. hmm..--Ariedartin 07:39, 4 May 2006 (UTC)
 * The real issue with the AH-64 is that, at least as of right now, there's only one subystem for it, the M139, which covers everything (including the AH-64s defensive flare launcher), except its missile launch capabilities. I am unsure if there are actually designated subsystems, or whether it suffices to say that the AH-64 has the ability to launch the AGM-114 HELLFIRE, FIM-92C/D Air-To-Air Stinger (ATAS), or previously the the AIM-9 series.  --Thatguy96 09:12, 4 May 2006

XM8 Merger
Support: It appears to me that the XM8, because of the extremely limited scope of the article, will be a perpetual stub. Suggest moving it in with this article. -- Thatguy96 14:34, 25 June 2007 (UTC)

Support, as the US Helicopter Armament Subsystems article covers it already. Sharkface217 18:27, 10 July 2007 (UTC)

On the definition of a subsystem
A recent revert on my part makes me think I should at least clarify on the talk page what I understand a subsystem to be in the context of this article. Maybe it will allow for some better text to be added to the introduction. What I do not consider to be a subsystem are physical extremities of an aircraft, ie stub wings and hardpoints, pylons and the like. This gets into a certain amount of potential confusion over the inclusion of turrets and similar components that are essentially standard on certain helicopters (mainly purpose built attack helicopters). These systems are included only because the respective services treat them as separate systems. Hardpoints and pylons that are mentioned are mention for the same reason, because they are treated as optional subsystems, such as the M156 universal mount, the mention of the BRU-type pylons, the EFSS, and the Universal Weapons Pylon. None of these systems appear on all UH-1/UH-60/OH-58 helicopters, respectively, nor even on all of a certain variant (the designation OH-58D does not specify the usage of the UWP, the EFSS can be mounted on any UH-60, and so on). The six external hardpoints on the AH-56 were to be found on all production AH-56, as are the four on AH-1s and AH-64s. These I understand to be an integral part of the aircraft and not a subsystem, similar to the hardpoint mounting "stations" on UH-1 helicopters to which subsystems are attached. -- Thatguy96 (talk) 21:06, 25 July 2008 (UTC)


 * I kinda thought that, but the lead mentions rockets. So I wasn't sure.  I only added the hardpoints (part of aircraft) to cover the TOW missile pods and Folding fin rocket launchers that are mounted on them not the hardpoitn themselves.  Anyway I added that text to the AH-56 article and will expand it as well. -Fnlayson (talk) 21:16, 25 July 2008 (UTC)


 * I know this is an old discussion, but also for consideration is the primary mission of the aircraft. The Apache was primarily designed to kill tanks, and then provide some CAS. It is a launch platform for Hellfire missiles. Therefore, maybe they should be considered an actual subsystem. Why else would the fire control be specifically designed to fire that missile using another subsystem, the TADS/PNVS? -- T HE F OUNDERS I NTENT  PRAISE 17:03, 30 June 2011 (UTC)

External links modified (January 2018)
Hello fellow Wikipedians,

I have just modified 6 external links on U.S. helicopter armament subsystems. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20100905111603/http://tri.army.mil/LC/CS/csa/aaarmsys.htm to http://tri.army.mil/LC/CS/csa/aaarmsys.htm
 * Added archive https://web.archive.org/web/20090325024529/http://tri.army.mil/LC/cs/Csa/aahist.htm to http://tri.army.mil/LC/CS/csa/aahist.htm
 * Added archive https://web.archive.org/web/20100905111603/http://tri.army.mil/LC/CS/csa/aaarmsys.htm to http://tri.army.mil/LC/CS/csa/aaarmsys.htm
 * Added archive https://www.webcitation.org/5JQMf7m5r?url=http://tri.army.mil/LC/CS/csa/aahist2.htm to http://tri.army.mil/LC/CS/csa/aahist2.htm
 * Added archive https://web.archive.org/web/20070224040142/http://tri.army.mil/LC/CS/csa/cpm197.htm to http://tri.army.mil/LC/CS/csa/cpm197.htm
 * Added archive https://web.archive.org/web/20100905111603/http://tri.army.mil/LC/CS/csa/aaarmsys.htm to http://tri.army.mil/LC/CS/csa/aaarmsys.htm

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 22:07, 24 January 2018 (UTC)