WPR12FA123 · Bellanca 7GCBC
Bellanca 7GCBC · Accident: aerodynamic stall/spin while maneuvering
From Sidney - Richland Regional Airport (SDY) to Sidney - Richland Regional Airport (SDY)
Event
- NTSB case
- WPR12FA123
- 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
- 1 · 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
Bellanca 7GCBC
- Aircraft type
- Bellanca 7
- 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
- N5542K
- Operator
- Steppler James M
- Onboard fatalities
- Unknown
- Route
- From Sidney - Richland Regional Airport (SDY), Sidney, MTTo Sidney - Richland Regional Airport (SDY), Sidney, MT
- 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 · low-altitude flying
- 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
- Aerodynamic stall/spin
- 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, not marked as estimated; no uncertainty radius is established.
NTSB narrative
Witnesses reported that the airplane made two low altitude 360 degree turns then ascended rapidly followed by a descent into the ground characteristic of a stall. The airplane “belly flopped” onto the edge of an elevated drive likely due to insufficient altitude for the pilot to recover. The witnesses further reported that the engine sounded normal throughout the accident sequence. A postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. A GPS receiver was recovered from the accident; however, no data was recovered for the accident flight. Previous flight paths revealed flight maneuvers at low altitudes similar to the one described during the accident sequence.
Probable cause
The pilot’s failure to maintain adequate airspeed and airplane control while maneuvering at a low altitude, which resulted in a stall and subsequent impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12FA123
- Event ID
- 20120306X22101
- Case number
- WPR12FA123
- 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. 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: 299080ba94df6b184edf94af1152b278721c5c470bf66e1601d10b0f3fccb88f; retrieved 2026-09-13T22:13:07.251Z.