GAA17CA497 · Beech A36 UNDESIGNAT
Comtemporary Communication Systems Beech A36 UNDESIGNAT · Accident: runway excursion during landing
From 043 · Yerington, NV to Warm Springs Creek Airport (0U1)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- GAA17CA497
- 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
Beech A36 UNDESIGNAT
- Aircraft type
- Beechcraft 36
- 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
- N136BJ
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From 043 · Yerington, NVTo Warm Springs Creek Airport (0U1), Loman, ID
- Aircraft age
- About 40 years (built 1977)
- 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
- Runway excursion
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, as he approached the airport, he requested a wind and weather PIREP. An unknown person replied on the CTAF to expect winds out of the west. With the intent of landing on runway 2, the pilot overflew the airfield and observed a light crosswind from the west. He landed the high-performance airplane on a 2,580-ft-long turf surface.
The pilot recalled a shift in wind direction during landing. The airspeed as he crossed the runway threshold was about 90 knots, and the airspeed "increased dramatically" during the landing flare and touchdown. The pilot applied the brakes; however, the airplane overran the departure end of the runway and collided with a tree. The airplane sustained substantial damage to the engine mounts and the fuselage.
According to the pilot, witnesses to the accident recalled that the airplane landed in variable wind conditions and touched down with a 20- to 30-knot tailwind.
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 inadequate compensation for a tailwind, which resulted in a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA497
- Event ID
- 20170821X15900
- Case number
- GAA17CA497
- 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: 1025602ce43d66a0e5c6c47c2e7b452ae8258acf7f033256c08a34a98dd9bb86; retrieved 2026-09-16T05:43:47.457Z.