Sabena Flight 503
Douglas DC-6B · Controlled flight into terrain due to harsh weather conditions and faulty navigation
From Melsbroek Air Base (EBMB) to Leopoldstad, Congo
Event
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- Event fatalities
- 29 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- Unknown
- Survivors
- 0
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
Douglas DC-6B
- Aircraft type
- Douglas DC-6
- Category
- Airplane · from aircraft type
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- OO-SDB
- Operator
- Sabena
- Onboard fatalities
- 29
- Route
- From Melsbroek Air Base (EBMB)To Leopoldstad, Congo
Cause areas
- Personnel issues › Psychological
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
- Personnel issues › Experience/knowledge
From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.
Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.
From the Wikipedia article
The crash of Sabena Flight 503 was an accident involving a Douglas DC-6 of the Belgian airline company Sabena which crashed into Monte Terminillo near Rieti, Italy, 100 km northeast of Rome on 13 February 1955, killing all 29 people on board.
Crash
Sabena Flight 503 was a Douglas DC-6 which departed from Brussels, Belgium at 17:17 GMT en route to Leopoldstad, Congo with stops at Rome-Ciampino, Italy and Kano, Nigeria under the command of pilot Stephan Stolz and co-pilot Patrick McNamara.
The aircraft made contact with Ciampino International Airport according to plan at 19:29 GMT, at which time the aircraft had passed over Florence, Italy at 17,500 ft. The weather conditions however kept getting worse with heavy rain and snow fall. At 19:48 Ciampino control asked the aircraft whether it had passed over Viterbo. Instead of answering this question directly, the crew inquired whether the Viterbo NDB (Non-directional beacon) was on full power. The controller replied that another aircraft had overflown Viterbo shortly before and had found it to be operating properly. At 19:51 GMT the aircraft stated that it had passed over Viterbo one minute previously and requested clearance to descend to 5500 ft which was granted. One minute later it inquired whether the Ciampino ILS was operating and received an affirmative reply. At 19:55 co-pilot McNamara contacted Ciampino and stated that the crew would prepare for the landing procedure but that the visibility had worsened; the connection was very weak due to the severe storm and heavy snow and rain fall. At 19:56 Flight 503 called Rome control for the last time when suddenly the communication was cut off.
The aircraft had crashed somewhere in the mountains of Rieti, Italy 100 km northeast of Rome and was now missing. Sabena itself got notified about the missing aircraft that same night at 23:15 but would not make an official statement until the morning of the following day.
Investigation and cause
Investigation
After determining the angle of impact with the mountain, it was discovered that Flight 503 was 150° off course. After investigators calculated the flight path, the final moments of Flight 503 could be reconstructed from the moment it passed Viterbo. A number of watches found stopped at the crash site together with the radio messages and the speed of the aircraft, allowed investigators to construct a clear image of Flight 503's flight path.
It shows that the pilots kept following their flight schedules and kept flying in a straight line. However the crew never noticed that the bad weather and the wind that was blowing from the west had blown the aircraft off course and towards the mountain range. On certain points in the Italian mountains the wind can be so strong that the aircraft was blown on a different course and that the radio-navigation tools on the medium wave couldn't offer the usual assistance which also explained the weak radio signals. In the end, the severe storm together with faulty navigation and a crew which were unfamiliar with the terrain proved to be fatal and send Flight 503 on a direct collision course with the mountain range without anyone realising it.
Text from the Wikipedia article “Sabena Flight 503” (revision 1362614838, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
Sources
Wikipedia article: Sabena Flight 503
- Article
- Sabena Flight 503
- Revision
- 1362614838 · 2026-07-05 · retrieved 2026-09-18
- Wikidata
- Q3797641
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
Where each value comes from
- Record
- Wikipedia article "Sabena Flight 503" (page 49294414, revision 1362614838)
- Date
- Wikipedia infobox: date
- Place and country
- Wikipedia infobox: site
- Map position
- Wikipedia article coordinates
- Aircraft, operator and route
- Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- flight number in the article title
- Fatalities
- Wikipedia infobox: aircraft fatalities
- Ground fatalities
- not stated in the Wikipedia infobox
- Summary
- Wikipedia infobox: summary
Source notes (1)
- Wikipedia · Facts from the Wikipedia article's infobox and coordinates, not checked against an investigation report. Independent review pending.