F-16 Aircraft Database

Airframe Details for F-16 #80-0606




F-16 Aircraft Profile

Aircraft: : 80-0606
LM Aero T/V 61-327
Plant General Dynamics
Local C/N
Delivered USAF 80606
F-16A Block 15B
Current USAF 80606
F-16A Block 15B
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
22 Apr 1982 [act] 80606 F-16A Block 15B
May 1982 [act] 80606 USAF 496 TFS 'HR' F-16A Block 15B
30 Jul 1985 [msh] 80606 USAF 496 TFS 'HR' F-16A Block 15B
Caught fire at Hahn AFB, Germany and was destroyed on the runway. Pilot Mike Jaensch, ejected from the air plane safely.
30 Jul 1985 [w/o] 80606 USAF 496 TFS 'HR' F-16A Block 15B
We have information that this airframe was rebuilt after the fire. Investigation found that when the pilot on take off went into full after burner, a fan blade from the engine broke off and went into a fuel tank, which caused it it catch fire on the runway. The pilot ejected-unhurt. The jet would have been last seen in 2002 on "Celebrity Row" in the "Bone Yard" in Tucson. Anyone has more information on this?

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.