WPR09CA322 · Diamond Aircraft IND Inc DA 20-C1
Airgyro Aviation Diamond Aircraft IND Inc DA 20-C1 · Accident: hard landing
From U77 · Spanish Fork, UT to U77 · Spanish Fork, UT
Event
- NTSB case
- WPR09CA322
- 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 Aircraft IND Inc DA 20-C1
- Aircraft type
- Diamond DA-20
- 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
- N765DC
- Operator
- Airgyro Aviation
- Onboard fatalities
- Unknown
- Route
- From U77 · Spanish Fork, UTTo U77 · Spanish Fork, UT
- 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 · 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
- 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 › 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
The student pilot reported that his final approach to the runway was high and that he "slipped" the airplane to lose altitude. As the airplane crossed over the runway, he pitched the airplane forward to prepare for landing. The student pilot stated that he "felt the [air]plane losing forward momentum and added throttle to compensate." The airplane landed hard, bounced back into the air, and began to drift to the left. As the student pilot attempted to abort the landing by applying full throttle and reducing flaps, the airplane landed hard and exited the runway to the left. Subsequently, the airplane impacted a ditch, which resulted in structural damage to the rudder, left aileron, fuselage, and engine firewall. The student pilot reported no mechanical anomalies with the engine or airframe prior to the accident.
Probable cause
The student pilot’s improper landing flare.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09CA322
- Event ID
- 20090630X80241
- Case number
- WPR09CA322
- 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: 5136e330fed433acd6c7bae2368d7b5087837161ae80b22381502a6506b2f17f; retrieved 2026-09-15T11:38:54.010Z.