DEN01LA143 · Blanik L-13
Blanik L-13 · Accident: in flight collision with object on approach
From Morgan County Airport (42U) to an unrecorded destination
Event
- NTSB case
- DEN01LA143
- 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
Blanik L-13
- Aircraft type
- Blanik L-13
- 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
- N310GM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Morgan County Airport (42U), Morgan, UTTo 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
- Approach · VFR pattern final
- 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
- In flight collision with object
- 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 › Lowering of flaps, inadvertent
- Pilot in command › Spoiler extension, not selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The glider was a little high as the pilot approached the airport for landing. She pulled the spoiler handle twice and heard what she thought was the sound of the spoilers deploying, but failed to verify it visually. She had actually pulled the flap handle. The glider overshot the runway and she elected to land on a road adjacent to the departure end of the runway. The right wing was severed when the glider struck a tree and ground looped. The empennage was also torn off. The pilot said the flap handle is next to the spoiler handle and they are identical in appearance. The flap handle was found unlocked and half deployed; the spoiler handle was stowed.
Probable cause
the pilot's inadvertent lowering of the flaps and her failure to extend the spoilers.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN01LA143
- Event ID
- 20010814X01686
- Case number
- DEN01LA143
- 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: 761598e0f8a8e2c95dcf5911797c31bd6736330696910f362abdab08bcdffa46; retrieved 2026-09-22T11:40:00.031Z.