F-16 Aircraft Database

Airframe Details for F-16 #84-1279




F-16 Aircraft Profile

Aircraft: : 84-1279
LM Aero T/V 5C-116
Plant General Dynamics
Local C/N
Delivered USAF 84279
F-16C Block 25D
Current USAF 84279
F-16C Block 25D
Status [w/o]

⇦ Copy-paste this code to link this airframe from our forum

Aircraft History

Date Status Local S/N Airforce/Unit Version Name Info
17 Jan 1986 [act] 84279 F-16C Block 25D
Feb 1986 [act] 84279 USAF 526 TFS 'RS' F-16C Block 25D
Nov 1986 [act] 84279 USAF 313 TFS 'HR' F-16C Block 25D
Jun 1991 [act] 84279 USAF 127 TFTS F-16C Block 25D "MATO PO TAN'KA"
15 Mar 1992 [act] 84279 USAF 127 FS F-16C Block 25D
Aug 1994 [act] 84279 USAF 194 FS F-16C Block 25D
19 Jan 2007 [msh] 84279 USAF 194 FS F-16C Block 25D News Article
The aircraft crashed near Owens Lake in remote eastern California. The pilot ejected safely and was not hurt. An engine failure caused the pilot to bail out during a training exercise.
19 Jan 2007 [w/o] 84279 USAF 194 FS F-16C Block 25D AIB Report

Crew Chief Comments

Create your own Crew Chief Profile
If you crewed this jet and want to leave a comment, you can create your own profile in our Crew Chief Profiles section.

TSgt. Paul Whynot

Crew Chief Profile
313th Tactical Fighter Squadron "Lucky Puppies" , -


Abbreviations and symbols:
[act] Active [i/a] Instructional Airframe [sto] Stored (e.g. at AMARG)
[cld] Cancelled Order [msh] Involved in Mishap [w/o] Write-off
[con] Converted [o/o] On Order
[des] Destroyed (drone) [pre] Preserved (museum, gateguard) T/V LM Aero Type/Version (Construction) number
[emb] Embargoed [scr] Scrapped Photo Available



Any aircraft or serials missing from this list? Did you see incorrect, incomplete, or outdated data?
Add your corrections at the bottom of this page or send them to us!
[Back to the F-16 Aircraft Database]


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.