312th Tactical Fighter Training Squadron (USAF AETC)

"Scorpions" 

312 TFTS "Scorpions" (USAF AETC)
Status:
Disbanded
Version: F-16C/D block 42
Role:Training
Tailband: Black & Red
Motto: N/A
Badge: N/A
Disbanded on January 18th, 1991.

Sideways profile for the 312th TFTS in 1987.

F-16 History

In order to keep up with qualifying enough pilots to match the production of F-16s coming out of Fort Worth, new training squadrons needed to be formed. In the mid 1980s there was a real rush at Luke AFB to get these new squadrons operational. To add to the confusion, the latest F-16s were of the new C/D models which required a different training sylabus. In late 1984 the 312th TFTS was formed mostly with F-16C/D block 25s that were coming off the assembly line. On December 7th, 1984 the first aircraft was received, #83-1121, carrying special markings on the fuselage stating it was F-16C No 1. Truthfully the first F-16C was the first production model F-16C #83-1118 which was also received by the 312th TFTS and was also marked with F-16C No1. The squadrons' first commander, Lt. Col. Steve Plummer, and the 314th Operations Officer went for training at the Fort Worth plant from the General Dynamics pilots. When they returned an F-16A to F-16C model conversion syllabus was written. The 312th TFTS was the first unit to receive operational F-16Cs in the form of block 25s.

A majority of the squadrons pilots had just returned from Kunsan which resulted in a tight knit group with close to a dozen former 35th TFS and a few 80th TFS guys.

First couple of years were spent flying the CX course. This consisted of six or more flights teaching A model Viper pilots the C model differences which also included using the F-16D version.


First production model of the F-16D #83-1174 of the 312th TFTS at Luke AFB, Arizona. After many years with other squadrons, it returned to Luke AFB, but now with the 62nd FS. [Photo by Mike Kopack]

In the late 1980s the 312th TFTS began instructing FMS students in CX-I courses. Teaching pilots from countries such as Korea, Egypt and many other nations the CX and then straight into an Instructor course. The following is a quote from a 312th pilot who talked about early training days with the RoKAF and delivery of some of their Vipers: Not all bad...got to deliver the first two RoKAF F-16Ds to Kunsan with Wolfman Cary. Flew the pond with the two RoKAF guys in the backseat. Not a bad way to travel...Maj. Ko would wake me up for the refuelings. The hop from Hickam to Kunsan was 10.3 hours. Compounded that by having to hang around the EOR after landing for 45 minutes while the ROKs changed the USAF markings to RoKAF so we could taxi in and present the jets to the ROK Chief of Staff. Got presented some RoKAF pilot wings and ate all the snails rolled in peanuts, kimchi, and garlic we could stand.

In late 1989 the squadron began to receive factory fresh F-16C/D block 42s. Unfortunately the 312th TFTS did not last long with the block 42 and disbanded in January of 1991.


USAF F-16C block 25 #84-1255 of the 312th TFTS parked on the flightline. This aircraft was written off on June 27th, 1997. [Photo by Frank Ertl]

Aircraft Markings History

1984 - 1991

Black tail band with red trim adorned the 312th TFTS F-16s with the standard 'LF' tail code used on all Luke Vipers. In some cases, a red star was added to the black stripe. The stars were awards for 'jet of the month' so not all jets had them. They were stenciled on by the Dedicated Crew Chief. The stars stayed on until the next time the aircraft was sent to be painted. More than one star would be applied if the jet was awarded more than once.


Unit History

  • 1942: Activation of the squadron in Harding, Louisiana
  • 1942: P-39 'Airacobra' (part of 58 PG)
  • 1942: P-39 'Airacobra' (Dale Mabry Field, Florida)
  • 1943: P-47 'Thunderbolt' (Perry AAF, Florida)
  • 1944: P-40F 'Warhawk'
  • 1944: Disbanded
  • 1984: Activation of the squadron in Luke, Arizona
  • 1984: F-16C/D 'Fighting Falcon' (part of 58 TTW)
  • 1991: Disbanded

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.