F-16 Reference

F-16 Aircraft Database

Airframe Details for F-16 #84-1358

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

F-16 Aircraft Profile

Aircraft: 84-1358
LM Aero T/V 6D-115
Plant Fokker
Local C/N L-219
Delivered RNlAF J-358
F-16A Block 15W
Current RNlAF J-358
F-16A Block 15W
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
03 Sep 1986 [act] J-358 F-16A Block 15W
05 Sep 1986 [act] J-358 RNlAF 315 sqn F-16A Block 15W
Jul 1987 [act] J-358 RNlAF 315 sqn F-16A Block 15W
Special characteristics:
  • Special Colorscheme
Tail logo for 35 years of 315 sqn.
Nov 1989 [act] J-358 RNlAF 313 sqn F-16A Block 15W
Jan 1990 [act] J-358 RNlAF 323 sqn F-16A Block 15W
10 May 1990 [msh] J-358 RNlAF 323 sqn F-16A Block 15W
Collided in mid-air with F-16A (78-0258, J-258) thirteen kilometres west of Grand Lake, Canada. The aircraft were flying out of Goosebay. The pilot of this aircraft, Capt. Leo "Moist" Vogt, was killed in the incident
10 May 1990 [w/o] J-358 RNlAF 323 sqn F-16A Block 15W

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.