FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC02FA131 · Diamond Aircraft Industries DA 20C-1

6 Jul 2002 · Leesburg, VA, United States

AV-ED Flight Schools Diamond Aircraft Industries DA 20C-1 · Accident: loss of engine power while maneuvering

From Leesburg Executive Airport (JYO) to JYO

Report a problem

Event

NTSB case
NYC02FA131
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
1 · 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 Industries DA 20C-1

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
N960CT
Onboard fatalities
Unknown
Route
From Leesburg Executive Airport (JYO), Leesburg, VATo JYO
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
First occurrenceThe 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 engine power
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
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

  • Reason for occurrence undetermined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The passenger reported that the pilot departed the airport, completed a touch-and go, and flew to a practice area. The passenger then flew two clearing turns at 2,500 feet msl, and the pilot subsequently retook control of the airplane and climbed to 3,000 feet msl. After the pilot leveled the airplane about 2,900 feet msl, the engine lost all power. The pilot completed emergency checklist items, but was unable to restart the engine. The pilot then attempted a forced landing to a field. The airplane impacted in residential area; left wing low, nose down, and slid about 100 feet. Aside from a sooty number two cylinder, examination of the wreckage did not reveal any discrepancies. After the initial examination, the engine was then disassembled, and no discrepancies were observed. The fuel control unit, injector lines, nozzles, manifold, magnetos, number two cylinder and piston, and connecting rod, were all tested at the engine manufacturer's facility. The fuel components and magnetos flowed and tested within specifications respectively. The cause of the black sooty deposit within the number two cylinder could not be determined; however, the deposit appeared to be over normal combustion deposit.

Probable cause

A loss of engine power for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC02FA131
Event ID
20020711X01091
Case number
NYC02FA131
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 06e781e752473cccb1eed14a4324b1a99a2326471d60d95e8b5701935885ce11; retrieved 2026-09-20T19:57:50.645Z.