Wikipedia

102nd Intelligence Wing

(Redirected from 102d Fighter Group)

The United States Air Force's 102nd Intelligence Wing (102 IW), of the Massachusetts Air National Guard, is a military intelligence unit located at Otis Air National Guard Base, Massachusetts. Its primary subordinate operational unit is the 101st Intelligence Squadron. The 102nd Fighter Wing was formally re-designated the 102nd Intelligence Wing on 6 April 2008 and was planned to reach full operational capacity in 2010.[3]

102nd Intelligence Wing
101st Fighter Squadron F-47N Thunderbolts Logan Airport 1946 Republic P-47N-25-RE Thunderbolt 44-89347 in foreground
Active15 October 1942 – Present
Country United States
Branch  Air National Guard
TypeWing
RoleGround-based distributed radar installation[1]
Size950 members:
80 officers
745 enlisted personnel
Part ofMassachusetts Air National Guard
Garrison/HQOtis Air National Guard Base, Mashpee, Massachusetts
Nickname(s)"Eagle Keepers"
"Bear Chasers"
Motto(s)"Omnis Vir Tigris"
Everyone A Tiger
EquipmentDistributed Common Ground Systems
Air Operations Center[2]
EngagementsWorld War II
Cold War
Operation Noble Eagle
Decorations Air Force Outstanding Unit Award Personnel Center Awards Search (Post-1991)
Commanders
CommanderColonel Wendy Armijo
Vice CommanderColonel James P. Hoye
Command ChiefChief Master Sergeant John G. Dubuc
Insignia
102nd Intelligence Wing emblemA standard shield, surrounded on the edge by a diminished yellow border. The upper part of the shield is blue, with one gray aircraft with a white trail pointing out from the left side. The plane is flying over the northeastern portion of the western hemisphere, which is colored in green and light blue. On the front of the gray aircraft with a white outline is a cockpit, with the jet firing three rockets. The three rockets trail white smoke and are aimed the same direction as the aircraft. Under the nose of the plane are two black aircraft coming out of clouds and rising up towards the jet. Attached to the shield is a white scroll edged with the same color border as the shield, surrounding the inscribed "102D INTELLIGENCE WING" in blue

Mission

edit

The wing mission is "to provide world wide precision intelligence and command and control, along with trained and experienced airmen for expeditionary combat support and homeland security." In addition, the website says that their Air Force–based mission is in line with the ability of joint force commanders to keep pace with information and incorporate it into a campaign plan.[4] In addition to its strictly military role, the wing shares the overall Air National Guard mission of providing assistance during national emergencies such as natural disasters and civil disturbances.[4]

However, the 102nd Intelligence Wing has been ordered to halt its intelligence-gathering mission.[5][6] Secretary Austin has ordered a DoD-wide review of the military intelligence practices to be completed in 45 days.[7][8] The recertified 102nd ISRG (Intelligence, surveillance and reconnaissance group) resumed its intelligence mission on 1 June 2024.[9]

Units assigned

edit

Current

edit
 
F-106A intercepting Soviet Tu-95 Bear D bomber aircraft off Cape Cod on 15 April 1982
102nd Intelligence Wing  [10]
102nd Intelligence Surveillance Reconnaissance Group 202nd Intelligence Surveillance Reconnaissance Group 102nd Mission Support Group 102nd Medical Group 253rd Cyberspace

Engineering Installation

Group

101st Intelligence Squadron 267th Intelligence Squadron 102nd Force Support Squadron 102nd Guard Medical Unit 212th Engineering Installation Squadron
102nd Intelligence Support Squadron 203rd Intelligence Squadron 102nd Security Forces Squadron 102nd EMEDS-CM 202nd Weather Flight
102nd Operations Support Squadron 202nd Intelligence Support Squadron 102nd Civil Engineer Squadron
102nd Communications Flight
102nd Contracting Office
102nd Environmental Management Office
102nd Logistics Readiness Flight

Former

edit
 
F-106A intercepting a Tu-95 Bear over Nova Scotia. This F-106 later crashed in 1983.
102nd Fighter Wing  [11]
102nd Operations Group 102nd Maintenance Group 102nd Mission Support Group 102nd Medical Group
101st Fighter Squadron 102nd Aircraft Maintenance Squadron 102nd Civil Engineering Squadron 102nd Medical Squadron
102nd Operations Support Flight 102nd Maintenance Squadron 102nd Communications Squadron
202nd Weather Flight 102nd Maintenance Operations Flight 102nd Security Forces Squadron
102nd Mission Support Flight
102nd Student Pilot Flight
102nd Services Flight

History

edit

According to the Air Force, the history of the 102nd begins with the 318th Fighter Group, which was active during World War II. After the war, the 318th was inactivated, and eventually the 102nd Fighter Wing was formed, which had a direct lineage link. In 1946, the 102nd was activated at Logan International Airport where it stayed until 1968, when it moved to Otis Air Force Base. Beginning in 1946, the wing began regular patrols of the Northeastern United States which took place in conjunction with Air Force active duty units. In 1968, the 102nd was moved to Otis, where it continued its regular patrols until 1973.

