F-16 Reference

F-16 Aircraft Database

F-16 Accident Reports for 1993

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



Found 40 aircraft, displaying 31- 40 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
08 Oct 1993 [ w/o] 91350 91- 0350 USAF 23 FS F-16C Block 50 C Details
The aircraft crashed at 18:30 hours on a delivery flight at Remsen, near Griffiss AFB, New York. Air Force investigators have concluded that night fog and a blown fuse in instruments that receive landing information were the cause of the crash. Because of this situation the pilot had to divert, but the engine cut due to fuel starvation. The pilot, Captain Robert 'Rob' Swaringen, ejected safely. The F-16 cut a 1,000-foot swath through the trees off Joslyn Road before coming to rest in a fiery heap 500 feet from the home of Nick and Diane Polce. The aircraft was being delivered from Fort Worth, Texas to the 23rd FS in Spangdahlem AB, Germany.
08 Nov 1993 [ w/o] 88448 88- 0448 USAF 57 FW F-16C Block 42 C Details
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.
09 Nov 1993 [ w/o] 86325 86- 0325 USAF 120 FS F-16C Block 30 E Details
Went down near Laramie, Wyoming at 14:22 hours. The pilot, Lt. Julian Clay, ejected safely. Cause was an engine failure.
10 Nov 1993 [ w/o] 84607 81- 0937 PAF 38 TW F-16B Block 15 N Details
Crash caused by a birdhit. Both pilots, Squadron Leader Khawaja Abdul Majeed and Squadron Leader Nawaz, ejected safely.
18 Nov 1993 [ act] J-143 85- 0143 RNlAF 314 sqn F-16A Block 15 Y OCU Details
Damaged and repaired
29 Nov 1993 [ w/o] 81770 81- 0770 USAF 114 FS F-16A Block 15 G ADF Details
Lost near Tulelake, California. The pilot, 1st Lieutenant Stephen Taylor, a student pilot from the Vermont ANG, died in the crash. The aircraft was engaged in BVR with an instructor at the time of the crash. Spatial disorientation was most likely the cause.
03 Dec 1993 [ act] 86222 86- 0222 USAF 149 FS F-16C Block 30 C Details
Belly landed Byrd IAP, Richmond, Virginia, but damage was said to be repairable. Said to have accidentally landed on its centre line fuel tank. It was being flown by the Virginia ANG at the time of the mishap. The aircraft was in depot at Ogden ALC, Utah where it was repaired and returned for service with the 149th FS in 1998.
17 Dec 1993 [ w/o] 82927 82- 0927 USAF 184 FS F-16A Block 15 K Details
Collided with an F-15A (75-0054) of the 122th FS over the Atlantic Ocean off Brunswick, Georgia. The pilot, Lieutenant Colonel John Michael Steward, was killed in this mid-air collision. The F-15 pilot ejected safely and was recovered.
21 Dec 1993 [ pre] J-260 78- 0260 RNlAF 323 sqn F-16B Block 1 Details
Ran off the runway at Leeuwarden AB. The two member crew survived. The aircraft is now on display at the Depot Mechanisch Vliegtuigmaterieel en Straalmotoren (Mechanical Aircraft Material and Jet Engine Depot) which is at Woensdrecht AB
23 Dec 1993 [ act] 89091 89- 2091 USAF 112 FS F-16C Block 42 F Details
The right main landing gear failed. This caused the aircraft to skid across runway, two taxi ways and the ramp coming to rest in front of the port authority fire department building. There were no injuries.

First Previous 123


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.