FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11FA155 · Muse KR2

7 Mar 2011 · Newberry Springs, CA, United States

Muse KR2 · Accident: aircraft structural failure during an uncontrolled descent

From Porterville Municipal Airport (KPTV) to Needles Airport (KEED)

Report a problem

Event

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

Muse KR2

Aircraft type
Muse KR2
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
N122B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Porterville Municipal Airport (KPTV), Porterville, CATo Needles Airport (KEED), Needles, 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
Uncontrolled 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
Aircraft structural failure
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 structures
  • Environmental issues › Conditions/weather/phenomena

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

NTSB narrative

The pilot had no previous experience flying the experimental airplane, although he did have the last registered owner give him a 1-hour overview of the airplane, including a demonstration of the flight controls. The pilot appeared to be rushed and departed in the airplane without performing a test flight. There was no record of the pilot receiving a weather briefing. The previous registered owner said that the airplane did not perform well in windy conditions due to its weight and design.

The airplane departed and proceeded south while gradually ascending and leveling off about 9,500 feet mean sea level (msl). About 30 minutes after departure, the airplane turned to an easterly direction and began a 12-minute ascent to 14,800 feet msl. The airplane proceeded in a meandering southeasterly course and descended to 12,000 feet msl. About 30 minutes later, the airplane turned to a meandering easterly course and started another gradual descent to 7,000 feet msl. During the last 12 minutes of the flight, the altitude fluctuated between 5,800 and 7,300 feet msl. The final radar return was located 1 mile west of the accident location and showed the airplane 1.5 hours after departure, at 7,100 feet msl (5,170 feet above ground level).

In the vicinity of the accident site, around the time of the accident, there was a westerly surface wind at 40 mph, gusting to 56 mph. The highest surface wind was reported north of the accident location with wind gusts up to 73 mph. At 9,500 feet msl, the wind was from 245 degrees at 28 knots, which resulted in a strong local vertical wind shear capable of producing moderate or greater turbulence in the layer. Several pilots operating in the area of the accident site reported encountering updrafts and downdrafts, from 1,500 to 2,500 feet per minute, and unusually strong low-level wind and turbulence.

The airplane debris field was comprised of large heavy debris (engine and landing gear) near the location of the initial impact and lighter debris that was distributed downwind. Two items, a 2-foot-long section of vertical stabilizer and an 8-inch piece of rudder skin, were found 1,820 feet and 2,880 feet (respectively) downwind from the main debris scatter area, significantly farther from the main debris scatter area, which would indicate these two items were the first to depart the airplane. The overall debris pattern, and lack of damage to the wings is consistent with an in-flight breakup of the airplane. The rapid descent was probably initiated by the separation of about half of the vertical stabilizer as a result of severe turbulence while the airplane was near the location of the final radar return. The departure of a portion of the vertical stabilizer and pieces of the rudder would have resulted in the pilot’s inability to control the airplane, followed by a rapid descent and subsequent in-flight breakup.

Probable cause

The airplane’s encounter with severe turbulence, which resulted in the in-flight breakup of the airplane. Contributing to the accident was the pilot’s inadequate preflight planning.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11FA155
Event ID
20110309X21618
Case number
WPR11FA155
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: 34d35d6c7756849f5c66371f00448b66d7322f81e4aa2a231a88674ebe42c1cd; retrieved 2026-09-13T21:16:18.678Z.