SEA07FA277 · Bellanca 8KCAB-180
Flying M Hunting Club Bellanca 8KCAB-180 · Accident: in flight encounter with weather while maneuvering
From Yerington, NV to Yerington, NV
Event
- NTSB case
- SEA07FA277
- 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 8KCAB-180
- Aircraft type
- Bellanca 8
- 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
- N240R
- Operator
- Flying M Hunting Club
- Onboard fatalities
- Unknown
- Route
- From Yerington, NVTo Yerington, NV
- 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
- 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
- In flight encounter with weather
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft performance, climb capability › Exceeded
- Pilot in command › Climb, not possible
- Pilot in command › Flight into adverse weather, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed from a private airport at Flying M Ranch on a local personal flight, which ground personnel thought would last about 2.5 to 3 hours. When the airplane failed to return, it was reported missing and a search was started. No emergency locator transmitter (ELT) signal was received from the airplane. The Civil Air Patrol suspended its search activities after about 1 month. About 1 year later, a hiker found some of the pilot’s personal effects, and an aerial search located the airplane wreckage about 0.5 mile from the personal effects. The accident occurred in remote mountainous terrain at an elevation of 10,000 feet. After the wreckage was discovered, a review of radar data from September 3, 2007, revealed a track that ended about 1 mile northwest of the accident site. This 20-minute track showed the airplane flying south along the crest of a mountain range with elevations greater than 13,000 feet.
During the search efforts, aircraft had flown over the accident location but did not see the wreckage. Additionally, the 20-minute track had been ruled out as the accident flight due to a witness report of seeing the airplane near Yerington at the time of the track. The witness reported the time of his sighting based on a telephone call with a friend. The search team initially used the time provided by the witness. Later, it was determined from the telephone company’s time log that the witness-reported time was off by 1 hour.
Examination of the accident site revealed that the airplane was on a northerly heading at impact, indicating that the pilot had executed a 180-degree turn after radar contact was lost. Ground scars and distribution of the heavily fragmented wreckage indicated that the airplane was traveling at a high speed when it impacted in a right wing low, near level pitch attitude. A postimpact fire consumed the fuselage, with the exception of its steel frame. The wings were fragmented into numerous pieces. The ELT was destroyed. Damage signatures on the propeller blades and the engine crankshaft indicated that the engine was operating at impact. Examination of the airframe and engine revealed no evidence of any malfunctions or failures that would have prevented normal operation.
Visual meteorological conditions existed in the accident area at the time of the accident. Mean winds at 10,000 feet were from 220 degrees at 15 to 20 knots; some gusts of 25 to 30 knots may have occurred. Moderate turbulence and downdrafts of at least 400 feet per minute probably occurred at the time and in the area of the accident. The magnitude of the downdrafts likely exceeded the climb capability of the airplane, which, at a density altitude of 13,000 feet, was about 300 feet per minute.
Probable cause
The pilot’s inadvertent encounter with downdrafts that exceeded the climb capability of the airplane. Contributing to the accident were the downdrafts, high density altitude, and mountainous terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA07FA277
- Event ID
- 20081007X17184
- Case number
- SEA07FA277
- 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. 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: e3834e50c69a908d27d0cd3c292ce44d8eb81b5c41fe10ab62ca207d5e38f9ae; retrieved 2026-09-20T16:18:55.654Z.