1956 Eindhoven Lockheed T-33 crash
Royal Netherlands Air Force Lockheed T-33 · Pilot error; reckless flying
From Volkel Air Base (UDE) to an unrecorded destination
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
- 2 · all aircraft and ground
- Ground fatalities
- 1
- Occupants
- 1
- Survivors
- Unknown
- 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
- 23 · all on the ground
- 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
- Military
Lockheed T-33
- Aircraft type
- Lockheed T-33
- 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
- Unknown
- Operator
- Royal Netherlands Air Force
- Onboard fatalities
- 1
- Route
- From Volkel Air Base (UDE)To not recorded
Cause areas
- Personnel issues › Action/decision
- Personnel issues › Experience/knowledge
From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.
Approximate · Estimated position: Eindhoven, the place the Wikipedia article names. Not the accident site.
From the Wikipedia article
On 22 September 1956, a Lockheed T-33 of the Royal Netherlands Air Force crashed at c. 01:45pm in a housing block in Eindhoven, the Netherlands. The pilot and one person on the ground were killed. Four houses burned down, twelve houses partly burned down and many more were severely damaged.
The pilot had recently married and lived with his wife at the place where the crash occurred. It was the first solo flight of the pilot. He deliberately ignored his instructions and safety rules and flew above his own house. The crash was likely due to a misjudgment resulting from his inexperience.
Flight and crash
In the afternoon of 22 September 1956, a Lockheed T-33 training plane of the Royal Netherlands Air Force departed from Volkel Air Base. According to the Royal Netherlands Air Force, the pilot was instructed to make a reconnaissance flight, followed by a few landings at Volkel Air Base. At around 01:45pm, the aircraft approached Eindhoven from south-east direction. According to eyewitnesses, the jet circled a few times above Strijp before the crash. The jet came in low at only a few hundred metres according to eyewitnesses at a high speed. It looked like the pilot wanted to land because he was flying so low. The wing of the jet hit the top of the house at Zeelsterstraat 166 and crashed into houses a few hundred meters further away. The fuel tanks exploded. The explosion was heard beyond Eindhoven. Due to the rain of burning kerosene, many houses were set on fire. Four houses were totally burned down, twelve houses partly burned down and many more houses were severely damaged.
Investigation and cause
Investigation
The pilot recently completed a refresher course, and so he knew that it was not allowed to fly at a low altitude and to fly above built-up areas. It was his first solo flight. The pilot was just married and lived with his wife at the Bergen op Zoomstraat 153 with the family of his wife. The pilot had told his wife that he would fly low above their house between 1:30pm and 2:30pm. His wife had told other people this before the crash.
During the flight, the pilot didn't have contact with the ground, though it is a normal procedure that a pilot didn't have radio contact during these flights. Normally, there was only radio contact before landing or when something was wrong. According to the Royal Netherlands Air Force, the pilot deliberately ignored the given instructions. The Dutch Air Force also stated that his commanders had been very clear regarding the correct execution of the given orders.
In an early report it was stated that the pilot attempted to climb before the crash, but failed in doing so. According to the investigation committee, there are multiple possible explanations for why the pilot was not able to avoid the house in time. The most plausible reason is that he didn't react in time, as he was unexperienced and it was his first solo flight. Other reasons included that he misjudged his height or that he became unwell. As he was flying in a westerly direction, it is also possible that he was blinded by the bright sun or he was inattentive by searching for his home and wife. A technical defect was also not ruled out at first.
Text from the Wikipedia article “1956 Eindhoven Lockheed T-33 crash” (revision 1359238741, 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: 1956 Eindhoven Lockheed T-33 crash
- Revision
- 1359238741 · 2026-06-14 · retrieved 2026-09-18
- Wikidata
- Q123560957
- 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 "1956 Eindhoven Lockheed T-33 crash" (page 74171936, revision 1359238741)
- Date
- Wikipedia infobox: date
- Place and country
- Wikipedia infobox: site
- Map position
- place the Wikipedia infobox site links (Wikidata 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
- operator named as an armed force or military unit in the infobox
- Fatalities
- Wikipedia infobox: total_fatalities
- Ground fatalities
- Wikipedia infobox: ground fatalities
- 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.