Good news for our community: The team of F-16.net prepares a new section called "F-16 Combat History". After consultation with Jon and Stefaan I will provide the first fact file related to the main combat phase of Operation Enduring Freedom (OIF), October 2001 – April 2002. This file includes facts and links to hot documents related to Operation Anaconda.
I will use this special topic also to get some additional info and especially photo support. As I remember, USAF published only a handful of related F-16 pictures.
In one or two weeks the first stuff should be online.
My first question: How many F-16s of the 170th FS, 183rd FW, Illinois ANG, were deployed to the 332nd AEG at Ahmed Al Jaber AB, Kuwait, in March 2002 (at this time usually 10 aircraft)?
Last edited by J.J. on Jan 07, 2007 - 07:23 AM; edited 9 times in total
Sponsor
Posted: Jul 07, 2008 - 4:58 AM
F-16.net Sponsor
This message from our sponsor will disappear if you log on as a member.
Last edited by J.J. on Jan 07, 2007 - 07:23 AM; edited 9 times in total
What kinds of operations are going to be included? There was Operation Provide Comfort that was not a conflict in the strictest sense of the word but they did drop bombs and fire missiles. There was also the Kosovo missions, that was a "police action" still missiles and bombs were dropped.
Good question, IDCrewDawg! The "F-16 Combat History" section will be open for any kinds of military operations in which F-16 units were or are involved. Because my focus is U.S. CENTCOM, I will edit OEF, OIF and OSW, later possibly also ONW and ODS. Everyone who will edit other related fact files, including Allied Force (as only one sample), should contact Jon.
Velvet, as I know there is currently no editor for any fact file related to Israeli combat operations against Lebanon. If you would provide some related stuff please contact Jon.
Would it be more accurate to call the section "Conflict Involvement History" or maybe "Operational Deployment History" or maybe even "Deployed Mission History". Would you include information like how many bombs were dropped, or missiles fired? What about things like targets destroyed?
Hi, IDCrewDawg! I made four suggestions for this upcoming section: "F-16 Combat History”, "F-16 in Combat”, "F-16 Units in Combat", and "Combat History”. My favorite was “F-16 Combat History” and Jon and Stefaan agreed. Another requirement, related to web site design standards, was the circumstance that the designation should be short enough for an one-line term in the left main navigation frame at F-16.net. In the next couple of days I will post a short preview, related to OEF´s main combat phase. Please enjoy!
Please take a first look! Note: That´s only a first preview, related to the chapter "F-16 Deployments". And, that´s only a working file. I would be very thankful for any corrections or additions.
Quote:
F-16 Deployments (Copyright 2005 by Joachim Jacob and F-16.net)
During OEF´s main combat phase, U.S. F-16s operated out of two Southwest Asian air bases used by CENTAF Forward: Ahmed Al Jaber AB, Kuwait, and Al Udeid AB, Qatar.
As the force build-up for OEF began, an Air Force Reserve Command (AFRC) "Rainbow Team" with 10 F-16Cs Block 30/32 was already deployed to Ahmed Al Jaber AB. This "rainbowed" Expeditionary Fighter Squadron (EFS) included jets from the following three units: 93rd FS "Makos", 482nd FW, Homestead ARB, Florida (4 aircraft), 457th FS, 301st FW, NAS Fort Worth JRB (Carswell Field), Texas (3 aircraft), 466th FS "Diamondback", 419th FW, Hill AFB, Utah (3 aircraft).
This contingent was deployed to the 332nd Air Expeditionary Group (332nd AEG) at Ahmed Al Jaber AB, Kuwait, as part of a regularly scheduled 90-day Aerospace Expeditionary Force (AEF) rotation to enforce the no-fly zone over southern Iraq, in this case for the AEF 7/8 (Cycle 2) rotation (September – November 2001). During AEF Cycle 2 AEFs with even numbers were clearly assigned to Operation Southern Watch (OSW), AEFs with odd numbers were assigned to Operation Northern Watch (ONW) and to some other tasks. In this case the AFRC contingent was an integrated part of AEF 8. To perform this 90-day deployment, which began in mid-September, 2001, the three units combined personnel, aircraft and equipment. The 482nd FW was the lead unit in September, followed by the 419th FW in October, and the 301st FW in November. This "Rainbow Team" was also supported by pilots and maintenance personnel from AFRC´s 302nd FS, 944th FW, Luke AFB, Arizona. Originally tasked only with OSW missions, on October 22, 2001, this contingent flew the first F-16 sorties for OEF over Afghanistan.
Especially for OEF, additionally F-16s were deployed to Al Udeid AB, Qatar. On November 7, 2001 – exactly one month after the operation started – at this bare base arrived 6 F-16CJ Block 52 from the 389th FS "Thunderbolts" (shortened nicknamed also as "T-Bolts"), 366th Wing "Gunfighters" (ACC), Mountain Home AFB, Idaho. This contingent deployed as 389th Expeditionary Fighter Squadron (389th EFS). Squadron commander was Lt. Col. Tom Lawhead. During the deployment the 389th EFS was the first F-16 unit to use the GBU-31 JDAM and the new Wind Corrected Munitions Dispensers (WCMDs), based on CBU-103, in combat.
In early December 2001 AFRC´s "Rainbow Team" at Ahmed Al Jaber AB was replaced by elements of the 18th FS "Blue Foxes", 354th FW (PACAF), Eielson AFB, Alaska, which deployed with 10 F-16C (Block …) and 142 personnel as part of the regularly scheduled AEF 9/10 (Cycle 2) rotation (December 2001 – February 2002). Squadron commander was Lt. Col. Burt Bartley. On March 2, 2002, pilots from the 18th FS were some of the first fighters involved in Operation Anaconda. Two pilots received Distinguished Flying Crosses for their effort. The jets returned to Eielson AFB in five-ship formations each on March 21 and 22, 2002. During this deployment the unit flew 3,200 flight hours, about four times the normal rate.
In early January 2002 the 389th EFS at Al Udeid AB was replaced by elements of the 157th FS "Swamp Foxes", 169th FW (South Carolina ANG), McEntire ANGB, South Carolina, which deployed also 6 F-16CJ Block 52. At this time the 157th FS was the only ANG squadron equipped with F-16CJ (Block 52). The aircraft left their home base on January 8 and 9, 2002. On April 3, 2002, the aircraft returned home to McEntire ANGB.
In mid-March 2002 the "Blue Foxes" at Ahmed Al Jaber AB were replaced by elements of the 170th FS, 183rd FW (Illinois ANG), Capital Airport, Springfield, Illinois, which deployed with probably 10 F-16C (Block …) as part of the regularly scheduled AEF 1/2 (Cycle 3) rotation (March – May 2002). During this deployment the 170th FS flew nearly 500 OSW sorties and 88 OEF sorties, alone more than 1,000 flight hours in the first 30 days. The unit achieved a 98-percent mission capable rate, with an equally impressive 97-percent sortie effectiveness rate. On April 17, 2002, a two-ship formation from the 170th FS mistakenly dropped a bomb over the Tarnak Farms Range near Kandahar. Four Canadians were killed and eight wounded during this "friendly fire" incident.
Last edited by J.J. on Dec 03, 2005 - 12:03 AM; edited 3 times in total
Joined: Nov 06, 2003
Posts: 952
Location: Canada
Status: Offline
J.J.
WOW, really good stuff, keep it coming. I hope we can get some personal stories from guys in these units to add to this great piece of history. Looking forward to seeing how this progresses.
I hope more people come forward with personal accounts!
Cheers,
Jon
Asif
Posted: Nov 30, 2005 - 04:28 PM
F-16.net Editor
Joined: Aug 23, 2003
Posts: 1560
Location: United Kingdom
Deployment patches for the 157th and 389th are in the patch gallery from the time period described in the above article.
J.J. Need tie up dates for the the 22nd and 23rd EFS. Got details?
Thank you for your replies, guys! IDCrewDawg: There were no OEF fighter support from Incirlik AB, Turkey, or Prince Sultan AB, Saudi Arabia. Jon: I also look forward for personal accounts but especially for photo stuff. Asif: The patches are known. The 22nd and 23rd FSs played no role in OEF. For the main combat phase of OIF elements of both squadrons deployed as 22nd and 23rd EFSs to the 379th AEW at Al Udeid AB, Qatar. During the U.S. force build-up for OIF some units were officially deployed for OEF or GWOT (Global War on Terrorism). But that was only cleared PA stuff.
"Cope India 2005" and another actually upcoming "tactical" thread currently dominate this general forum. Instead of that I will go further in the history. Here´s another preview related to my upcoming fact file. Please note: That´s only a working file. I would be very thankful for any corrections or additions.
Quote:
F-16 Deployments copyright 2005 by Joachim Jacob and F-16.net.
The 332nd Air Expeditionary Group (332nd AEG)
The 332nd AEG at Ahmed Al Jaber AB, Kuwait, was activated in November 1998 to replace the 4406th Operations Group (Provisional) at this deployed air base, often dubbed shortened as "The Jab" by U.S. airmen. The 332nd AEG played a key role during OSW, and later also during OEF´s main combat phase. At this time the largest CENTAF Forward host unit deployed to the CENTCOM AOR for OSW was the 363rd AEW at Prince Sultan AB, Saudi Arabia. Typically assigned fighter units were an F-15C Eagle EFS and an F-16CJ EFS mainly for SEAD ("Wild Weasel") missions. Saudi Arabia never allowed the use of Prince Sultan AB (by U.S. military shortly nicknamed "PSAB") for any strike missions, only for self-defense. At least, Saudi Arabia allowed the use of CENTCOM´s Combined Air Operations Center (CAOC) at PSAB for the main combat phases of OEF and OIF. In contrast to "PSAB", Ahmed Al Jaber AB could be used for any air strike (Air Interdiction) or close air support (CAS) missions related to OSW, OEF and OIF.
332nd AEG Organization:
As an expeditionary unit the 332nd AEG consisted of a small number of one-year permanent party personnel, including the group commander, and a number of operational and support expeditionary squadrons. The permanent party personnel were assigned usually for a year, to provide continuity in key positions. The majority of the assigned personnel – about 1500 before the force build-up for OEF – was deployed as parts of regularly AEF rotations. During OEF´s main combat phase the 332nd AEG was commanded by Col. David C. ("Dave") Nichols, an F-16 pilot. His deputy commander was Col. (or at this time Lt. Col.) Matthew D. Neuenswander, an A/OA-10A pilot.
During the AEF 7/8 (Cycle 2) rotation there were originally three operational flying squadrons assigned to the 332nd AEG: An F-16 expeditionary fighter squadron (EFS), an A/OA-10A Thunderbolt II ("Warthog") expeditionary fighter squadron, and an expeditionary rescue squadron (ERQS). Both of the last two units were tasked with combat search and rescue (CSAR) alert, if any U.S. military aircraft should be crashed or shot down over Iraq´s southern no-fly zone.
As part of the force build-up for OEF, in October 2001 the 366th Wing "Gunfighters" (ACC), Mountain Home AFB, Idaho, deployed elements of the 391st FS "Bold Tigers" with F-15E Strike Eagles to the 332nd AEG. On October 17, 2001, pilots from the 391st EFS flew their first combat missions over Afghanistan. In early January 2002 this unit was replaced by elements of the 335th FS "Chiefs", 4th Wing, Seymour Johnson AFB, North Carolina, which deployed with F-15Es as 335th EFS. On January 12, 2002, the first eight aircraft of the 391st EFS returned to their home base.
Surprisingly, both A/OA-10A contingents which were regularly deployed to the 322nd AEG as parts of the AEF 7/8 and AEF 9/10 rotations were never tasked with OEF missions. The first involved A/OA-10A contingent was the 74th EFS which consisted of elements from the 74th FS, 23rd FG "Flying Tigers" (ACC), Pope AFB, North Carolina. This EFS regularly deployed for the AEF 1/2 (Cycle 3) rotation.
After the withdrawal of the F-15Es from the 335th EFS, by mid-April 2002 the 332nd AEG hosted additionally a contingent of F/A-18C Hornets from an USMC fighter-attack squadron.
In the next couple of days I will post some more previews related to the 366th AEW and the 379th AEW at Al Udeid AB, Qatar, and also some info related to Operation Anaconda.