FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13FA086 · Beech V35A

6 Jan 2013 · Woody, CA, United States

Floyd Johnston Construction Beech V35A · Accident: loss of control in flight en route

From Imperial, CA to Fresno Yosemite International Airport (FAT)

Report a problem

Event

NTSB case
WPR13FA086
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
2 · 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 V35A

Aircraft type
Beechcraft 35
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
N35SD
Onboard fatalities
Unknown
Route
From Imperial, CATo Fresno Yosemite International Airport (FAT), Fresno, CA
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
En route · descent
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
Loss of control in flight
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 › Aircraft oper/perf/capability
  • Aircraft › Aircraft structures
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

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

NTSB narrative

During a visual flight rules cross-country flight, air traffic control was providing flight-following services. The pilot informed the controller that there was cloud cover ahead and requested an instrument flight rules clearance and approach to the destination airport. The controller granted the clearance and then instructed the pilot to maintain 14,000 ft; the pilot read back the clearance. The pilot then requested a lower altitude and was advised to expect a lower altitude in 10 to 12 miles. The pilot was subsequently cleared for a descent to 7,000 ft and issued arrival instructions. Two minutes later, the controller advised the accident pilot of a pilot report of icing in the area. One minute later, the controller issued a clearance to 6,000 ft but received no response from the pilot. The controller issued the clearance again, and the pilot acknowledged the instruction. The controller relayed a nearby outside air temperature but received no response from the pilot. The controller made several attempts to contact the pilot and also asked another pilot to try to establish contact; all attempts were unsuccessful. Two minutes later, radar contact was lost. The wreckage was located about 1 mile from the last radar return and was distributed over the terrain for about 1/2 mile, indicating that an in-flight breakup had occurred. A postaccident examination of the airframe or engine revealed no anomalies that would have precluded normal operation.

A weather study indicated that the airplane likely encountered light-to-moderate precipitation, especially near the end of the radar flight track. Precipitation and clouds would have reduced visibility. Considering the environmental freezing level, the airplane likely encountered supercooled liquid water and snowflakes about the time that voice communication was lost. Pilot reports in the immediate area described increasing instrument meteorological conditions (IMC) along with light-to-moderate icing conditions. The reports described the flight conditions as mostly smooth with some light turbulence when passing in and out of cloud tops. Along with the likely IMC, the airplane likely experienced moderate or greater icing conditions around the accident time. The airplane likely developed ice on the wings, which resulted in an aerodynamic stall followed by a loss of control and in-flight breakup during the descent.

Probable cause

An in-flight encounter with icing conditions during descent, which resulted in the airplane exceeding its critical angle-of-attack and experiencing an aerodynamic stall followed by an in-flight breakup.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13FA086
Event ID
20130107X22046
Case number
WPR13FA086
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2013-01-07.
  • API snapshot SHA-256: 0e5b5077f255385f5090d2cdb21bbf65908f718e7129be64b407f9d6f53686fd; retrieved 2026-09-14T15:51:45.948Z.