CHI00LA100 · Piper J-3C
Piper J-3C · Accident: airframe, component or system failure while maneuvering
From SD16 · Eureka, SD to an unrecorded destination
Event
- NTSB case
- CHI00LA100
- 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
Piper J-3C
- Aircraft type
- Piper J-3
- Category
- Airplane
- 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
- N71060
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From SD16 · Eureka, SDTo 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
- Maneuvering
- 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
- Airframe, component or system failure
- 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
- Flt control syst, yoke/control stick › Foreign material/substance
- Flt control syst, yoke/control stick › Jammed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The purpose of the flight was to shoot coyotes for the South Dakota wildlife management program. The pilot began a descending left turn from an altitude of 125 feet above ground level (agl) so his passenger could take a shot at a coyote. At an altitude of about 40 feet agl he attempted to level the airplane, but was unable to pull back on the control stick. The control stick was jammed with the airplane in a nose low, left bank attitude. The pilot applied rudder and pulled the power off prior to the airplane contacting the ground. The airplane impacted the terrain and slid sideways. It contacted a badger hole which resulted in the landing gear collapsing and the left wing contacting the terrain. Inspection of the airplane revealed that a 12 gauge shot gun shell was jammed in the aft control stick preventing it from being moved.
Probable cause
the foreign object (shot gun shell) which jammed the control stick. Factors associated with the accident were the low altitude at which the control stick jammed and the rough terrain which the airplane contacted.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI00LA100
- Event ID
- 20001212X20602
- Case number
- CHI00LA100
- 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: bb2a0abe793974d639d73aaf66727e08f1d6f175a4367aad82c3f65a2981035e; retrieved 2026-09-22T13:01:02.076Z.