FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR15CA110 · Raytheon Aircraft Company B300 UNDESIGNAT

9 Feb 2015 · Mammoth Lakes, CA, United States Narrative disagrees

West Coast Charters Raytheon Aircraft Company B300 UNDESIGNAT · Accident: turbulence encounter en route

From John Wayne Orange County International Airport (SNA) to Mammoth Yosemite Airport (MMH)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

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

Raytheon Aircraft Company B300 UNDESIGNAT

Aircraft type
Beechcraft 300
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
N49WC
Onboard fatalities
Unknown
Route
From John Wayne Orange County International Airport (SNA), Santa Ana, CATo Mammoth Yosemite Airport (MMH), Mammoth Lakes, CA
Aircraft age
About 19 years (built 1996)
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
Turbulence encounter
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

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that while in a descent from 16,000 feet, at 1,500 feet per minute, slowing from 190 knots indicated airspeed to 160 knots, the airplane encountered extreme turbulence. The pilot reported one hard jolt up/down followed by about 15 seconds of light turbulence then one final hard jolt similar to the first. The weather was visual conditions and no turbulence was encountered prior to or after the event. A postflight examination of the airplane revealed that the extreme turbulence encountered resulted in substantial structural damage to both wings spars.

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

Probable cause

The airplane encountered extreme turbulence during descent.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR15CA110
Event ID
20150220X75302
Case number
WPR15CA110
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2015-02-10.
  • API snapshot SHA-256: 819ba9db52ed8e25b7a67986516217318db41d8de868c4e7f870e2d7fb9fd0a3; retrieved 2026-09-16T02:05:57.891Z.