Editing Bell UH-1 Iroquois (section)

===U.S. Air Force===
[[File:Huey Trio UH-1Ns Fly Over Joint Base Andrews, MD, May 10, 2019.jpg|thumb|Trio of UH-1N in 2019]]
[[File:UH-1N-6.jpg|thumb|A USAF UH-1N during Exercise Wounded Eagle '83]]
<!-- [[File:Vietnam Air Force UH-1 in flight 19700718.jpg|thumb|[[Republic of Vietnam Air Force]] (VNAF) UH-1H lands during a combat mission in Southeast Asia in 1970|alt=USAF UH-1 landing]] -->

In October 1965, the [[United States Air Force]] (USAF) [[20th Helicopter Squadron]] was formed at [[Tan Son Nhut Air Base]] in South Vietnam, equipped initially with [[Sikorsky S-61R|CH-3C]] helicopters. By June 1967, the UH-1F and UH-1P were also added to the unit's inventory and, by the end of the year, the entire unit had shifted from Tan Son Nhut to [[Nakhon Phanom Royal Thai Air Force Base]], with the CH-3s transferring to the [[21st Helicopter Squadron]]. On 1 August 1968, the unit was redesignated the 20th Special Operations Squadron. The 20th SOS's UH-1s were known as the ''Green Hornets'', stemming from their color, a primarily green two-tone camouflage (green and tan) was carried, and radio call-sign "Hornet". The main role of these helicopters were to insert and extract reconnaissance teams, provide cover for such operations, conduct psychological warfare, and other support roles for [[covert operation]]s especially in Laos and Cambodia during the so-called [[Laotian Civil War|Secret War]].<ref name="Covert">Mutza 1987, pp. 22–31.</ref>

USAF UH-1s were often equipped with automatic grenade launchers in place of the door guns. The XM-94 grenade launcher had been tested on Army rotorcraft prior to its use by the USAF. The unit was capable of firing 400 grenades per minute, up to 1,500 yards effective range.<ref>Mutza 2012, p. 33.</ref>

Into the twenty-first century, the USAF operates the [[Bell UH-1N Twin Huey|UH-1N]] for support of [[intercontinental ballistic missile]] (ICBM) sites, including transport of security personnel and distinguished visitors.<ref>{{cite web |url= https://www.af.mil/About-Us/Fact-Sheets/Display/Article/104464/uh-1n-huey/ |title= UH-1N Huey |publisher= U.S. Air Force |date= 30 September 2015 |access-date= 21 August 2017 |archive-date= 22 August 2017 |archive-url= https://web.archive.org/web/20170822012904/http://www.af.mil/About-Us/Fact-Sheets/Display/Article/104464/uh-1n-huey/ |url-status= live }}</ref><ref>{{cite web |url= http://www.janes.com/article/71230/us-air-force-targets-july-for-uh-1n-replacement-solicitation |title= US Air Force targets July for UH-1N replacement solicitation |publisher= IHS Jane's Defence Weekly |date= 8 June 2017 |access-date= 21 August 2017 |archive-date= 22 August 2017 |archive-url= https://web.archive.org/web/20170822052644/http://www.janes.com/article/71230/us-air-force-targets-july-for-uh-1n-replacement-solicitation |url-status= dead }}</ref> On 24 September 2018, the USAF announced that the Boeing/Leonardo MH-139 (an [[AgustaWestland AW139|AW-139]] variant) had won a competition to replace the UH-1N fleet.<ref>{{cite web |url= https://www.defensenews.com/breaking-news/2018/09/24/the-air-force-picks-a-winner-for-its-huey-replacement-helicopter-contract/ |title= The Air Force picks a winner for its Huey replacement helicopter contract |first= Valerie |last= Insinna |date= 24 September 2018 |website= defensenews.com |access-date= 25 September 2018}}</ref> The UH-1N fleet is in service as of 2024, as production of the new type is ramped up.<ref>{{Cite web |last=Losey |first=Stephen |date=2024-01-30 |title=Boeing expects Grey Wolf helicopter deliveries to Air Force this year |url=https://www.defensenews.com/air/2024/01/30/boeing-expects-grey-wolf-helicopter-deliveries-to-air-force-this-year/ |access-date=2024-04-26 |website=Defense News |language=en}}</ref><ref name=":3">{{Cite web |last=Hadley |first=Greg |date=2023-11-20 |title=Air Force Gets Its Final Test MH-139 Helicopter from Boeing |url=https://www.airandspaceforces.com/air-force-final-test-mh-139-helicopter/ |access-date=2024-04-26 |website=Air & Space Forces Magazine |language=en-US}}</ref>