F-16 Reference

F-16 Aircraft Database

Airframe Details for F-16 #79-0365

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

F-16 Aircraft Profile

Aircraft: 79-0365
LM Aero T/V 61-150
Plant General Dynamics
Local C/N
Delivered USAF 79365
F-16A Block 10A
Current USAF 79-0365
F-16A Block 10A
Status [pre]

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

Aircraft History

Date Status Local S/N Airforce/Unit Version Name Info
21 Jan 1981 [act] 79365 F-16A Block 10A
22 Jan 1981 [act] 79365 USAF 428 TFS 'NA' F-16A Block 10A
11 Mar 1986 [msh] 79365 USAF 428 TFS 'NA' F-16A Block 10A
Collided with #79-0367 and although extensively damaged it was able to land at Gila Bend AP.
Oct 1986 [act] 79365 USAF 428 TFS 'NA' F-16A Block 10A
Special characteristics:
  • Unit Markings: 474 TFW
Jun 1989 [act] 79365 USAF 89 TFS 'DO' F-16A Block 10A " City of Youngstown"
01 Feb 1992 [act] 79365 USAF 89 FS 'DO' F-16A Block 10A
20 Jun 1994 [sto] AAFG0171 USAF AMARC 'DO' F-16A Block 10A
04 Mar 2024 [pre] 79-0365 'DO' F-16A Block 10A
To be preserved at the March Field museum.

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

Please use this form to add any list any error or omissions you find in the above text.

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.