During the time that the wing had a flying mission, the wing deployed to many locations around the globe to assist in missions for the Air Force. In 1961, the wing deployed to France during the Berlin Crisis. Twenty eight years later, the wing deployed to Panama during Operation Coronet Nighthawk. It also participated in Operation Northern Watch, helping to patrol the No-Fly Zone north of the 36th parallel in Iraq. During the September 11 attacks, the 102nd Fighter Wing deployed the first Air Force aircraft toward New York City, but they arrived too late to stop the attacks.

Over the years, the wing has controlled many other Air National Guard units. Following the inactivation of the 67th Fighter Wing in November 1950, the wing was put in charge of a few fighter units on the Atlantic Coast. In 1976, the wing even became responsible for the 147th Fighter Interceptor Group, located in Texas.

Military downsizing through the Base Realignment and Closure (BRAC) process removed the wing's F-15C Eagles beginning in 2007, leaving the 102nd with an intelligence gathering mission. If activated to federal service, the Wing is gained by the United States Air Force Air Force Intelligence, Surveillance and Reconnaissance Agency, and is one of three Air National Guard wings under this agency. As commonwealth militia units, the units in the 102nd Intelligence Wing are not in the normal United States Air Force chain of command. They are under the jurisdiction of the Massachusetts National Guard unless they are federalized by order of the President of the United States.

After a large-scale leak of Department of Defense documents in early 2023 that were traced to Jack Teixeira from the wing, the USAF announced a separate investigation on April 18 and halted the wing from carrying out its intelligence tasks.[12]

Roots of the 102nd

edit

The 102nd Intelligence Wing traces its roots to the 318th Fighter Group[13] which was formed in 1942. It fought in the Pacific as part of bomber escort missions to Japan, and participated in aircraft carrier operations, rarely experienced by the Army Air Force.[13] The 318th returned to the United States after the war, was inactivated on 12 January 1946.[13]

The wartime 318th Fighter Group was re-designated as the 102nd Fighter Group, and was allotted to the Massachusetts Air National Guard on 24 May 1946. It was organized at Logan Airport, Boston, and was extended federal recognition on 22 October 1946 by the National Guard Bureau. The 102nd Fighter Group was bestowed the lineage, history, honors, and colors of the 318th Fighter Group.

From October 1946 the 102nd (previously the 67th Fighter Wing) was commanded by General Louis E. Boutwell until his death in July 1947. From July 1947 until 1956 the 102nd was commanded by Brigadier General Lyle E. Halstead.

Cold War

edit
 
F-86Hs lined up on the ramp at night at Logan

In 1946-47 the National Guard Bureau began a major expansion of its air units. Massachusetts was allotted the 67th Fighter Wing, which consisted of the 101st Fighter Squadron, the 131st Fighter Squadron, the 132nd Fighter Squadron, the 202nd Air Service Group, 601st Signal Construction Company, 101st Communications Squadron, 101st Air Control Squadron, 151st Air Control and Warning Group, 567th Air Force Band, 101st Weather Flight and the 1801st Aviation Engineer Company. The 67th Wing was assigned to Air Defense Command.[14]

Guard units were generally neglected when the United States Air Force was created.[14] Despite the introduction of jet fighters, the Guard units were left with generally overused World War II propeller aircraft, and had few funds for training.[14] As the Cold War intensified, the Air Force looked to the Guard to fill United States–based interception missions and started overhauling their organization.[14] Although the Massachusetts Air National Guard was not federalized for the Korean War, many airmen volunteered for active duty and flew in Korea.[14] On 1 November 1950, the 67th Fighter Wing was inactivated and replaced by the 102nd Fighter Wing, including just the 101st and 131st squadrons and their associated support units,[14] and at some point before 1961 the wing was renamed a Tactical Fighter Wing. Additionally, the wing kept the 567th, and the 1801st.[14] The squadrons were issued F-84B Thunderjets, but these were recalled and replaced by F-51 Mustangs which were flown until 1954 when the F-94 Starfire replaced the Mustangs.[14] In 1952 the 253rd Combat Communications Group was activated and added to the 102nd.[14] In 1958 the Wing converted to the F-86H Sabre.[14]

From 195, the 102nd was commanded by Brigadier General Charles W. Sweeney, pilot of the B-29 Superfortress Bockscar that dropped the Fat Man nuclear bomb on Nagasaki, Japan.[15] During his tenure, the wing developed from a rather new unit to the mainstay of air defense in the Northeastern United States.[14] Sweeney retired as a major general in 1976.

Berlin Wall Crisis

edit
 
North American YF-86H-5-NA Sabre of the 138th Tactical Fighter Squadron/102nd Tactical Fighter Wing deployed at Phalsbourg – 1962

