F-16 Aircraft Database

F-16 Accidents & Mishaps for the Belgian Air Force




Found 60 aircraft, displaying advertising.html-14 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
02 Sep 1985 [w/o] FA-06 78-0121 BAF 350 sqn F-16A Block 1 Details
Crashed at Havrenne (near Rochefort), Belgium after Captain Etienne De Meulenaer ejected safely
10 Nov 1983 [w/o] FA-07 78-0122 BAF 350 sqn F-16A Block 1 Details
Collided in mid-air with Belgium F-16A (78-0156, FA-41) near Opont, Belgium. Pilot of this aircraft was Lieutenant Roger Uytterhagen
28 Jul 1980 [i/a] FA-08 78-0123 BAF 349 sqn F-16A Block 1 Details
After a flame-out the pilot managed to restart the engine, but crashed nevertheless near Obaix-Buzet, Belgium. The wreck was later used at Florennes for BDRT. Captain Henri Malaise ejected
12 Mar 1981 [w/o] FA-11 78-0126 BAF 349 sqn F-16A Block 1 Details
Crashed near Ville-du-Bois (not far from Vielsalm), Belgium killing pilot Captain Jean-Marie Paul. During a low level interception an actuator from the leading edge automatic flap broke
19 Oct 1989 [w/o] FA-12 78-0127 BAF 350 sqn F-16A Block 1 Details
Destroyed in a mid-air with F-16A (80-3545, FA-54) near Kirgirac, Turkey. The pilot, Captain Guy de Walsche, was killed
10 May 1983 [w/o] FA-13 78-0128 BAF 349 sqn F-16A Block 1 Details
Impacted the ground near Bierbeek, Belgium after the pilot, Captain Herman Devos, ejected safely
19 Jan 1982 [w/o] FA-14 78-0129 BAF 350 sqn F-16A Block 1 Details
Collided with another Belgian F-16A (78-0150, FA-35) at 20,000 feet over Wavreille (near Rochefort) in Southern Belgium. Lieutenant Colonel Steve Nuyts, ejected safely. Steve was the leader of the Slivers aerobatic team which operated two F-104G Starfighters
17 Nov 1988 [w/o] FA-15 78-0130 BAF 350 sqn F-16A Block 1 Details
Crashed near Beauvechain, Belgium after a bird strike. Pilot, Captain Louis Wolfs, ejected safely
29 Apr 1985 [w/o] FA-24 78-0139 BAF 350 sqn F-16A Block 5 Details
Impacted the ground at Court St. Etienne, Belgium when Slt. Konrad Pauwels became disorientated and was killed
22 Oct 1981 [w/o] FA-29 78-0144 BAF 350 sqn F-16A Block 10 Details
Crashed after the aircraft suffered an engine flame-out, in Soumoy, Belgium. Lieutenant Roger Uytterhagen ejected safely
19 Sep 1987 [act] FA-31 78-0146 F-16A Block 10A Details
Collided with F-16A (FA-52, 80-3543) 30 km South-west of Limoges, France. The pilot, Captain Danny Faye, managed to make an emergency landing at Limoges. Aircraft was repaired
19 Aug 1986 [w/o] FA-33 78-0148 BAF 350 sqn F-16A Block 10A Details
Went down near Maubeuge (Ferrier-La-Petite), France. Pilot, Major Gommaire Van Beneden, ejected safely
19 Jan 1982 [w/o] FA-35 78-0150 BAF 350 sqn F-16A Block 10A Details
Collided with another Belgian F-16A (78-0129, FA-14) near Wavreille (near Rochefort). The pilot of this aircraft, Captain Jean Marie Debaix was killed
23 Mar 1999 [w/o] FA-39 78-0154 BAF 2 sqn F-16A Block 10B News Article Details
Crashed near Dinant, Belgium around 21:30 hours while training for air combat. Captain Frédéric Desirotte did not eject and was killed in the mishap
10 Nov 1983 [w/o] FA-41 78-0156 BAF 350 sqn F-16A Block 10B Details
Collided in mid-air with Belgium F-16A (78-0122, FA-07) near Opont, Belgium. Piloted by Captain Michel Thibaut

1234 Next Last


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.