F-16 Aircraft Database

Airframe Details for F-16 #86-0275




F-16 Aircraft Profile

Aircraft: : 86-0275
LM Aero T/V 5C-381
Plant General Dynamics
Local C/N
Delivered USAF 86275
F-16C Block 30D
Current USAF 86275
F-16C Block 30D
Status [scr]

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

Aircraft History

Date Status Local S/N Airforce/Unit Version Name Info
18 Nov 1987 [act] 86275 F-16C Block 30D
Dec 1987 [act] 86275 USAF 35 TFS 'WP' F-16C Block 30D
01 Oct 1991 [act] 86275 USAF 35 FS 'WP' F-16C Block 30D
27 Jul 1993 [msh] 86275 USAF 35 FS 'WP' F-16C Block 30D
In poor weather this F-16 landed on top of F-16C (87-0335) which was trying to take off . Pilot Lt. Col. Ralph Earl "Bark" Gardner who had just arrived at Kunsan AB, Korea from MacDill AFB was killed. The 56th FW which was closing down had just enough aircraft to fly for his memorial.
27 Jul 1993 [w/o] 86275 USAF 35 FS 'WP' F-16C Block 30D
Unknown [scr] 86275 F-16C Block 30D
This aircraft and an unused F-101F ABDR 59-0454 were cut into pieces at Kunsan AB, ROK so could be hauled off to a scrapper sometime during 1995.

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.



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.