On 16 August 1961, when the Berlin Wall crisis was unfolding, several United States Air Force Reserve units were notified of their pending recall to active duty. On 1 October the wing and its three squadrons, the 101st, 131st and 138th were placed on active duty at Otis Air Force Base.[15]

In late October, the 102nd departed Logan for Phalsbourg-Bourscheid Air Base, Phalsbourg, France.[14] The wing had 82 Sabres, plus two C-47 Skytrains and six T-33 Shooting Stars for support and training purposes. During the crisis, the wing controlled the 102nd Tactical Fighter Group, the 104th Tactical Fighter Group, and the 174th Tactical Fighter Group from New York.[16] The 102nd's primary mission was to provide close air support to NATO ground forces, including the Seventh Army,[14] and air interdiction.[14] During the blockade, the 102nd did not incur any losses.[14] Starting on 5 December 1961 the 102nd began deploying to Wheelus Air Base, Libya for gunnery training.

During its time in Europe, the 102nd participated in several United States Air Force and North Atlantic Treaty Organization exercises, including a deployment to Leck Air Base, West Germany near the Danish border. At Leck, ground and support crews from both countries exchanged duties, learning how to perform aircraft maintenance and operational support tasks.

The 102nd returned to the United States in August 1962.[14] Regular Air Force personnel and a group of Air National Guard personnel who volunteered to remain on active duty formed the 480th Tactical Fighter Squadron of the newly activated 366th Tactical Fighter Wing.[17]

Relocation to Otis

edit

In 1968, the 102nd Tactical Fighter Wing moved to Otis Air Force Base, and was reassigned from the Air Defense Command to the Tactical Air Command the next year. The wing flew the F-84F Thunderstreak from 1964 until June 1971, when a squadron of F-100D Super Sabres was transferred directly from units fighting the Vietnam War.[16] These were superseded soon after by the Mach 2 F-106 Delta Darts and on 10 June 1972, the unit became the 102nd Air Defense Wing.[16] On 30 December 1973, Otis Air Force Base was inactivated and transferred to the Massachusetts Air National Guard as Otis Air National Guard Base.[18]

The wing intercepted Soviet Tupolev Tu-95 Bear bombers on many occasions, the first of which occurred off Long Island on 25 April 1975.[19] Many of these incidents involved escorting the Bears to Cuba. The wing occasionally shadowed drug smuggling aircraft, and on one occasion was scrambled to escort an unidentified object, which later turned out to be a weather balloon.[20]

In 1976, the 102nd Fighter Interceptor Group was inactivated and reformed as the 102nd Fighter Interceptor Wing. It assumed authority for the 177th Fighter Interceptor Group at Atlantic City Air National Guard Base and the 125th Fighter Interceptor Group at Jacksonville Air National Guard Base. Both units flew the F-106. It also assumed command of the 107th Fighter Interceptor Group at Niagara Falls Air Reserve Station and the 147th Fighter Interceptor Group at Ellington Field, Texas. The latter two flew the F-4C Phantom.[16]

 
F-15 from the 49th Fighter Wing that was transferred to the 102nd

The 102nd Fighter Interceptor Wing lost its F-106s on 5 January 1988. Between January and April 1988, the wing converted to the F-15A Eagle, which it received from the 5th Fighter-Interceptor Squadron which was inactivating at Minot Air Force Base.[21] It then resumed its alert commitment at Otis, and also established a new Detachment 1 at Loring Air Force Base, taking over for the inactivating 5th Fighter-Interceptor Squadron. The 102nd was the first Air National Guard unit to be equipped with the 102nd 's conversion to the F-15 marked the first Air National Guard air defense unit to receive the Eagle. The 102nd Fighter Interceptor Wing was redesignated the 102nd Fighter Wing in April 1992. [16]

On 24 January 1989, airmen monitoring the radar at the Northeast Air Defense Sector at Griffiss Air Force Base spotted a plane which was not following any known flight plan. The order was then given to "scramble the Eagles," after repeated attempts to contact the pilot failed. Two jets then took off from Loring to search for the "unknown rider." The pilots later came across a plane that was blacked out, with no lights on inside or outside. The pilot was a narcotics smuggler from Colombia's Medellin drug cartel. He was carrying had a street value of two hundred million dollars in the amount of 500 kilograms of cocaine.[22]

Post-Cold War

edit

Local defense

edit
 
F-15s from Otis Air National Guard Base

The wing continued its air defense mission after the fall of the Soviet Union. In 1992, the wing deployed eight pilots, five F-15 Eagles, and 48 maintenance and security personnel, for five days training at Canadian Forces Base Goose Bay, Labrador, Canada.[18] The same year, with the reorganization of the Air Force, the wing was reassigned from the disbanding Tactical Air Command to the newly formed Air Combat Command.[23] In July 1993, the wing deployed 50 personnel from the 102nd Civil Engineering Squadron under field conditions, to the island of Eleuthera in the Bahamas. They helped rebuild schools and municipal facilities damaged by Hurricane Andrew.[1]

