F-16 Aircraft Database

Airframe Details for F-16 #78-0013

F-16 Aircraft Profile

Aircraft: : 78-0013
LM Aero T/V 61-19
Plant General Dynamics
Local C/N
Delivered USAF 78013
F-16A Block 1
Current USAF 78013
F-16A Block 1
Status [i/a]

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

Aircraft History

Date Status Local S/N Airforce/Unit Version Name Info
27 Jul 1979 [act] 78013 F-16A Block 1
31 Jul 1979 [act] 78013 USAF 34 TFS 'HL' F-16A Block 1
06 Apr 1981 [msh] 78013 USAF 34 TFS 'HL' F-16A Block 1
Crashed at Holloman AFB, New Mexico due to fuel starvation. After being written-off, it was transferred to Lowry TTC as a GF-16A
06 Apr 1981 [w/o] 78013 USAF 34 TFS 'HL' F-16A Block 1
Jun 1983 [i/a] 78013 'HL' F-16A Block 1
Lowry AFB, Colorado as GF-16A. Unknown what has happened to this aircraft since training has switched to Sheppard AFB.
Unknown [i/a] 78013 F-16A Block 1
At Eglin AFB, Florida for the Naval School Explosive Ordnance Disposal. It is unknown how long the F-16 has been there but was first pointed out to F-16.net in December 2008. The school itself started in April of 1999.

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.