CHI05CA117 · Aviat A-1B
Aviat A-1B · Accident: vortex turbulence encountered while maneuvering
From Meadow, SD to Lodgepole, SD
Event
- NTSB case
- CHI05CA117
- 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
- Government
- 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
Aviat A-1B
- Aircraft type
- Aviat A-1
- 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
- N102AM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Meadow, SDTo Lodgepole, SD
- 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
- Public Aircraft
- 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
- Vortex turbulence encountered
- 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
- Pilot in command › Aircraft control, not possible
- Pilot in command › In-flight planning/decision, poor
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane collided with the terrain following a loss of control during a predator control flight. The pilot reported the purpose of the flight was an aerial hunt of coyote. The pilot stated that upon arriving in the area, he spotted a coyote and made a normal pass near it. His gunner then informed him that the shotgun had jammed so he made an "immediate 360-degree left turn." The pilot reported that when he got within 20 to 30 yards of the coyote, he encountered wake turbulence from his previous pass. He stated he applied full power and attempted to pull up. The pilot reported, "I sensed that due to the rate of descent I was going to strike the ground." The airplane contacted the terrain and became airborne before striking the terrain a second time.
Probable cause
The poor inflight planning and the pilot's inability to maintain control of the airplane. A factor associated with the accident was the low altitude at which the airplane encoutnered its own wake.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05CA117
- Event ID
- 20050617X00803
- Case number
- CHI05CA117
- 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, coordinates. 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: e5b6ca9394cd0a7b346837f83c2b125873c285d11fee3e43bd6b1b24869d29b1; retrieved 2026-09-18T21:16:02.031Z.