ERA11CA420 · de Havilland TIGER MOTH DH 82A
Owls Head Transportation Museum de Havilland TIGER MOTH DH 82A · Accident: landing area undershoot
From Knox County Regional Airport (RKD) to Knox County Regional Airport (RKD)
Event
- NTSB case
- ERA11CA420
- 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
- 0 · 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 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
- N8872
- Operator
- Owls Head Transportation Museum
- Onboard fatalities
- Unknown
- Route
- From Knox County Regional Airport (RKD), Rockland, METo Knox County Regional Airport (RKD), Rockland, ME
- Aircraft age
- Not recorded
- 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
- Landing
- 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
- Landing area undershoot
- 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 oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was landing at the conclusion of a local flight. As the airplane passed over the runway threshold the airplane's main landing gear contacted high grass. The airplane nosed over and impacted the runway inverted, resulting in substantial damage to the vertical stabilizer and both left and right top wings. The pilot reported that there were no mechanical malfunctions or anomalies with the airplane prior to the accident, and that the accident could have been prevented by conducting a higher approach to landing.
Probable cause
The pilot's failure to maintain a proper approach path during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA420
- Event ID
- 20110725X54256
- Case number
- ERA11CA420
- 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. 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: 933797d0c975992000e0f3068b17fe480aa0b3c63c7c65eff7c4255736b07793; retrieved 2026-09-15T16:30:19.684Z.