WPR10CA344 · Diamond Aircraft IND Inc DA 20-C1
American Flight Center Diamond Aircraft IND Inc DA 20-C1 · Accident: loss of control on ground during landing
From U77 · Spanish Fork, UT to Dutch John Airport (33U)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR10CA344
- 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
- N376DC
- Operator
- American Flight Center
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From U77 · Spanish Fork, UTTo Dutch John Airport (33U), Dutch Jones, 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
- Loss of control on ground
- 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
- Environmental issues › Conditions/weather/phenomena
- 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 pilot reported that while flying he began to experience turbulence and fast-developing clouds. As he approached his destination he observed heavy clouds over the airport and diverted to a nearby alternate airport. Upon approaching the alternate airport he observed moderate weather at his original destination and redirected to the original airport. The approach was uneventful; as the airplane touched down a strong crosswind gust struck the airplane and lifted the right wing. Subsequently the left wing struck the ground, resulting in substantial damage. The pilot reported no mechanical failures or malfunctions with the airframe or engine prior to the accident.
Probable cause
The pilot’s inadequate compensation for the crosswind conditions and failure to maintain directional control during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10CA344
- Event ID
- 20100712X51301
- Case number
- WPR10CA344
- 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: c5a4e905a6a218d43450e9a266be831b5e7eafd65996bf0b2e37d331cc3633ec; retrieved 2026-09-15T14:40:45.898Z.