WPR20FA057 · Thunder Mustang TM-1
Thunder Mustang TM-1 · Accident: loss of engine power (total) en route
From Van Nuys Airport (VNY) to Van Nuys Airport (VNY)
Event
- NTSB case
- WPR20FA057
- 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
Thunder Mustang TM-1
- Aircraft type
- Thunder Mustang TM-1
- 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
- N151WR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Van Nuys Airport (VNY), Van Nuys, CATo Van Nuys Airport (VNY), Van Nuys, CA
- Aircraft age
- About 19 years (built 2001)
- 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
- En route
- 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 (total)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 power plant
- Environmental issues › Task environment
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed for flight in an amateur-built experimental airplane. A few minutes after takeoff, the pilot made a distress call to the airport tower controller stating a loss of engine power and a cockpit visibility issue. A witness observed the airplane maneuvering at a low altitude with smoke trailing from the airplane. Subsequently, the airplane struck a tree and impacted terrain in a grassy field located in the median of an interstate’s off-ramp, destroying the airplane.
Postaccident examination of the engine revealed damage that was consistent with detonation. One cylinder had material deformation that had burnt through the crankcase. Other cylinders had varying degrees of material deformation on their piston faces and cylinder heads, and the piston faces, and cylinder heads were absent of any carbon buildup. During the forced landing, the hole in the crankcase would have leaked coolant and oil, creating smoke and limiting the visibility from the cockpit, which likely would have prevented the pilot from seeing and avoiding the tree. The specific reason for the detonation could not be determined.
Probable cause
Engine detonation that resulted in material deformation of the crankcase and led to engine failure and restricted cockpit visibility.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20FA057
- Event ID
- 20200104X54406
- Case number
- WPR20FA057
- 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, cause areas. 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: 866f41090838b9717cdf93e54af842e1cf87f151be306e405ba3edcfcec9395b; retrieved 2026-09-15T07:10:08.246Z.