WPR20CA305 · Diamond DA20 C1
Platinum Aviation Diamond DA20 C1 · Accident: hard landing
From Delta Municipal Airport (DTA) to Fillmore Municipal Airport (FOM)
Event
- NTSB case
- WPR20CA305
- 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
Diamond DA20 C1
- Aircraft type
- Diamond DA20
- 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
- N802CT
- Operator
- Platinum Aviation
- Onboard fatalities
- Unknown
- Route
- From Delta Municipal Airport (DTA), Delta, UTTo Fillmore Municipal Airport (FOM), Fillmore, UT
- Aircraft age
- About 20 years (built 2000)
- 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
- Hard landing
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot reported that, after completing a normal approach, the airplane touched down nose gear first and the airplane bounced. The airplane continued to bounce down the runway and the pilot elected to abort the landing. He applied full engine power and the airplane again became airborne and veered off the left side of the runway. The pilot attempted to maneuver the airplane to the right, however the airplane descended onto the uneven dirt surface on the right side of the runway. The right main landing gear separated from the airplane and the lower fuselage was substantially damaged. The student pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The student pilot's improper landing flare and delayed remedial action to abort the landing, which resulted in a loss of aircraft control, runway excursion and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20CA305
- Event ID
- 20200911X75746
- Case number
- WPR20CA305
- 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: f0546171cae7085ee880e20a32a393d88d6a617f6a6f41314db1b08d212e2ffc; retrieved 2026-09-16T13:01:36.526Z.