ERA19LA016 · SA300 Starduster
SA300 Starduster · Accident: collision during takeoff/landing on approach
From Maidment Field (7MS3) to Maidment Field (7MS3)
Event
- NTSB case
- ERA19LA016
- 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
SA300 Starduster
- Aircraft type
- Sa300 STARDUSTER
- 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
- N503CM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Maidment Field (7MS3), Byhalia, MSTo Maidment Field (7MS3), Byhalia, MS
- Aircraft age
- About 27 years (built 1991)
- 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 · VFR pattern final
- 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
- Collision during takeoff/landing
- 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
- 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
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot reported that he was practicing landings. He departed and flew over a nearby town and noted that the air was "quite turbulent." Upon returning to the airport, the pilot entered the downwind leg of the traffic pattern and began a constant-radius, descending turn to the final leg of the traffic pattern. He noticed that the airplane was too low and applied engine power to maintain level flight. The airplane leveled off, and the pilot continued the approach to the runway. The pilot added that, as the airplane approached a tree line, which was about 100 ft before the approach end of the runway, the airplane "suddenly sank" and impacted trees before he could arrest the descent. The airplane came to rest inverted in a wooded area. The wings, fuselage, and empennage sustained substantial damage.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. Given the evidence, it is likely that the pilot did not maintain a proper approach path, which resulted in the impact with trees.
Examination of upper air sounding data revealed that no turbulence nor low-level wind shear existed in the area at the time of the accident. A review of meteorological data revealed that the wind conditions had the potential to develop into a 1-knot tailwind. However, the pilot should have been able to anticipate and adequately respond to the slight tailwind.
Probable cause
The pilot's failure to maintain a proper approach path, which resulted a collision with trees short of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA19LA016
- Event ID
- 20181012X62050
- Case number
- ERA19LA016
- 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: investigation status. 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: c846fcb67a18ed1ad9708e25aa577a6c66f43816d2aed65871627a961e1b8527; retrieved 2026-09-16T08:20:21.645Z.