35th Fighter Squadron (USAF PACAF)

"Pantons" 

35 FS "Pantons" (USAF PACAF)
Status:
Active
Version: F-16C/D block 40
Role:Attack
Tailband: Blue
Motto: First to Fight
Badge: N/A

Sideways profile for the 35th FS in 2008 with unit markings on the tail.

F-16 History

Starting in 1981 the 35th TFS started to receive vipers to replace the F-4D Phantoms. Factory fresh F-16A/B block 15s were delivered over that year. The USAF always saw that the Korean based units received the newest technology first. Korea at that time was at least as important as the European theatre. The squadron was tasked with air defense as well as both conventional attack as nuclear strike. In late 1987 the squadron again received band-new F-16s, this time C and D models of the block 30 version. They had the so-called ‘big inlet’ from the start gaining the full extent of the General Electric F110 engine. The squadrons’ F-16A/B block 15s were sent to Shaw & Moody AFB. The mission of the squadron remained practically the same.

Ushering in a new era for F-16 operations with the unit was the conversion to block 40 airframes. On November 17th, 2000 three block 40s landed at Kunsan AB destined for the 35th FS. These block 40s came from Moody AFB which was closing down at that time. The block 30s that had been operated before were taken by the 80th FS, 93rd FS and the 186th FS throughout 2000 and 2001. This meant the squadron’s task changed somewhat as advanced targeting both during the day and night became possible. By that time the squadron had already given up its strike task, that was abandoned back in 1991.


USAF F-16C block 30 #86-0290 from the 35th FS has been equipped with a SUU-20 training pod under a wing station. [Photo by Mike Kopack]

In its history the squadron has flown the exact same models of aircraft as its sister squadron, the 80th FS. However, the 80th would remain in the block 30. It did give the 8th FW more flexibility by offering two distinctive capabilities that the different blocks offered. By February of 2001 the squadron received its full strength of block 40s. This ultimately changed in January of 2008 when the 80th FS gave up its block 30s to the newly formed 18th AS and received their block 40s from when the squadron was a normal fighter squadron. So as of 2008 the 8th FW flew both the block 40 versions.

In an interesting move by the RoKAF, a new squadron was set up by the Koreans. This was the 111th FS. It is unique as this RoKAF F-16 squadron would be based alongside the USAFs 8th FW at Kunsan AB. In October of 2007 the 35th FS briefed, flew and debriefed on the same mission side-by-side with the RoKAF’s 111th FS.


USAF F-16C block 30 #88-0406 of the 35th FS parked in an open shelter with opened canopy at Kunsan AB. [Photo by Alec Fushi]

Aircraft Markings History

1981 - 1987

The tail consist of a blue tailband with the 'WP' tailcode in the center - meaning Wolf Pack - and the serial underneath with the colored PACAF logo underneath the tailband.

1987 - present

With the introduction of the C/D models the design was changed slightly. The PACAF logo was retained but in toned down colors and a wolfs head - which previously adorned the side of the airframe - was moved to the tail and placed between the tailcode and PACAF logo.


Unit History

  • 1917: Activation of the squadron in Camp Kelly, Texas
  • 1917: No aircraft assigned (part of 3 AIC)
  • 1917: No aircraft assigned (Etampes [Fr.])
  • 1917: No aircraft assigned (Paris [Fr.])
  • 1917: No aircraft assigned (Issoudun [Fr.])
  • 1919: No aircraft assigned (Clisson [Fr.])
  • 1919: No aircraft assigned (St. Nazaire [Fr.])
  • 1919: No aircraft assigned (Garden City, New York)
  • 1919: Disbanded
  • 1932: Activation of the squadron in Langley Field, Virginia
  • 1932: P-12 (part of 8 PG)
  • 1936: P-30
  • 1939: P-36 'Hawk'
  • 1940: P-40 'Warhawk' (Mitchell Field, New York)
  • 1941: P-39 'Airacobra'
  • 1942: P-39 'Airacobra' (Brisbane [Aus.])
  • 1942: P-39 'Airacobra' (part of 8 FG, Port Moresby [N. Gui.])
  • 1942: P-39 'Airacobra' (Woodstock [Aus.])
  • 1942: P-39 'Airacobra' (Townsville [Aus.])
  • 1942: P-39 'Airacobra' (Milne Bay [N. Gui.])
  • 1943: P-40 'Warhawk' (Mareeba [Aus.])
  • 1943: P-40 'Warhawk' (Port Moresby [N. Gui.])
  • 1943: P-40 'Warhawk' (Finschhafen [N. Gui.])
  • 1944: P-38 'Lightning' (Cape Gloucester [N. Brit.])
  • 1944: P-38 'Lightning' (Nadzab [N. Gui.])
  • 1944: P-38 'Lightning' (Owi [Indo.])
  • 1944: P-38 'Lightning' (Morotai [Indo.])
  • 1944: P-38 'Lightning' (Dulag [Phil.])
  • 1944: P-38 'Lightning' (San Jose [Phil.])
  • 1945: P-38 'Lightning' (Fukuoka [Jap.])
  • 1946: P-38 'Lightning' (Ashiya AB [Jap.])
  • 1946: P-51 'Mustang' (Itazuke AB [Jap.])
  • 1947: P-51 'Mustang' (Ashiya AB [Jap.])
  • 1948: P-51 'Mustang' (Miho AB [Jap.])
  • 1949: P-51 'Mustang' (Itazuke AB [Jap.])
  • 1950: P-80C 'Shooting Star' (part of 8 FBG, Tsuiki AB [Jap.])
  • 1950: P-80C 'Shooting Star' (Suwon AB [S. Kor.])
  • 1950: P-80C 'Shooting Star' (Kimpo AB [S. Kor.])
  • 1950: P-80C 'Shooting Star' (Pyongyang [N. Kor.])
  • 1950: P-80C 'Shooting Star' (Seoul AB [S. Kor.])
  • 1950: P-80C 'Shooting Star' (Itazuke AB [Jap.])
  • 1951: P-80C 'Shooting Star' (Kimpo AB [S. Kor.])
  • 1951: P-80C 'Shooting Star' (Suwon AB [S. Kor.])
  • 1953: F-86F 'Sabre'
  • 1954: F-86F 'Sabre' (Itazuke AB [Jap.])
  • 1957: F-100D/F 'Super Sabre'
  • 1958: F-100D/F 'Super Sabre' (part of 8 TFW)
  • 1963: F-105D 'Thunderchief'
  • 1964: F-105D 'Thunderchief' (part of 41 AD, Yokota AB [Jap.])
  • 1964: F-105D 'Thunderchief' (Korat AB [Thai.])
  • 1965: F-105D 'Thunderchief' (part of 6441 TFW, Takhli AB [Thai.])
  • 1966: F-105D 'Thunderchief' (part of 41 AD)
  • 1966: F-105D 'Thunderchief' (part of 347 TFW, Osan AB [S. Kor.])
  • 1967: F-4C 'Phantom II'
  • 1971: F-4D 'Phantom II' (part of 3 TFW, Kunsan AB [S. Kor.])
  • 1974: F-4D 'Phantom II' (part of 8 TFW)
  • 1981: F-16A/B 'Fighting Falcon'
  • 1987: F-16C/D 'Fighting Falcon'
  • 1992: F-16C/D 'Fighting Falcon' (part of 35 FW)
  • 1994: F-16C/D 'Fighting Falcon' (part of 35 OG)

F-16 Airframe Inventory

Photos

Errors and Omissions



Note: Errors and omissions in the above text can be added here. Please note: your comments will be displayed immediately on this page.

If you wish to send a private comment to the webmasters, please use the Contact Us link.