ERA22LA025 · Pipistrel Apis-Bee
Pipistrel Apis-Bee · Accident: loss of control in flight during landing
Event
- NTSB case
- ERA22LA025
- 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
- Event fatalities
- Unknown
- 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
Pipistrel Apis-Bee
- Aircraft type
- Pipistrel APIS-BEE
- 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
- N812DS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- Built the same year (2021)
- 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
- 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
- Loss of control in flight
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, this was the first flight he made in the glider. He performed the first landing with the engine up and idling, and then during the second time around the traffic pattern, he stowed the engine during the downwind leg. When he turned the glider onto the base leg of the traffic pattern, he realized that he was “coming in high,” so he extended the airbrakes. He thought the glider needed a “little more help” descending, so he put the glider into a side slip. The pilot slipped the glider two more times, and on the third slip, the nose of the glider “dropped,” and it impacted the runway in a nose down position, which resulted in substantial damage to the fuselage. Postaccident examination of the glider revealed no evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain control of the glider during the landing approach, which resulted in an aerodynamic stall and subsequent impact with the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA025
- Event ID
- 20211022104146
- Case number
- ERA22LA025
- 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: bf7daa84a3c06d1f959f32062e1b239b0e80816005e746f6198cdeaacec76134; retrieved 2026-09-16T14:41:32.247Z.