ERA20CA279 · Dakota S18-160
Dakota S18-160 · Accident: nose over/nose down during landing
From Old Orchard Airpark (2NK9) to Old Orchard Airpark (2NK9)
Event
- NTSB case
- ERA20CA279
- 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
Dakota S18-160
- Aircraft type
- Dakota S18
- 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
- N811RD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Old Orchard Airpark (2NK9), Modena, NYTo Old Orchard Airpark (2NK9), Modena, NY
- Aircraft age
- About 1 year (built 2019)
- 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 · landing roll
- 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
- Nose over/nose down
- 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 systems
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, he was landing after a local flight with a passenger seated in the rear seat of the tail-wheel equipped airplane. During touchdown the airplane started to nose over, and the pilot realized that the passenger had his feet on the brakes. He yelled at the passenger to get his feet off the brakes, but it was too late to prevent the airplane from nosing over. The airplane flipped over inverted and came to a complete stop. Examination of the airplane by a Federal Aviation Administration inspector revealed that the vertical stabilizer was buckled. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The passenger's inadvertent application of the rear brakes during landing, which resulted in a nose-over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20CA279
- Event ID
- 20200807X64527
- Case number
- ERA20CA279
- 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: 73b6dae064a4e163d517cebc8a590d9bfb1cc8dcc1806d57b46e1e57d78945bd; retrieved 2026-09-16T12:24:58.644Z.