NYC95LA199 · LET BLANIK L-13 BLANIK L-1
LET BLANIK L-13 BLANIK L-1 · Accident: on ground/water collision with terrain/water during landing
From Dart Airport (D79) to an unrecorded destination
Event
- NTSB case
- NYC95LA199
- 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
LET BLANIK L-13 BLANIK L-1
- 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
- N69AS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dart Airport (D79)To 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 · landing roll
- 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
- On ground/water collision with terrain/water
- 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 › Flight controls, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE GLIDER PILOT STATED, '...I NOTICED A SMALL PLANE MOVING DOWN RUNWAY 31. I WAS INTENDING TO LAND ON 13....I LANDED IN THE HIGH GRASS WEST OF THE RUNWAY, ABOUT 10 FEET FROM THE EDGE OF THE RUNWAY....NOT WANTING TO ROLL ACROSS THE RUNWAY INTO THE POWERLINES, DITCH, OR ROAD, I APPLIED FULL RIGHT RUDDER AND DEPLOYED MY SPOILERS. I HADN'T NOTICED THAT MY RIGHT WING HAD NOT YET CLEARED THE HIGH GRASS....MY WINGTIP DIPPED, CAUGHT IN GROUND AND DAMAGED GLIDER. THE SOLE CAUSE OF THE DAMAGE TO THE GLIDER WAS THE GROUND LOOP INSTIGATED BY MY APPLYING RUDDER WHILE WING WAS STILL IN GRASS...' ADDITIONALLY, THE STUDENT PILOT HAD A TOTAL TIME OF ABOUT 18 HOURS, OF WHICH 1 HOUR WAS SOLO TIME.
Probable cause
the pilot's improper flight control input during the landing roll in high grass, which resulted in a ground loop and subsequent wingtip damage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC95LA199
- Event ID
- 20001207X04358
- Case number
- NYC95LA199
- 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: 45d9927e4aa6bcdd9dd0a94b941b2a9e28a40ad0fff2e83e8d10c960dce55f61; retrieved 2026-09-22T23:23:52.038Z.