ERA20LA055 · Piper PA18 A
Piper PA18 A · Accident: abnormal runway contact during landing
From New Market Airport (8W2) to New Market Airport (8W2)
Event
- NTSB case
- ERA20LA055
- 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
Piper PA18 A
- Aircraft type
- Piper PA18
- 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
- N1984A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From New Market Airport (8W2), Newmarket, VATo New Market Airport (8W2), Newmarket, VA
- Aircraft age
- About 67 years (built 1952)
- 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 · flare/touchdown
- 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
- Abnormal runway contact
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot of the tailwheel-equipped airplane, the airplane immediately rolled right and pitched forward at touchdown. The pilot's corrective control inputs had "no effect"; the airplane continued 100 ft past its touchdown point and came to rest facing about 40° off centerline with the tailwheel on the runway centerline. The right main landing gear leg and shock/dampener fractured, and the right wing was substantially damaged. Metallurgical examination of the right main landing gear leg and gear shock/dampener revealed no pre-impact anomalies, and the fracture surfaces of each displayed features consistent with overload failure. Thus, it is likely that the failure of the landing gear was a result of a hard landing.
Probable cause
The pilot's improper touchdown, which resulted in a hard landing and an overload failure of the right main landing gear leg and its associated shock/dampener.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20LA055
- Event ID
- 20191216X53550
- Case number
- ERA20LA055
- 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: 49abe90eb4020a23deb22b60c7d21041547b6e81de3e572ef468bc099fd5eed1; retrieved 2026-09-16T10:46:04.659Z.