CEN22LA106 · de Havilland TIGER MOTH DH 82A
de Havilland TIGER MOTH DH 82A · Accident: loss of engine power (partial) while maneuvering
From Lampasas Airport (LZZ) to an unrecorded destination
Event
- NTSB case
- CEN22LA106
- 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
- Event fatalities
- Unknown
- 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 TIGER MOTH DH 82A
- Aircraft type
- de Havilland TIGER MOTH DH 82A
- 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
- N5300
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lampasas Airport (LZZ), Lampasas, TXTo not recorded
- Aircraft age
- About 82 years (built 1940)
- 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
- Maneuvering
- 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
- Substantial
Cause areas
- Aircraft › Aircraft power plant
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane’s engine lost partial power and the pilot was unable to maintain altitude. He executed a forced landing to a terraced farm field. During the landing, the airplane struck one of the terraced areas and nosed over. The airplane sustained substantial damage to the rudder, engine mounts, and lower right wing. Postaccident examination of the engine revealed that the ball end of the No. 2 cylinder exhaust valve rocker was not seated in the pushrod. Additionally, the head of one of the bolts securing the rocker arm bracket had fractured and the bolt head was found in the rocker cover. Based on the available evidence it is likely that the fractured bolt head allowed enough movement of the No. 2 cylinder rocker arm bracket for the pushrod to become separated from the ball end of the rocker arm. This prevented the exhaust valve for the No.2 cylinder from opening and thereby reducing the power output of the engine.
Probable cause
The failure of a bolt in the engine valve system which resulted in malfunction of the engine exhaust valve system and a partial loss of engine power. The rough terrain encountered during the forced landing contributed to the outcome.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22LA106
- Event ID
- 20220124104548
- Case number
- CEN22LA106
- 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, coordinates, 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: dddc4e53f1fe8842ea70f8015b50584d3b19c7f1c7a977a04796afe3dfea09f9; retrieved 2026-09-16T14:54:29.018Z.