FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18FA200 · De Havilland DH112 VENOM FB54

20 Jul 2018 · Sheboygan, WI, United States

World Heritage Air Museum De Havilland DH112 VENOM FB54 · Accident: loss of engine power (partial) during initial climb

From Sheboygan County Memorial Airport (SBM) to Sheboygan County Memorial Airport (SBM)

Report a problem

Event

NTSB case
WPR18FA200
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
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
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
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

De Havilland DH112 VENOM FB54

Aircraft type
de Havilland DH112
Category
Airplane
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
N747J
Onboard fatalities
Unknown
Route
From Sheboygan County Memorial Airport (SBM), Sheboygan, WITo Sheboygan County Memorial Airport (SBM), Sheboygan, WI
Aircraft age
About 61 years (built 1957)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Initial climb
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of engine power (partial)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft power plant
  • Environmental issues › Conditions/weather/phenomena

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot was conducting a formation training flight consisting of two airplanes; the accident airplane was in the No. 2 position. The airplane took off about 8 seconds behind the lead (No. 1 position) airplane. Witnesses described the airplane's takeoff as sluggish and indicated that the airplane's wings rocked back and forth shortly after lifting off. The witnesses' testimony was consistent with one witness' video recording, which showed the airplane climbing away from the runway and making a shallow left turn. As the airplane passed the witness' position, the engine sound decreased and rapidly increased. The airplane reached an altitude of about 200 ft above the ground before descending and impacting a farm structure. Another video captured the airplane descending in a slightly nose-up and wings-level attitude before impact. The flaps and landing gear both appeared retracted in that video.

No preimpact anomalies with the airframe and engine were found that would have precluded normal operation of the airplane. Signatures consistent with circumferential rub marks within the turbine were identified. Although the rate of rotation at the time of impact could not be determined, the retraction of the landing gear at a normal rate showed that the engine was likely producing some power at that time.

One of the witnesses to the accident was a pilot with experience in the accident make and model. He described the engine powering the airplane as "high airflow and thrust" and indicated that the engine could experience a compressor stall when operating at a high angle of attack and a high-power setting. He also stated that the airplane could get into a low energy state if an engine failure occurred and that the airplane would normally accelerate "very quickly" if it leveled off at 200 ft.

The witness accounts of the accident airplane's wings rocking back and forth were consistent with the airplane encountering the wake turbulence of the lead airplane. Wake turbulence can disrupt airflow to the engine of a trailing airplane. The final seconds of the witness' video showed the pilot controlling the airplane during the climb to 200 ft, after which the airplane began descending. Thus, the wake turbulence from the lead airplane likely disrupted airflow to the engine and caused a compressor stall and a partial loss of engine power, which resulted in the airplane's inability to continue to climb.

Toxicology testing identified sedating medications in the pilot's specimens, but the levels of the medications at the time of the crash were well below the levels that would have caused significant effects. Therefore, it is unlikely that impairing effects of these medications contributed to this accident.

Probable cause

The airplane's encounter with wake turbulence from the lead airplane in the formation flight, which resulted in a compressor stall and the airplane's subsequent inability to climb.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18FA200
Event ID
20180720X93110
Case number
WPR18FA200
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: d1b68d1aef905882db0e4237bfa3263432f0b85737deaea7c2d667b1236b08f3; retrieved 2026-09-15T06:44:39.667Z.