F-16 Reference
5th Gen Fighters
|
Found 22 aircraft, displaying 1-15
[Sorted by Date]
| Date |
Status |
Local S/N |
Aircraft |
AF/Unit |
Version |
Info |
Details |
| 24 Apr 1997 |
[w/o] |
274 |
78-0274
|
RNOAF 332 skv |
F-16A
Block 1
|
|
Details
|
|
|
|
|
Crashed near Bindal, north of Ørland, Norway hitting a high volt power cable. The pilot, Per Morten Storengen, ejected safely.
|
|
| 23 Mar 1992 |
[w/o] |
278 |
78-0278
|
RNOAF 332 skv |
F-16A
Block 5
|
|
Details
|
|
|
|
|
The aircraft was an early block 5, and was lost due to an engine failure at 18,000 feet. After three attempts to relight the engine, the pilot directed the aircraft away from populated areas and ejected at 3,000 feet. This happened near Banak AB, Norway
|
|
| 02 Jun 1981 |
[w/o] |
280 |
78-0280
|
RNOAF 332 skv |
F-16A
Block 5
|
|
Details
|
|
|
|
|
Suffered a collision with a goose and crashed at Lake Tunhovd, Norway. The pilot, Morten Køpke, ejected with minor injuries.
|
|
| 31 Jan 1983 |
[w/o] |
283 |
78-0283
|
RNOAF 331 skv |
F-16A
Block 5
|
|
Details
|
|
|
|
|
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
|
|
| 05 Apr 1989 |
[w/o] |
287 |
78-0287
|
RNOAF 338 skv |
F-16A
Block 10
|
|
Details
|
|
|
|
|
Collided with F-16A (78-0294, 294) over Sula, Norway killing one of the pilots.
|
|
| 15 Sep 1987 |
[w/o] |
290 |
78-0290
|
RNOAF 338 skv |
F-16A
Block 10
|
|
Details
|
|
|
|
|
Crashed near Froya, Norway. The pilot ejected safely.
|
|
| 05 Apr 1989 |
[w/o] |
294 |
78-0294
|
RNOAF 338 skv |
F-16A
Block 10
|
|
Details
|
|
|
|
|
Collided with F-16A (78-0287, 287) over Sula, Norway killing one of the pilots.
|
|
| 22 May 1990 |
[w/o] |
296 |
78-0296
|
RNOAF 338 skv |
F-16A
Block 10
|
|
Details
|
|
|
|
|
Crashed near Houffallize, Belgium. The pilot ejected safely.
|
|
| Feb 2006 |
[i/a] |
298 |
78-0298
|
RNOAF 338 skv |
F-16A
Block 20 MLU
|
|
Details
|
|
|
|
|
Aircraft was struck by lightning. Exact date unknown but most likely was flying at the time as ground lighting in Norway would be rare in the winter time. The aircraft was taken to Kjeller for repairs and inspection.
|
|
| 05 Jul 1988 |
[w/o] |
300 |
78-0300
|
RNOAF 334 skv |
F-16A
Block 15
|
|
Details
|
|
|
|
|
Destroyed in a crash at Morsvikfjord, Norway. The pilot didn't survive the crash.
|
|
| 13 Nov 1984 |
[w/o] |
301 |
78-0301
|
RNOAF 332 skv |
F-16B
Block 1
|
|
Details
|
|
|
|
|
Burnt out on the ground at Rygge AB, Norway. Just as power was increased for take-off a compressor blade came loose and shot up through the fuel tank creating a gaping hole. Fuel then drained into the engine causing a fire. A ladder was pushed up to the plane by ground crew and both pilots could step down unhurt. The F-16 virtually melted down before the fire was put out. One of the pilots was a USAF exchange pilot temporarily flying with the 332 sqn
|
|
| 12 Jun 1985 |
[w/o] |
303 |
78-0303
|
RNOAF 332 skv |
F-16B
Block 5
|
|
Details
|
|
|
|
|
Crashed north of Banak, Norway during a low level flight over the ocean. The crew consisted of a pilot and a higher ranking officer. The pilot experienced a sudden pitch down and due to the low level he did not have time to recover so he chose to eject. It was later speculated that the high ranking officer experienced a hart attack where he grabbed the side stick controler and pushed it forward. At the same time his body went rigid lifting up of the seat. When the pilot in charge decided to eject the seat hit the high ranking officer with extream force causing serious internal injuries which later lead to his death. The pilot in charge survived without serious injuries
|
|
| 03 May 1995 |
[w/o] |
307 |
78-0307
|
RNOAF 332 skv |
F-16B
Block 10
|
|
Details
|
|
|
|
|
Suffered a bird strike in the air intake after take-off from Rygge air base at 11:38 hours. It was flying with an F-16A going on a bombing mission on a range in southern Norway. Both crew, 1st Lieutenants Bråthen and Vereide, ejected safely after twice attempting to relight the engine. The aircraft came down about three minutes later in and open field 300 yards from a main highway
|
|
| 10 Jan 1989 |
[w/o] |
676 |
80-3676
|
RNOAF 331 skv |
F-16A
Block 15
|
|
Details
|
|
|
|
|
Crashed near Andøya, Norway killing the pilot.
|
|
| 14 Mar 1988 |
[w/o] |
679 |
80-3679
|
RNOAF 331 skv |
F-16A
Block 15
|
|
Details
|
|
|
|
|
The aircraft crashed near Hindøya Island, during a NATO exercise. The pilot was unfortunately killed in the crash.
|
|
Abbreviations and symbols:
| [act] |
Active |
[msh] |
Involved in Mishap |
[sto] |
Stored (e.g. at AMARC) |
| [cld] |
Cancelled order |
[o/o] |
On Order |
T/V |
LM Aero Type/Version (Construction) number |
| [emb] |
Embargoed |
[pre] |
Preserved (museum, gateguard) |
[w/o] |
Write-off |
| [i/a] |
Instructional Airframe |
[scr] |
Scrapped |
 |
Photo Available |
Errors and Omissions
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.
|
|
|