WPR21LA053 · Air Creation Buggy
Air Creation Buggy · Accident: hard landing
Event
- NTSB case
- WPR21LA053
- 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
Air Creation Buggy
- Aircraft type
- Air Creation BUGGY
- Category
- Weight-Shift
- 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
- N2764N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 19 years (built 2001)
- 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
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The non-rated pilot reported that he was landing the weight control shift aircraft. While on a final approach, about 40 ft above the ground, he increased the engine power to arrest an excessive descent rate. The rapid descent continued, and the front tire struck the edge of the runway. As a result, the front wheel assembly “broke” and got jammed on the throttle cable, and with its weight on the cable, set the throttle setting to full. The aircraft tookoff and became airborne. The pilot safely maneuvered the aircraft at full throttle around the traffic pattern and initiated a power off landing north of the runway in the dirt field. Shortly after touchdown, the aircraft “somersaulted” once before coming to a stop. Both wings were substantially damaged. The non-rated pilot reported that there were no preaccident mechanical failures or malfunctions that would have precluded normal operation.
Probable cause
The non-rated pilot’s unstable approach and failure to maintain aircraft control, which resulted in a hard landing and collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR21LA053
- Event ID
- 20201113102285
- Case number
- WPR21LA053
- 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, coordinates, 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: 95ff65f8280e6af3173efaf89796857920e8384c157b5256147323a9ba6869df; retrieved 2026-09-16T13:22:48.011Z.