CHI05CA232 · LET Blanik L-13
LET Blanik L-13 · Accident: hard landing
From K46 · Blair, NE to K46 · Blair, NE
Event
- NTSB case
- CHI05CA232
- 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
LET Blanik L-13
- Aircraft type
- Let 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
- N9295Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From K46 · Blair, NETo K46 · Blair, NE
- 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
- 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
- Hard landing
- 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
- Dual student › Airspeed, low
- Pilot in command(cfi) › Flare, improper
- Pilot in command(cfi) › Supervision, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The glider received substantial damage during a hard landing. The certified flight instructor (CFI), seated in the rear seat, stated that he took the front seat pilot on the flight and allowed him to land the airplane during the accident landing. The CFI stated that while over the runway, "the sink rate quickly increased dramatically to a rate too high for a normal touchdown." He stated that the front seat pilot applied full back stick and the nose came up arresting the sink rate "significantly." The tail wheel initially contacted the ground which was followed by the main wheels. The CFI stated that he noted that the dive brakes were partially extended and didn't know if they had been closed and then reopened during rollout or remained open during landing.
Probable cause
The low airspeed by the pilot and the inadequate supervision by the certified flight instructor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05CA232
- Event ID
- 20050826X01317
- Case number
- CHI05CA232
- 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, 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: a9ceaf666eb290e86091ee90a02517ecfea734d4b3e86959d577b4ca530dd870; retrieved 2026-09-22T05:32:16.087Z.