On 11 February 1993, jets were scrambled to intercept the hijacked Lufthansa Flight 592, which eventually landed at John F. Kennedy International Airport without incident. The planes were joined by F-16s from the 177th Fighter Wing in Atlantic City, New Jersey. The F-15s initially intercepted the aircraft off the coast of eastern Canada. The planes then began to trail the jet at a distance of 10-mile (16 km). As they approached the airport, the distance decreased to 5-mile (8.0 km). The fighters then did a low fly-by as the plane landed. They continued to circle around the airport until they returned to Otis.[24]

In 1994, the 102nd received more F-15A/B Eagles from the 32nd Fighter Group at Soesterberg Air Base, which was inactivating as part of the post Cold War draw down of forces in Europe.[21]

Deployments

edit

Between 1991 and 1995, the 102nd deployed to Panama as part of Operation Coronet Nighthawk, which was a drug interdiction operation. In 1992 the wing became simply the 102nd Fighter Wing as part of an Air Force-wide renaming of units.[25] The wing was deployed from 1995 to 1998 to Iceland for periodic 45-day deployments. In 1998, the wing's members also trained and deployed to Iceland, Canada, Korea, and Europe. The next year, the 102nd participated in Operation Northern Watch and was deployed to Turkey in order to enforce the no-fly zone over Iraq north of the 36th Parallel. In 2000, personnel were deployed to the Middle East and Europe in order to participate in Operation Southern Watch.[1]

9/11 terrorist attacks

edit
See also: U.S. military response during the September 11 attacks
 
F-15 over New York City after 9/11

Around 8:30 on the morning of 11 September 2001, the Otis Air Base Operations Center received a call from the Federal Aviation Administration's Cape Cod Facility Calls Operations Center that it might be receiving a call from the North American Aerospace Defense Command's Northeast Air Defense Sector. The manager of the Cape Cod facility then called the 102nd at Otis Air National Guard Base as they figured "...a call [to Otis Air Base] will be coming from NEADS soon and a scramble order is likely."[24] He called the base because he figured that the pilots would appreciate the heads up. When he called the Otis operations center, the superintendent of aviation management, Mark Rose, answered. He was initially confused by the call as no identification was given. Lieutenant Colonel Timothy Duffy was then handed the phone and alerted of the situation. On his radio, he called pilot Major Daniel Nash, the pilot who was sharing alert duty, and told him to get ready for a coming alert call. He also told him to suit up and get ready for a scramble call.[24]

Soon after, the commander of the 101st Fighter Squadron phoned the Northeast Air Defense Sector and asked for permission to launch the fighter jets. The sector in turn responded by ordering the commander of the weapons team which controlled the jets, Major Kevin Naspany, to place the fighters on "battle stations." This resulted in a warning siren sounding at Otis and the pilots scrambled to their jets. Four to five minutes later, the scramble order was received and the jets took off. Officially, this occurred at 8:46 am, with a six-minute difference between the official and unofficial accounts. Duffy radioed his command post for guidance and was told among other things that American Airlines Flight 11 was a Boeing 737, when in reality it was a 767. Once in the air, their radar kicked in, allowing them to effectively intercept the plane.[24]

Difficulties in accurately locating Flight 11 caused a delay of five minutes, to 8:43 am, before the scramble order was given and pilots Duffy and Nash could respond. When Flight 11 hit the North Tower at 8:46, the two jets were still readying for flight and did not take off until 8:52 am.

Major Naspany was then asked what to do with the fighters and he responded by saying, "Send 'em to New York City still. Continue! Go! This is what I got. Possible news that a 737 just hit the World Trade Center. This is a real-world...Continue taking the fighters down to the New York City area, JFK [International Airport] area, if you can. Make sure that the FAA clears it—your route all the way through...Let's press with this."[24] Unsure of their target, they were directed to a holding pattern in military-controlled airspace Whiskey 105 off of Long Island to avoid New York area air traffic. At 9:03 am, United Airlines Flight 175 hit the South Tower as the fighters were progressing to their holding position. The Northeast Air Defense Sector was not advised of this hijacked aircraft until 9:03.

Between 9:09 and 9:13, the jets stayed in a holding pattern. Soon after, they headed toward Manhattan and arrived at 9:25, where they established a Combat Air Patrol over the city.[26][27][28]

While all of this was going on, senior battle staff at Otis were watching the news when United Airlines Flight 175 crashed into the South Tower. This immediately caused one commander to shout out, "We need to go to battle staff!" This order caused senior commanders to disperse and head towards nearby operations buildings. Inside, the gathered together in the battle cab of the installation operations center. Soon after, a voice came over the base's loudspeakers: "The commander has ordered the 102nd core battle staff to assemble. Please report to the operations building immediately." Mobilization of the wing began to occur after this time. At the time of the order, eighteen planes were ready for flight and commanders began to prepare based on what they anticipated they would be asked to do. Most of these actions were guessing because there had never been an attack on the country before. Knowing that they could not await on guidance from the North American Aerospace Defense Command, the recalled all training flights and began loading fuel and weapons onto all available fighter jets.[24]

