Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

February 23, 2010 · Diamond Aircraft Ind DA 20-C1 · N894CT

Delta, UT

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 23, 2010
Injury Outcomes
No injuries (1 uninjured)
Location
Delta, UT
Aircraft
Diamond Aircraft Ind DA 20-C1
Tail Number
N894CT
Operator
Utah Valley University
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR10CA146

The student pilot was on his first solo cross-country flight, which had as its planned destination an airport that he had never been to prior to that flight. Upon arriving at the unfamiliar airport, he overflew the area in order to get a sight picture of the situation. He then flew a non-standard pattern to the final approach of the runway he chose to land on. Although his approach had not become stabilized by short final, he decided to continue the landing. When the airplane’s main gear contacted the runway, it bounced back into the air, and the pilot decided to execute a go-around. During the go-around, the pilot, who said the engine sounded like it went to full rpm, did not let the airplane stabilize and accelerate before retracting the flaps, and he therefore found that the airplane would not maintain the climb that he tried to establish. As he attempted to continue the go-around, the airplane slowed and its left wing dropped, and the pilot was unable to maintain directional control. The airplane then descended into the soft terrain off the left side of the runway, and nosed over onto its back. The airplane sustained substantial damage to its wings, fuselage, and empennage. A Federal Aviation Administration inspector monitored an engine inspection and test run, which did not reveal any anomalies or issues with the engine, which was able to be run to full power.

NTSB Probable Cause

The student pilot's incorrect use of the flaps and failure to attain and maintain an adequate airspeed during the attempted go-around procedure, which led to a stall/mush condition. Contributing to the accident was the student pilot's lack of familiarity with the destination airport, and his delayed decision to execute the go-around.

Full Narrative

The student pilot was on his first solo cross-county fight, which had as its planned destination an airport that he had never been to prior to that flight. Upon arriving at the unfamiliar airport, he overflew the area in order to get a sight picture of the situation. He then flew a non-standard pattern to the final approach of the runway he chose to land on. Although his approach had not become stabilized by short final, he decided to continue the landing. When the airplane’s main gear contacted the runway, it bounced back into the air, and the pilot decided to execute a go-around. During the go-around, the pilot, who said the engine sounded like it went to full rpm, did not let the airplane stabilize and accelerate before repositioning the flaps, and he therefore found that the airplane would not maintain the climb that he tried to establish. As he attempted to continue the go-around, the airplane slowed and its left wing dropped, and the pilot was unable to maintain directional control. The airplane then descended into the soft terrain off the left side of the runway, and nosed over onto its back. The airplane sustained substantial damage to its wings, fuselage, and empennage. A Federal Aviation Administration inspector monitored an engine inspection and test run, which did not reveal any anomalies or issues with the engine, which was able to be run to full power.

Flight

Event TypeAccident
Event Time15:45 MST
Nearest AirportDelta Municipal (0nm)
Runway30
Runway Length5935 ft
Runway Width85 ft
Flight Plan FiledVFR
Flight Plan ActivatedUnknown
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftDiamond Aircraft Ind DA 20-C1
Tail NumberN894CT
Aircraft CategoryAir
DamageSubstantial
OperatorUtah Valley University
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsCont Motor · IO-240 SERIES · Reciprocating · 125
Seats2

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 23 · Second Class · None

Conditions

ConditionsVMC
LightDaylight
Wind135° @ 6 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point39 C / 0 C
Altimeter0
Weather SourcePILO

Appendix: Source Data