FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC03FA080 · Dassault Aviation DA-20

8 Apr 2003 · Swanton, OH, United States

Grand Aire Express Dassault Aviation DA-20 · Accident: in flight encounter with weather on approach

From Cherry Capital Airport (TVC) to Eugene F. Kranz Toledo Express Airport (TOL)

Report a problem

Event

NTSB case
NYC03FA080
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
3 · 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
Instrument Meteorological Cond

Dassault Aviation DA-20

Aircraft type
Dassault 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
N183GA
Onboard fatalities
Unknown
Route
From Cherry Capital Airport (TVC), Traverse City, MITo Eugene F. Kranz Toledo Express Airport (TOL), Swanton, OH
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
Approach
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
In flight encounter with weather
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/mush; Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command(cfi) › Airspeed, not maintained
  • Pilot in command(cfi) › Supervision, inadequate

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

NTSB narrative

The flight crew of the Fan Jet Falcon (DA-20) were practicing ILS approaches in instrument meteorological conditions with low clouds and rime ice. A first officer (FO) in training occupied the right seat, while the pilot-in-command (PIC), who was also the company chief pilot/check airman/designated flight instructor, occupied the left seat and was handling the radios. On the second approach, the airplane struck trees and burned, 1.57 nm from approach end of the runway. The landing gear was found extended, and the trailing edge and droop leading edge flaps were retracted. The wing and engine cowl anti-ice valves were found closed, consistent with it being off in the cockpit. Radar data revealed that on approach, the airspeed decreased from 188 knots to 141 knots at the outer marker, and continued to decrease down to 106 knots, when the airplane entered an abrupt descent and disappeared from radar. Simulator flights matched the radar profile with a flight idle approach, a power reduction inside the outer marker, and 1/4 inch of ice on the wings. In the simulator, the airplane stalled about 2 miles from the end of the runway with an airspeed of 103 kts. At flight idle, the engine power in the last 2 minutes of approach was below the recommended power setting for wing or engine anti-ice to be effective. Vref and stall speeds were computed to be 129 kts and 96 kts, with wing flaps and droop leading edges retracted. The PIC had about 1,100 hours in the make and model. The PIC did not have any documented previous flight instruction experience in make and model or any other multi-engine airplanes. The PIC had given 4 pilot proficiency checks in the DA-20 since receiving his check airman designation. The company Director of Operations reported that the accident FO was the first student the PIC had taken through the initial second-in-command course. The PIC and FO had received all of their turbojet experience with the operator.

Probable cause

The flight instructor's inadequate supervision of the flight, including his failure to maintain an approach airspeed consistent with the airplane's configuration, which resulted in an aerodynamic stall due to slow airspeed, and subsequent uncontrolled descent into trees. Factors were the icing conditions, the flight instructors failure to turn on the wing and engine anti-ice, and his lack of experience as an instructor pilot in the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC03FA080
Event ID
20030421X00535
Case number
NYC03FA080
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: 8d145bf2974ad5d6dbd0a49deb58475232384b4677011f6f08f0830a0b0efa60; retrieved 2026-09-20T19:19:43.549Z.