F-16 Aircraft Database

Airframe Details for F-16 #78-0209




F-16 Aircraft Profile

Aircraft: : 78-0209
LM Aero T/V 6G-6
Plant SABCA
Local C/N B-060
Delivered RDAF ET-209
F-16B Block 10
Current RDAF ET-209
F-16B Block 10
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
14 May 1981 [act] ET-209 F-16B Block 10
Jun 1981 [act] ET-209 RDAF Esk 727 F-16B Block 10
Aug 1982 [act] ET-209 RDAF Esk 730 F-16B Block 10
19 Jun 1984 [msh] ET-209 RDAF Esk 730 F-16B Block 10
Collided over Fyn Island, Denmark, with F-16B (78-0211, ET-211) during a NATO exercise 'Blue Moon' near Assens. The aircraft was flown by Lieutenant Egon Christensen and the back-seat rider was aircraft technician SA Flemming Mortensen. Both crewmembers ejected but hit the canopy and didn't survive. The aircraft were flying in close formation in low altitude with ET-209 in front. During a turn the pilot in ET-211 misunderstood the instructions from the formation leader and collided with ET-209 during the turn.
19 Jun 1984 [w/o] ET-209 RDAF Esk 730 F-16B Block 10

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



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.