FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25LA009 · Schleicher ASK-21

6 Oct 2024 · Front Royal, VA, United States

Skyline Soaring Club Schleicher ASK-21 · Accident: abnormal runway contact during landing

Report a problem

Event

NTSB case
ERA25LA009
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

Schleicher ASK-21

Aircraft type
Schleicher ASK-21
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
N341KS
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 22 years (built 2002)
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
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
Abnormal runway contact
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The glider pilot reported the purpose of the flight was to work on landings, so he requested a “pattern tow” from the tow pilot. He released the towline on a 45° entry to the downwind leg and proceeded to fly a standard right-hand traffic pattern. The pilot stated that he kept his airbrakes in the “mostly closed” position from the final approach segment through landing. Upon touching down short of his intended aim point, the pilot reported that the glider bounced and entered a pilot-induced-oscillation, bouncing a few more times down the runway, and resulting in substantial damage to the fuselage. The pilot reported that there were no preimpact mechanical malfunctions or failures with the glider that would have precluded normal operation.

Probable cause

The pilot’s improper landing flare and subsequent improper recovery from a hard, bounced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA25LA009
Event ID
20241015195306
Case number
ERA25LA009
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, cause areas. 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: 41810ecd2a172882746541f28d2449c4ace31eab7007c55340856347e3670ba7; retrieved 2026-09-16T19:22:30.556Z.