F-16 Aircraft Database

Airframe Details for F-16 #91-0469




F-16 Aircraft Profile

Aircraft: : 91-0469
LM Aero T/V CD-24
Plant General Dynamics
Local C/N
Delivered USAF 91469
F-16D Block 50D
Current USAF 91469
F-16D Block 50D
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
28 Oct 1993 [act] 91469 F-16D Block 50D
Nov 1993 [act] 91469 USAF 85 TES 'OT' F-16D Block 50D
Test bed for the HTS pod in early 1994.
Apr 1994 [act] 91469 USAF 78 FS 'SW' F-16D Block 50D
Oct 2004 [act] 91469 USAF 55 FS 'SW' F-16D Block 50D
18 Apr 2005 [msh] 91469 USAF 55 FS 'SW' F-16D Block 50D
Crashed into a marshland area next to Ashley River near Charleston, South Carolina at about 5 pm local time. The aircraft was from the 55th FS but the crew were from the 77th FS. Both of them (Major Steve Granger and Lt.Col. Maurice Salcedo) ejected safely and walked away but were examined at hospital as a precaution. The aircraft was on a routine training mission when it lost engine power.
18 Apr 2005 [w/o] 91469 USAF 55 FS 'SW' F-16D Block 50D AIB Report

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.