F-16 Reference

F-16 Aircraft Database

F-16 Accidents & Mishaps for the Royal Jordanian Air Force

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

Found 7 aircraft, displaying 1- 7 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
14 Jan 2016 [ w/o] 159 78- 0166 RJAF 1 sqn F-16B Block 20 MLU Details
Crashed with both pilots escaping unharmed.
20 Apr 2008 [ w/o] 224 80- 0582 RJAF 2 sqn F-16A Block 15 A ADF News Article Details
Lost during a routine training mission sadly killing the pilot Hamzah Samir Odeh Al-Abbadi. The crash occured at 13:10 hours.
28 Sep 2010 [ w/o] 140 80- 3549 RJAF 1 sqn F-16A Block 20 MLU Details
05 Dec 2016 [ w/o] 145 80- 3564 RJAF 1 sqn F-16A Block 20 MLU News Article Details
The aircraft crashed due to a technical malfunction. The pilot, Maj. Ayed Ahmad al-De'ajah, was unfortunately killed.
08 Feb 2011 [ w/o] 146 80- 3565 RJAF 1 sqn F-16A Block 20 MLU Details
01 Sep 2002 [ w/o] 229 81- 0672 RJAF 2 sqn F-16A Block 15 C ADF Details
The aircraft broke its left main landing gear during landing and it subsequently exited the runway. The pilot, Firas Masaedeh, ejected safely.
Unknown [ w/o] 157 88- 0045 RJAF 1 sqn F-16A Block 20 MLU Details
Suffered a mishap at an unknown date.

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.