F-16.net

Printed from: F-16.net - The Ultimate F-16 Reference [http://www.f-16.net]
Document title: F-16.net - The Ultimate F-16 Reference
Original URL: http://www.f-16.net/f-16_fighting_falcon_airframe-23.html
Printed on: 11 October 2008

[ Register | Log in ]

F-16 Reference

5th Gen Fighters

F-16 Aircraft Database

F-16 Airframe Details for 78-0013

[Back to F-16 Aircraft Database menu | Missing Photos]

Aircraft Profile

USAF FY/N: 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 the F-16.net forum

Aircraft History

Date

Status

Local S/N

Airforce/Unit

Version

Name

Info

27 Jul 1979

[act]

78013

F-16A Block 1

28 Jul 1979

[act]

78013

388 TFW 'HL'

F-16A Block 1

06 Apr 1981

[msh]

78013

388 TFW 'HL'

F-16A Block 1

Comments:
Crashed at Holloman AFB, New Mexico due to fuel starvation. After being written-off, it was transferred to Lowry TTC as a GF-16A

Jun 1983

[i/a]

78013

F-16A Block 1

Comments:
Lowry AFB, Colorado as GF-16A. Unknown what has happened to this aircraft since training has switched to Sheppard AFB.

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	[msh]	Involved in Mishap	[sto]	Stored (e.g. at AMARC)
[cld]	Cancelled order	[o/o]	On Order	T/V	LM Aero Type/Version (Construction) number
[emb]	Embargoed	[pre]	Preserved (museum, gateguard)	[w/o]	Write-off
[i/a]	Instructional Airframe	[scr]	Scrapped		Photo Available

Any 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

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.