CEN13LA380 · Diamond Aicraft Industries Inc DA 20-C1
Flight Source Aviation Diamond Aicraft Industries Inc DA 20-C1 · Accident: abnormal runway contact during landing
From Georgetown Executive Airport at Johnny Gantt Field (GTU) to Odessa Schlemeyer Field (ODO)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN13LA380
- 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 Aicraft Industries Inc DA 20-C1
- Aircraft type
- Diamond Aicraft 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
- N322FS
- Operator
- Flight Source Aviation
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Georgetown Executive Airport at Johnny Gantt Field (GTU), Gerogetown, TXTo Odessa Schlemeyer Field (ODO), Odessa, TX
- 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 · flare/touchdown
- 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
- Abnormal runway contact
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the 4-mile final leg for landing in night visual meteorological conditions, the pilot set the flaps at 15 degrees for the approach and landing. According to the manufacturer's flight information manual, the flap position for landing is 45 degrees. The pilot stated that she kept the airplane speed "up" so that the airplane would not lose too much altitude and that, although the approach was a "little low," it was still within limits. The airplane touched down on the runway and bounced three times before the pilot increased engine power to perform a go-around. As the engine power increased, the airplane nosed down and contacted the runway, damaging the nosewheel and firewall. The pilot's use of partial flaps at a low altitude with a high approach speed resulted in more energy than a typical landing approach and the pilot was unable to arrest the descent rate before impact. Although high wind conditions and gusts prevailed at the time of the accident, the wind was within the manufacturer's maximum demonstrated crosswind velocity for the airplane.
Probable cause
The pilot's use of an improper flap setting and a subsequent inadequate flare of the airplane, which resulted in a bounced landing, and the pilot's delay in executing a go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13LA380
- Event ID
- 20130701X30753
- Case number
- CEN13LA380
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2013-06-27.
- API snapshot SHA-256: 2d33b980e111dc00e32db2e2f3c74e40f3e5fd91d006692306f620dbdd40f4ec; retrieved 2026-09-15T22:02:40.050Z.