Meanwhile, at the battle cab, a maintenance squadron officer was told, "Listen, I want you to generate as many airframes [i.e. fighter jets] as you can!" This immediately caused all personnel to be called back and they were ordered to work on the remaining jets. This rush involved the placement of missiles on all jets, including some newer missiles which were rarely pulled out. Six jets which were on a training mission were traversing through the Whiskey Airspace when they were told by the Boston Air Route Traffic Control Center to head back to Otis immediately. Once landed, the pilots were told to park their jets but leave the engines running. Finally, the first planes took off at 10:20 in the morning.[24]

After a while, an order was received to launch all available fighters. Pilots were briefed on the national emergency and the potential that they might have to take out an aircraft. At this point, someone then ran into the room and said that there had been an order that was received from the Northeast Air Defense Sector that all available jets must launch. The pilots then ran out to their aircraft with speaker Treacy saying "Go, go, go!" In the haste that the morning had become, not all the jets had been refueled and a majority of the jets were still unarmed. The handful of jets that were armed were sent up with one or two missiles. The standard missile load involves at least two missiles at launch. This is after the handlers had worked at a "furious pace" and "hurried to fix all available jets with live weapons." Arming of the jets even began fifteen minutes after the South Tower had been hit. This fact would later lend credence to the theory that there was an idea floating around to ram the hijacked planes with a jet. Starting around 10:30 and ending at six that night, all twenty one planes were put into the air.[24][29]

edit
See also: 9/11 Conspiracy theories § Foreknowledge

After the initial shock of the attacks had passed, questions arose about how the military handled the hijacking and subsequent response with the jets. Some thought that the jets had been purposely kept from flying immediately to New York City.[30] The questions arising from the response time of the jets come from the practice of Cold War era policies which prohibited the immediate response to an emergency like a hijacking.[31] First responder and pilot Daniel Nash said that he could not recall being told that the North Tower was hit but he did remember seeing the smoke over 70-mile (110 km) away.[30] It is also claimed by conspiracists that the calculations of North American Aerospace Defense Command were incorrect because according to their own calculations, the planes were flying at 24% of their maximum speed.[30] This statement takes into account the time in which the planes were in a holding pattern over military airspace. The jets were also prohibited from going supersonic over land by Federal Aviation Administration rules. These rules are meant to prevent damage to buildings from the shock wave a sonic boom produces.[32][33]

Global War on Terror

edit

Operation Noble Eagle

edit
 
An F-15C from the 102d Fighter Wing prepares to fire upon an aerial drone over the Gulf of Mexico in 2005

More than 600 wing members were mobilized for Operation Noble Eagle, and the wing began flying around-the-clock combat air patrol missions immediately thereafter. This continued until February 2002.[18] On 22 December 2001 the wing escorted American Airlines Flight 63 as a direct result of Richard Reid trying to blow up a plane.[34]

In the buildup to the invasion of Afghanistan, six F-15s and 161 personnel were sent to the Persian Gulf region.[35] The wing also patrolled the skies of the Northeastern United States during this time period. The wing though never deployed for Operation Iraqi Freedom. The wing converted from the F-15A/B to the F-15C/D in 2004.[36] These planes came from Kadena Air Base.[16]

BRAC 2005

edit

The Base Realignment and Closure 2005 commission originally planned to close Otis Air National Guard Base and dissolve the 102nd.[37] Locals argued that this would leave a huge gap in the national air defenses. Commission officials, after visiting the base, decided to keep it open, but the 102nd would still lose its planes, only this time they were only going to the 104th Fighter Wing, based at Barnes Municipal Airport.[20]

In May 2006 it trained with the Israeli Air Force's 115 Squadron.[38]

The wing hosted the Cape Cod Air Show & Open House, its last air show with the F-15C Eagle at the end of Air Force Week in August 2007. The wing shared a commonality with the 101st Air Refueling Wing,[39] the 103d Fighter Wing,[39][40] and the 104th Fighter Wing,[39] which due to commission decisions, also changed the type of planes that they flew. Beginning in 2007, the F-15s began moving to Barnes Municipal Airport. With the grounding of the F-15 Eagles, the 158th Fighter Wing, which is based in Vermont took over the role of patrolling the Northeast's skies earlier than expected.[41] This interruption of the F-15's flight, coinciding with the transitioning of the fighter jets to the 104th Fighter Wing, created some issues.[41]

 
F-15 From 101st Fighter Squadron during the 2007 Cape Cod Air Show

On 24 January 2008, the 102nd Fighter Wing flew its last patrol mission.[20] The unit is wing commander, Colonel Anthony Schiavi, led the flight, accompanied by Major Daniel Nash, who was one of the first responders for 9/11. Fire trucks were on hand when the team landed a half-hour later, giving the planes and the pilots the customary ceremonial hose-down for the last time.[20]

