F-16 Reference

F-16 Aircraft Database

Airframe Details for F-16 #78-0211

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



F-16 Aircraft Profile

Aircraft: 78-0211
LM Aero T/V 6G-8
Plant SABCA
Local C/N B-086
Delivered RDAF ET-211
F-16B Block 10B
Current RDAF ET-211
F-16B Block 10B
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
04 Feb 1982 [act] ET-211 F-16B Block 10B
05 Feb 1982 [act] ET-211 RDAF Esk 727 F-16B Block 10B
May 1984 [act] ET-211 RDAF Esk 730 F-16B Block 10B
19 Jun 1984 [msh] ET-211 RDAF Esk 730 F-16B Block 10B
Collided over Fyn Island, Denmark, with F-16B (78-0209, ET-209) during a NATO exercise 'Blue Moon' near Assens. The pilot, Captain Ole Brian Lessel, ejected safely. He was the only one aboard. 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-211 RDAF Esk 730 F-16B Block 10B

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




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.