Fatal accident · Yugoslavia

Britannia Airways Bristol Britannia crash near Ljubljana

Britannia Airways Flight 105, a Bristol Britannia 102, crashed near Ljubljana, Yugoslavia, on September 1, 1966 during a landing attempt. There were 117 people aboard and 98 died. The cause was pilot error, tied to an incorrect altimeter setting and missed cross-checks.

This is one of 2 Britannia Airways fatal accidents on record. See also all plane crashes in 1966.

Flight 105 struck forest on approach to Ljubljana

Flight 105 was inbound from Luton to Ljubljana when it crashed during the landing attempt. The Bristol Britannia 102 hit forest near Ljubljana Airport. Ninety-eight of the 117 people aboard were killed.

The accident happened in the final phase of the flight, when the crew should have been descending and aligning the aircraft for landing. There were no fatalities on the ground.

The captain kept the wrong pressure setting

The Bristol Britannia used pressure settings on its altimeters to show height correctly for the approach. In this case, the captain did not change his altimeter from QNH to QFE. That left his instrument indicating height on the wrong reference for the landing procedure.

The crew also failed to cross-check the altimeters. With that error uncorrected, the aircraft descended into terrain before reaching the runway. The cause was pilot error. For broader context on this category, see other accidents with the same cause.

A procedural breakdown in a classic turboprop airliner

Britannia Airways was operating a Bristol Britannia, a long-range turboprop airliner widely used in that era on passenger routes. Aircraft of that generation relied heavily on disciplined instrument procedures, especially on approach, because a small setup error could put the airplane lower than the crew intended.

Flight 105 is a clear case of that kind of breakdown. The problem was not a mystery of unknown systems or missing wreckage evidence. It was the crew's failure to follow the proper landing procedure and to verify the altimeter indications against each other. That is the sort of chain investigators look for when they determine the cause of a crash.

Questions people ask about this accident

What caused the Britannia Airways crash near Ljubljana in 1966?

The crash was caused by pilot error. The captain kept his altimeter on QNH instead of changing to QFE, and the crew failed to cross-check the altimeters during the approach.

Where did Britannia Airways Flight 105 crash?

Flight 105 crashed in forest near Ljubljana Airport, near Ljubljana in Slovenia, then part of Yugoslavia.

How many people died in the Britannia Airways Ljubljana crash?

Ninety-eight people died. There were 117 people aboard the aircraft.

What aircraft was involved in Flight 105?

The aircraft was a Bristol Britannia 102, registered G-ANBB, operated by Britannia Airways.

  1. Globe Air Britannia crashed on approach near Nicosia

    Near Nicosia, Cyprus · Bristol Britannia 175 · Globe Air · HB-ITB

    126 killed
  2. British Eagle Flight 802 hit Mt. Glungezer near Innsbruck

    Near Innsbruck, Austria · Bristol Britannia 312 · British Eagle International Airlines · G-AOVO

    83 killed
  3. Inex Adria and British Airways midair collision near Gaj

    Near Gaj, Hrvatska, Yugoslavia · McDonnell Douglas DC-9-31 / Trident 3B · Inex Adria Aviopromet / British Airways · YU-AJR/G-AWZT

    176 killed
  4. Aviogenex Flight 130 crashed landing at Rijeka

    Near Rijeka, Yugoslavia · Tupolev TU-134A · Aviogenex (Yugoslavia) · YU-AHZ

    78 killed
  5. Learjet 60 crash in Greenacres, Florida kills all nine aboard

    Greenacres, Florida · Bombardier Learjet 60 · Private (LR60271 LLC) · N722BD

    9 killed

Correct this page or send a photo

Spotted a wrong date, registration or number? Have a photo of the aircraft or the site that you took yourself? Send it here. Nothing is published until an editor has checked it.

By sending a photo you confirm you took it and allow Air Crash DB to publish it with your credit. We keep your message and, if you give them, your name and email, until the correction is handled. See the privacy policy.