2008: new mission

edit

When it was announced that the wing would be restructured and Otis Air National Guard Base would remain open, discussions began about the future of the 102nd. Staff of the 102nd and those at Massachusetts Air National Guard headquarters considered a plan centered on the idea that the wing could transition to an intelligence mission to support the growing War on Terror. The idea hit a roadblock when it was announced that the funds which the wing could use to convert into its new mission had been depleted.[42]

Eventually, Governor Deval Patrick announced that the wing would adopt an intelligence role as soon as the aircraft left.[43]

Original Base Realignment and Closure commission plans only hinted at a Distributed Common Ground System being created at Otis.[44] These plans did not include the air guardsmen affected by the loss of their jobs. The issue was resolved when the Air Force announced its plans, right before the F-15s started to leave for Barnes.[43]

Members of the wing had the option of moving with the F-15s to Barnes, but most decided to stay behind and train for new missions. The crash trucks went to Barnes, leaving the brush breakers of the Massachusetts Military Reservation behind. The buildings formerly occupied by the fighter wing, including the hangars, will be occupied by the intelligence mission.[42]

On 6 November 2009, ground was broken on new facilities for the 102nd Intelligence Wing. The building was to eventually replace the temporary facilities in which the wing was then operating.[45]

Intelligence leak

edit

In an article published on April 13, 2023, the New York Times revealed that the individual responsible for the 2023 Pentagon document leaks was a junior enlisted member of the 102nd.[46][47] The FBI arrested Airman 1st Class Jack Teixeira, cyber transport systems journeyman of the 102nd Intelligence Wing, Joint Base Cape Cod for allegedly uploading Top Secret information to a Discord server.[48] Teixeira was stationed at Fort Bragg during the time of the data leaks, which were widely reported.[48]

The detachment commander and operations commander of the 102nd Intelligence Support Squadron have both been suspended, pending completion of the Inspector General's investigation into the leak; both commanders have also lost their access to classified data.[49] Other airmen from the unit are sidelined from the primary mission of the 102nd.[50]

Texeira was observed making notes on the intelligence stream and was warned about his behavior.[51] Texeira has been indicted on six counts; after the warnings, authorities were baffled over how long Texeira was allowed to continue to operate at the Air National Guard Base.[48][52][53] See Need to know

In response, the Pentagon is instituting °Top Secret Control Officers,[54] °plans for electronic device detection systems suitable for classified, secret, and top secret areas, and °an office to address insider threats. The Justice department said each violation for "Unauthorized retention and transmission of national defense information provides for a sentence of up to 10 years in prison, up to three years of supervised release, and a fine of up to $250,000".[54] [55]

On 11 December 2023 Wing Commander Sean Riley was relieved of command, and 14 others were disciplined.[56]

Formation of A-staff

edit

On 28 June 2023 the 102nd Wing commander announced the formation of an A-staff to operate in parallel with wing staff;[57] from twenty to twenty-six positions would reach initial operating capability (IOC) on 1 October 2023.[57] The A-staff would have crisis action planning capability to off-load demands on the operational wing;[57] the A-staff will have functional directorates (A-1: Manpower, Personnel and Services, A-2/3/5: Intelligence, Operations and Strategic Plans, A-4: Logistics and Engineering, and A-6: Communications), each reporting to the wing's chief of staff. 102nd IW will serve as test unit for non-flying wings,[57] and a beta site for ISR (Intelligence, surveillance and reconnaissance).[58] Corresponding A-staffs are being formed, for example at Air Task Forces (ATFs) as a test.[59]

References

