F-16 Aircraft Database

Airframe Details for F-16 #88-0448

F-16 Aircraft Profile

Aircraft: : 88-0448
LM Aero T/V 1C-50
Plant General Dynamics
Local C/N
Delivered USAF 88448
F-16C Block 42C
Current USAF 88448
F-16C Block 42C
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 Dec 1989 [act] 88448 F-16C Block 42C
04 Jan 1990 [act] 88448 USAF 310 TFTS 'LF' F-16C Block 42C
01 Oct 1991 [act] 88448 USAF 310 FS 'LF' F-16C Block 42C
Oct 1992 [act] 88448 USAF 57 FW 'WA' F-16C Block 42C
08 Nov 1993 [msh] 88448 USAF 57 FW 'WA' F-16C Block 42C
The aircraft flew into teraain 17 miles southwest of Alamo, Nevada at 15:17 hours with the pilot, Captain John M. Barelka, didn't eject. Probable cause was G-excess effect.
08 Nov 1993 [w/o] 88448 USAF 57 FW 'WA' F-16C Block 42C 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.

MSgt. Kevin Patrick

Crew Chief Profile
310th Fighter Squadron "Tophats" , 1989 -
Crewed jet until we swapped Nellis this F-16C for a block 42 F-16D (89-2157) which became my jet. '448 crashed about six months or so after transfer to Nellis.

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.