WPR10CA050 · Aeromot AMT-200(SU
Aeromot AMT-200(SU · Accident: airport occurrence during landing
From O1LC · Placerville, CA to O1LC · Placerville, CA
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR10CA050
- 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
Aeromot AMT-200(SU Narrative disagrees
- Aircraft type
- Aeromot AMT-200
- Category
- Glider
- 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
- N107MJ
- Operator
- Stenbock Roger M
- Onboard fatalities
- Unknown
- Route
- From O1LC · Placerville, CATo O1LC · Placerville, CA
- 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 · landing roll
- 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
- Airport occurrence
- 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
- Environmental issues › Physical environment
- Personnel issues › Action/decision
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 reported that during the landing rollout at the private airport, the glider's left wing struck a series of bushes located along the side of the landing runway. After striking the bushes, the glider swerved, exited the runway and came to rest in a ravine located along the right side of the runway. The glider sustained substantial damage to the right wing and aileron. The pilot reported that the airplane's wing span is approximately 60-feet and the width of the paved runway is approximately 50-feet, with a 10-foot shoulder on each side of the runway. The pilot reported the bushes were located approximately 900-feet from the landing threshold, were 4-7 feet tall, and 8-12 feet from the pavement edge on neighboring property to the north of his runway. In a written report, he indicated that there were no mechanical malfunctions or failures with the glider at the time of the accident. Following the accident, the neighboring property owner removed the bush.
Probable cause
The pilot's failure to maintain clearance from an obstacle during the landing rollout. Contributing to the accident was the presence of the brush in proximity to the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10CA050
- Event ID
- 20091109X85421
- Case number
- WPR10CA050
- 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, 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: 69ea6c1fc10838866f4f0bf7675dbea70aaf0fc0c16d2f576e3598dee7896dea; retrieved 2026-09-15T13:28:59.284Z.