⇦ Copy-paste this code to link this airframe from our forum
Aircraft History
Date
Status
Local S/N
Airforce/Unit
Version
Name
Info
27 Feb 1981
[act]
283
F-16A
Block 5
03 Mar 1981
[act]
283
RNoAF 332 skv
F-16A
Block 5
Oct 1982
[act]
283
RNoAF 331 skv
F-16A
Block 5
31 Jan 1983
[msh]
283
RNoAF 331 skv
F-16A
Block 5
Crashed in Tysfjord, Norway after it hit and cut two out of three power cables crossing the fjord. The two power cables that were hit were properly marked, while the remaining third power cable was unmarked. The aircraft was part of a flight of three RNoAF F-16s, but was lower and in front of his formation when it hit the power cables. A power cable hit just above the pitot tube, scraping up the radome and cutting of the canopy, the HUD and the top 50cm of the rudder. Needles to say, with the high position of the pilot, he was killed instantly. The plane continued forward in slight descending angle, hitting the tip of a perpendicular aligned mountain ridge spreading debris out between 2 and 5 km, with a lot ending up in the fjord. There where eye witnesses to the incident in a nearby village. During the next 3 days over 1 meter (3.5 feet) of snow fell in the area. Although the pilot was found and identified, the snow made it impossible to find more than just a few bits of the plane. It was spring before the area could be searched properly. It was later determined that the pilot was looking out to the side when his plane hit the power cables, so he never knew what happened. The crash was considered a pilot error. The pilot apparently had less than a week left of his mandatory service and had a job as an airline pilot lined up
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.