edit
  1. ^ a b c Middleton, Ken (22 January 2008). "102nd Fighter Wing". Archived from the original on 3 October 2016. Retrieved 10 November 2016.
  2. ^ "Commander Environmental Statement" (PDF). 102IW Public Affairs office. 22 January 2008. Archived from the original (PDF) on 10 September 2008. Retrieved 29 May 2008.
  3. ^ "A change of the Guard at Otis". Massachusetts National Guard. 7 April 2008. Archived from the original on 18 May 2011. Retrieved 29 May 2008.
  4. ^ a b "102 IW Mission". 102nd Intelligence Wing Public Affairs Office. Archived from the original on 14 July 2009. Retrieved 23 April 2009.
  5. ^ Reuters (19 Apr 2023) Alleged leaker Teixeira's unit ordered to halt intelligence mission -Air Force
  6. ^ AP (18 Apr 2023) Air Force unit in document leaks case loses intel mission
  7. ^ LOLITA C. BALDOR and TARA COPP (19 Apr 2023) Air National Guardsman age not key in Pentagon leaks: Austin
  8. ^ Leo Shane III (1 Jun 2023) Top National Guard officer vows intel leaks 'will never happen again'
  9. ^ Audrey Decker (31 May 2024) Air Force unit resumes intel ops after Discord leak
  10. ^ "Units". Falmouth, Massachusetts: 102nd Intelligence Wing Public Affairs Office. 2010. Retrieved 27 April 2010.
  11. ^ "FY05 Annual Report Final" (PDF). Massachusetts National Guard. 29 May 2008. Archived from the original (PDF) on 3 August 2008. Retrieved 29 May 2008.
  12. ^ Martinez, Luis (18 April 2023). "Air Force opens own investigation into secret documents leak". ABC News. Retrieved 18 April 2023.
  13. ^ a b c "Air Force Combat Units of World War II – Part 5". Maurer, Maurer. 1986. Archived from the original on 27 December 2007. Retrieved 10 August 2008.
  14. ^ a b c d e f g h i j k l m n o p "Commonwealth of Massachusetts Military Division, Air National Guard History". National Guard Museum & Archives. 29 May 2008. Archived from the original on 29 October 2016. Retrieved 10 November 2016.
  15. ^ a b "Today in Guard History (August) History". National Guard. 2008. Archived from the original on 10 November 2016. Retrieved 10 November 2016.
  16. ^ a b c d e f "The 102nd Fighter Wing". Philippe Colin. 22 January 2008. Archived from the original on 27 August 2008. Retrieved 29 May 2008.
  17. ^ "390th Fighter Squadron". GlobalSecurity.org. 26 April 2005. Retrieved 27 April 2010.
  18. ^ a b c "Otis Air National Guard Base and the Massachusetts Military Reservation". 102nd Intelligence Wing Public Affairs Office. Archived from the original on 14 July 2009. Retrieved 11 December 2010.
  19. ^ "History of the 102nd Intelligence Wing". United States Air Force. Archived from the original on 22 July 2011. Retrieved 5 May 2010.
  20. ^ a b c d Deluzuriaga, Tania (29 May 2008). "Otis sees its last landing". Boston News. Retrieved 29 May 2008.
  21. ^ a b Baugher, Joe (15 April 2000). "Service of F-15 Eagle with USAF and ANG". Joe Baugher. Archived from the original on 24 November 2010. Retrieved 12 December 2010.
  22. ^ McKenna, Pat. "The Border Guards-NORAD: The eyes and ears of North America". Cheyenne Mountain Air Force Station: United States Air Force. Archived from the original on 11 January 2005. Retrieved 27 April 2010.
  23. ^ "Global Security History of the 101st Fighter Squadron". Global Security. 29 May 2008. Archived from the original on 7 May 2008. Retrieved 29 May 2008.
  24. ^ a b c d e f g h "Profile: Otis Air National Guard Base". Falmouth, Massachusetts: Historycommons.org. 2010. Archived from the original on 26 July 2011. Retrieved 22 April 2010.
  25. ^ Rogers, B. (2006). United States Air Force Unit Designations Since 1978. ISBN 1-85780-197-0
  26. ^ "Flight Path Study – American Airlines Flight 11" (PDF). National Transportation Safety Board. 19 February 2002. Archived from the original (PDF) on 30 May 2008. Retrieved 25 May 2008.
  27. ^ "'We Have Some Planes'". National Commission on Terrorist Attacks Upon the United States. July 2004. Archived from the original on 11 May 2008. Retrieved 25 May 2008.
  28. ^ "9/11 recordings chronicle confusion, delay". CNN. 17 June 2004. Retrieved 24 May 2008.
  29. ^ "US considered 'suicide jet missions'". Falmouth, Massachusetts: BBC. 29 August 2002. Retrieved 23 April 2010.
  30. ^ a b c "Conspiracies!". The Daily Telegraph. London. 7 July 2008. Archived from the original on 7 March 2016. Retrieved 30 July 2008.
  31. ^ Eggen, Dan (2 August 2006). "9/11 Panel Suspected Deception by Pentagon". Washington Post. Retrieved 7 November 2008.
  32. ^ Pike, John (22 January 2009). "Supersonic Transports (SST)". GlobalSecurity.org. Archived from the original on 6 June 2010. Retrieved 27 April 2010.
  33. ^ Blackburn, A.W. (July 1988). "High-Speed Environmental Cruise Concerns". Transportation Research Circular (333). Transportation Research Board of the National Archives. Retrieved 27 April 2010.
  34. ^ Haskell, Bob (28 January 2008). "Air Guard wing ends fighter mission, embraces intelligence". The National Guard. Archived from the original on 10 November 2016. Retrieved 22 December 2010.
  35. ^ "U.S. force buildup under way". USA Today. 20 September 2001. Retrieved 22 November 2008.
  36. ^ "102nd Fighter Wing, Massachusetts ANG". The AMARC Experience. 16 August 2006. Archived from the original on 10 December 2008. Retrieved 22 November 2008.
  37. ^ "Global Security History of the 102nd Fighter Wing". Global Security. 29 May 2008. Archived from the original on 31 May 2008. Retrieved 29 May 2008.
  38. ^ Weiss, Raanan (September 2010). "Dogfighting over the Dunes". Air Forces Monthly (269).
  39. ^ a b c "Displays". capecodairshow2007.org. 2007. Archived from the original on 20 November 2008. Retrieved 7 January 2009.
  40. ^ Haskell, Bob (August 2007). "The on Guard" (PDF). United States Air National Guard. p. 2. Archived from the original (PDF) on 8 October 2011. Retrieved 24 April 2010.
  41. ^ a b "A Falcon for an Eagle". airforce-magazine.com. 14 December 2007. Retrieved 7 November 2008.
  42. ^ a b "New Otis Mission in Limbo". Cape Cod Times. 2 June 2007. Retrieved 29 May 2008.
  43. ^ a b Lehmert, Amanda (17 September 2007). "Otis Air Base 'Secure'". Cape Cod Times. Archived from the original on 9 November 2016. Retrieved 25 November 2008.
  44. ^ "Department of the Air Force" (PDF). United States Air Force. August 2005. Archived from the original (PDF) on 9 January 2009. Retrieved 7 November 2008.
  45. ^ Brennan, George (7 November 2009). "Mission breakthrough at Otis". Cape Cod Times. Otis Air National Guard Base. Archived from the original on 9 November 2009. Retrieved 20 November 2009.
  46. ^ Toler, Aric; Schwirtz, Michael; Willis, Haley; Mellen, Riley; Triebert, Christiaan; Browne, Malachy; Gibbons-Neff, Thomas; Barnes, Julian E. (13 April 2023). "Here's what we know about the leader of the online group where secret documents were leaked". The New York Times. ISSN 0362-4331. Retrieved 13 April 2023.
  47. ^ Harris, Shane (13 April 2023). "Suspected leaker of top-secret Pentagon documents arrested". The Washington Post. Retrieved 15 April 2023. (subscription required)
  48. ^ a b c Geoff Ziezulewicz (13 April 2023) Deputy defense secretary to troops: Don't share classified information
  49. ^ Haley Britzky, Oren Liebermann and Natasha Bertrand, CNN (26 April 2023) Air Force suspends leadership for unit of suspected Pentagon document leaker
  50. ^ Thomas Novelly (19 Apr 2023) Air National Guard Unit Where Alleged Leaker Worked Sidelined from Intelligence Work
  51. ^ Alexander Smith and Ken Dilanian (18 May 2023) Intel leak suspect was caught twice taking notes on classified info but allowed to keep access, prosecutors say
  52. ^ Holmes Lybrand, CNN (15 Jun 2023) 21-year-old guardsman indicted on six counts after allegedly posting classified documents online 21-year-old Texeira's response to the warnings: "IDGAF"
  53. ^ Robert Legare, Andres Triay (29 Feb 2024) Jack Teixeira, alleged Pentagon leaker, to plead guilty 15 superiors enabled the leaks.
  54. ^ a b Reuters (5 July 2023) Pentagon to Tighten Controls on Classified Information After Leak
  55. ^ Caitlin M. Kenney (5 Jul 2023) Pentagon will create office to monitor users and insider threats in wake of leaks "the Joint Management Office for Insider Threat and Cyber Capabilities"
  56. ^ Audrey Decker (11 Dec 2023) USAF cracks down on 'need to know' violations in wake of Discord leaks; WCVB (11 Dec 2023) Members of Mass. Air National Guard unit had opportunities to blunt document leak, Air Force IG finds; Video by Timothy Sandland, 102nd Intelligence Wing (1 Mar 2023) Command Message - March 2023 - Colonel Enrique Dovalo not relieved of command; Brian MacQuarrie (17 Apr 2023) With leak case, Massachusetts Air National Guard is thrust into the spotlight; Photo by Airman 1st Class Julia Ahaesy 102nd Intelligence Wing (4 Jun 2023) 102nd ISRG participates in Resiliency Tactical Pause Image 7 of 7; Jeff Schogol, Task & Purpose (11 Dec 2023) Wing commander relieved over Teixeira classified document leak; 102nd ISRG (2023) 102nd Intelligence, Surveillance and Reconnaissance Group;
  57. ^ a b c d Airman 1st Class Julia Ahaesy, 102nd Intelligence Wing (11 Aug 2023) 102nd IW establishes an A-Staff
  58. ^ Rear Admiral Patrick Piercey, U.S. Navy (Retired) (Sep 2023) Planning for the Next War Must Be a Mixture of Art & Science "In recent decades, military planning has leaned more heavily on science than art, but success in a peer-level fight will depend on commander’s intent and the art of warfare". Proceedings of US Naval Institute vol 149 (9) #1,447
  59. ^ Greg Hadley (19 Sep 2023) USAF Will Test Out a New Way to Organize Deployments: Air Task Forces

Further reading

edit
 
Wikimedia Commons has media related to 102d Intelligence Wing (United States Air Force).
edit

Retrieved from "https://en.wikipedia.org/w/index.php?title=102nd_Intelligence_Wing&oldid=1251309834"