WPR20CA043 · John Sample BEARHAWK
John Sample BEARHAWK · Accident: collision during takeoff/landing
From Nampa Municipal Airport (MAN) to Nampa Municipal Airport (MAN)
Event
- NTSB case
- WPR20CA043
- 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
John Sample BEARHAWK
- Aircraft type
- John Sample BEARHAWK
- 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
- N719JS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Nampa Municipal Airport (MAN), Nampa, IDTo Nampa Municipal Airport (MAN), Nampa, ID
- Aircraft age
- About 11 years (built 2008)
- 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 · landing roll
- 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
- Collision during takeoff/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
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, after an uneventful flight, he verified the current weather conditions about 10 miles from the airport and subsequently entered the airport traffic pattern, at which point he chose to land on a grassy area between the runway and taxiway. The airplane touched down normally, but during the landing roll, the pilot saw an obstacle in the middle of the grassy area. The pilot was unable to react before the right main landing gear impacted a knoll, and the airplane ground looped. The right main landing gear collapsed, and the right wing sustained substantial damage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's selection of unsuitable terrain for landing, which resulted in impact with a knoll and a subsequent ground-loop.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20CA043
- Event ID
- 20191216X72031
- Case number
- WPR20CA043
- 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. 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: f7ed561233ab79c6767122124bde1883c7c7357116156e10c03194115a28299e; retrieved 2026-09-16T10:46:11.002Z.