WPR20CA150 · Air Creation TANARG
Air Creation TANARG · Accident: aircraft/propeller/rotor contact with person while standing
From Buckeye Municipal Airport (BXK) to Buckeye Municipal Airport (BXK)
Event
- NTSB case
- WPR20CA150
- 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
Air Creation TANARG
- Aircraft type
- Air Creation TANARG
- 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
- N837TB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Buckeye Municipal Airport (BXK), Buckeye, AZTo Buckeye Municipal Airport (BXK), Buckeye, AZ
- Aircraft age
- About 15 years (built 2005)
- 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
- Standing · engine(s) operating
- 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
- Aircraft/propeller/rotor contact with person
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The accident pilot had been preforming touch and go landings with several trike pilots when he decided to land and talk to another trike pilot on the ground. After landing and setting the parking brake, he exited his trike with the engine still running, to go talk to the other pilot. When he returned to his trike, it had started to move, and he chased after it. As he neared the trike, he attempted to reach around to the right rear strut with his left hand, to stop it. However, the pilot did not see the rear mounted propeller, and his left-hand fingers were struck by the propeller and he was seriously injured. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The failure of the pilot to adequately maintain a safe distance from the airplane's propeller, which resulted in a serious injury when the propeller struck his hand.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20CA150
- Event ID
- 20200518X25034
- Case number
- WPR20CA150
- 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, damage. 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: e4a6384a651c21545a519cf3d0f951959fc4ff4a6f6f15d40211686117cb4899; retrieved 2026-09-16T11:38:05.108Z.