F-16 Reference

F-16 Aircraft Database

Airframe Details for F-16 #93-0688

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



F-16 Aircraft Profile

Aircraft: 93-0688
LM Aero T/V HC-32
Plant TAI
Local C/N TK-238
Delivered TuAF 93-0688
F-16C Block 50
Current TuAF 93-0688
F-16C Block 50
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
Unknown [act] 93-0688 F-16C Block 50
FMS Program: Peace Onyx II
May 1998 [act] 93-0688 TuAF 192 Filo F-16C Block 50
Nov 1998 [act] 93-0688 TuAF 143 Filo F-16C Block 50
Apr 2000 [act] 93-0688 TuAF 192 Filo F-16C Block 50
Jun 2012 [act] 93-0688 TuAF 151 Filo F-16C Block 50
13 May 2013 [msh] 93-0688 TuAF 151 Filo F-16C Block 50 News Article
The F-16 crashed around 14:15 local time near the town of Yarpuz, in the mountainous southern area of Amansolar in Osmaniye province (about 25 miles (40km) from the Syrian border). The pilot, Lt. Hamza Gümüşsoy, ejected but unfortunately got killed.
13 May 2013 [w/o] 93-0688 TuAF 151 Filo F-16C Block 50

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.