F-16 Reference
5th Gen Fighters
|
Found 24 aircraft, displaying 1-9
[Sorted by Date]
Abbreviations and symbols:
| [act] |
Active |
[msh] |
Involved in Mishap |
[w/o] |
Write-off |
| [cld] |
Cancelled Order |
[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 |
| [i/a] |
Instructional Airframe |
[sto] |
Stored (e.g. at AMARG) |
|
|
Errors and Omissions
Jun 03, 2007 - 07:29 PM
|
Oct 16, 2006
Crashed Oct 16, 2006 F-16C near Bitlis, Turkey. 1st Lt.Bahadir Sahin killed
|
Bjorn
Jun 25, 2007 - 06:23 PM
|
05/23/2006
Crash of an unknown Turkish viper, 192 Filo. http://www.f-16.net/news_article1809.html
|
orko_8
Feb 10, 2009 - 11:22 AM
|
05/23/2006
93-0684, F-16C Block 50, 1st Lt Halil Ibrahim Ozdemir ejected safely.
|
Jon
Feb 20, 2009 - 05:58 AM
|
Can't be 93-0684 it was...
photographed in 2007: http://www.f-16.net/gallery_item247966_size5.html Or did the pilot eject and the aircraft was still repaired? Something like a ground ejection.
|
Fantasma337
Apr 15, 2009 - 01:01 AM
|
93-0684
The a/c of Ozdemir was blown apart in the midair and sank to the sea, no chance for repair. So the question of its real s/n remains unanswered unless the a/c photographed in 2007 has a fake s/n painted on it.
|
Bjorn
May 12, 2009 - 04:49 PM
|
April 14th, 2009
Turkish F-16 crashed killing the pilot.
|
Bjorn
Jan 30, 2011 - 10:34 PM
|
More unconfirmed crashes
July 25th, 1997: Eskisehir, pilot ejected. November 6th, 1997: 131 Filo, crashed near Asagi Pinarbasi with Lt. Mustafa Gumus and 2nd Lt. Tugkan Inan ejecting. August 26th, 1999: 182 Filo, Lt. Ozcan Kete ejected. June 27th, 2001: 143 Filo, Capt. N. Tunc Sözen ejected. September 25th, 2001: no more info. If anyone has more info, please let us know!
|
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.
|
|
|