FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA369 · Stinson 108 3

8 Jul 2016 · Red Lodge, MT, United States

Stinson 108 3 · Accident: wildlife encounter (non-bird) during takeoff

From Red Lodge Airport (RED) to Billings Logan International Airport (BIL)

Report a problem

Event

NTSB case
GAA16CA369
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

Stinson 108 3

Aircraft type
Stinson 108
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
N955C
Operator
Unknown
Onboard fatalities
Unknown
Route
From Red Lodge Airport (RED), Red Lodge, MTTo Billings Logan International Airport (BIL), Billings, MT
Aircraft age
About 69 years (built 1947)
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
Takeoff
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
Wildlife encounter (non-bird)
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

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot of the tailwheel equipped airplane reported that during takeoff he noticed movement from the left as a deer ran onto the runway. He further reported that he applied right rudder to avoid hitting the deer, but the deer impacted the airplane between the left pilot's door and the horizontal stabilizer causing the airplane to veer to the left. The pilot stated that he attempted to recover by applying maximum right brake and right rudder, however it was ineffective and the airplane exited the runway to the left, ground looped, and nosed over. The airplane sustained substantial damage to both wings, empennage and fuselage.

The pilot reported that there were no pre impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

Probable cause

A deer running across the runway and impacting the left side of the airplane, resulting in a loss of directional control, a runway excursion, and a ground loop.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA369
Event ID
20160711X51106
Case number
GAA16CA369
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: f22288954b01ca77ca1b6941a2d7d565f5bbad92373bf9211abd239b4aa48655; retrieved 2026-09-16T03:38:45.271Z.