ATL04LA022 · Diamond Aircraft DA 20-C1
Diamond Aircraft DA 20-C1 · Accident: overrun during landing
From Huntsville International Airport (HSV) to Moises R. Espinosa Airport (MBT)
Event
- NTSB case
- ATL04LA022
- 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 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
- N575MT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Huntsville International Airport (HSV), Huntsville, ALTo Moises R. Espinosa Airport (MBT)
- 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 · aborted
- 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
- Overrun
- 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
- Pilot in command › Directional control, not maintained
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 set up for a straight-in approach to runway 36. During the landing, the airplane initially contacted the runway with its nose wheel, then bounced up and continued down the runway. The pilot used rudder control input to maintain centerline. He stated he realized he was running out of runway and intended to initiate a go-around, but the airplane settled back to the runway, the left main wheel touched down, and the airplane skidded left. The pilot's efforts to regain control of the airplane were unsuccessful, and it skidded left off the runway, struck an airport sign for taxiway A, and came to rest on the north end of the runway. Examination of the airplane revealed the right main landing gear was separated, and the propeller was damaged. Cracks were observed on the composite wing structure and on the composite fuselage near the gear attachment block. The pilot reported no mechanical malfunction with the airplane. Examination of the runway revealed a gouge in the asphalt on the north end of runway 36, near the numbers for the approach end of runway 18.
Probable cause
The pilot's failure to attain adequate airspeed, which resulted in a stall mush and collision with a taxiway sign. A factor was the pilot's delay in aborting the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL04LA022
- Event ID
- 20031031X01842
- Case number
- ATL04LA022
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2003-10-22.
- API snapshot SHA-256: bdbf7ee16d557cd72a80f507e038c09919da7e2004107c64831b3b9611ae56fe; retrieved 2026-09-22T08:18:07.355Z.