FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11FA050 · Diamond Aircraft IND Inc DA20-C1

17 Nov 2010 · Payson, UT, United States

Utah Valley University Diamond Aircraft IND Inc DA20-C1 · Accident: loss of control in flight while maneuvering

From Provo Municipal Airport (KPVU) to Provo Municipal Airport (KPVU)

Report a problem

Event

NTSB case
WPR11FA050
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
2 · 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 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
N978CT
Onboard fatalities
Unknown
Route
From Provo Municipal Airport (KPVU), Provo Municipal, UTTo Provo Municipal Airport (KPVU), Provo Municipal, 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
Maneuvering
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 in flight
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 from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

During the dual instructional flight, the airplane entered a spin and made numerous descending rotations before impacting at a 44-degree nose down angle onto a residential driveway. Sounds consistent with engine operation during the descent were reported by witnesses. The aircraft wreckage was located directly under a designated practice area. The floor of the practice area was 2,500 feet above ground level (agl) and the upper altitude limit was 5,500 feet agl. According to the flight school director of operations, typical work done in the high-altitude working areas included stalls, slow flight, and steep turns. Examination of the airplane wreckage revealed that the flaps were in-between the takeoff and landing position; flap deployment is consistent with slow flight or stall practice.

The intention of the instructional flight was to prepare the student for his private pilot practical examination. According to records maintained by the flight school, a majority of the student pilot's flights had been with the accident instructor; however, the certified flight instructor (CFI) provided extremely little documentation on the actual performance of the student during the flight portion of his training. A similar stall and spin event occurred 2 weeks prior to the accident where the same CFI and a different student lost control of the airplane during a slow flight practice; however, in that instance, the CFI was able to recover the airplane quickly. The CFI's most recent spin training was conducted 7 years prior to the accident, although the flight school required instructors to complete a flight check every 12 months for each course of training they were approved to teach.

The flight school that operated the training flight did not have a functional mechanism to track safety incidents or a well advertised way for the students or staff to anonymously report aviation safety concerns. The director of safety did not convene regular safety meetings. Flight school management did not require CFIs to create written commentary regarding each student’s performance. There was a perception by three of the four chief flight instructors that CFI proficiency flights were not encouraged, and the CFIs were discouraged from using company flight time to maintain proficiency.

Probable cause

The pilots' failure to maintain adequate airspeed during a slow flight maneuver that resulted in a stall and spin, and the flight instructor’s delayed or improper remedial actions to recover from the spin. Contributing to the accident was the flight school’s inadequate safety program.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11FA050
Event ID
20101117X70315
Case number
WPR11FA050
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: 31606f73f68b6c4f2a0e34d0752324482ca672fb34e1a05aba80652ebdaa094d; retrieved 2026-09-13T21:08:19.283Z.