MIA99LA231 · Alson g. Siler CH-701
Alson g. Siler CH-701 · Accident: loss of control in flight during landing
From N44 to an unrecorded destination
Event
- NTSB case
- MIA99LA231
- 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
- 0
- 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
Alson g. Siler CH-701
- Aircraft type
- Alson G Siler CH-701
- 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
- N4394S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From N44To not recorded
- 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
- Loss of control in flight
- 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
- Pilot in command › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot spent 5 years building the airplane which was signed off 4 days earlier by the FAA for 40 hours test phase. He had flown the airplane 2 previous times that day, each for 30 minutes. The accident flight departed, then returned to the airport and he stated that he was landing using runway 21 for the first time. He was on a long, low, final approach, and the airplane bounced twice and headed towards a corn field. He applied full power to go-around but the airplane collided with the tops of trees adjacent to the field, then the ground. A witness reported seeing the airplane on a low approach and believed the airplane would land short of the runway. He heard power applied and the airplane cleared a road near the approach end of the runway, then heard power decreased and observed the nose landing gear contact. The airplane bounced, he then heard power applied then reduced, and the airplane bounced again. He then heard power applied, observed the airplane turn to the left, and collide with trees. Examination of the site by an FAA inspector revealed the airplane collided with trees 100-150 yards south of the runway.
Probable cause
The failure of the pilot to apply sufficient right rudder input during the go-around following a bounced landing and his failure to maintain runway alignment resulting in the in-flight collision with trees 100-150 yards to the left of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA99LA231
- Event ID
- 20001212X19597
- Case number
- MIA99LA231
- 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. 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: d60132ec91d240516f5f7d81ed3b63cbb1fb18d61217c8b2eb5324f87019d81a; retrieved 2026-09-21T10:52:36.801Z.