FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03FA051 · Piper PA-24-250

16 Dec 2002 · Anaheim Hills, CA, United States

Piper PA-24-250 · Accident: in flight encounter with weather on approach

From Prescott Regional Airport - Ernest A. Love Field (PRC) to John Wayne Orange County International Airport (SNA)

Report a problem

Event

NTSB case
LAX03FA051
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
Instrument Meteorological Cond

Piper PA-24-250

Aircraft type
Piper PA-24
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
N6268P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo John Wayne Orange County International Airport (SNA), Santa Ana, 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
Approach
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

  • Pilot in command › Design stress limits of aircraft, exceeded
  • Weather condition › Turbulence(thunderstorms)
  • Weather condition › Windshear

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

NTSB narrative

The airplane sustained an in-flight breakup following an encounter with weather. The flight was in instrument conditions on an IFR clearance and being radar vectored to the ILS final approach course at 3,000 feet when the breakup occurred. The left wing tip and the outboard 1/2 of the left and right horizontal stabilators were the first pieces of wreckage in the 1/4-mile long debris path. The horizontal stabilators exhibited permanent down deformation at the separation points. The wings exhibited both up and down permanent deformation of the spars and other structural elements. The fracture surfaces at the separation points for the wings and stabilators were consistent with structural overload. There is no record that the pilot requested or received a preflight weather briefing. The National Weather Service (NWS) issued SIGMETs and AIRMETs for occasional severe turbulence, strong gusty winds, low level wind shear, and for occasional severe rime to mixed icing in clouds. The SIGMETs and AIRMETS were valid prior to the pilot's departure and covered the timeline of the flight. The NWS weather radar depicted moderate intensity echoes extending over the accident site. While en route at 1219, the pilot requested the current destination weather from the center controller, who provided the METAR report of 10 miles visibility and broken layers at 4,000 and 20,000 feet. Shortly after the pilot was given this observation, the destination conditions rapidly deteriorated to include lowering ceilings, strong and gusty winds, and moderate to heavy rain showers. The destination weather 30 minutes prior to the accident included winds gusting to 21 knots with scattered clouds at 3,800 feet, and a broken layer at 10,000 feet. A special observation issued about 5 minutes prior to the accident indicated that winds were gusting 14 to 19 knots, visibility was 2 miles in moderate rain and mist, a broken ceiling was at 2,800 feet, and the sky was overcast at 5,000 feet. It noted that rain began about 15 minutes earlier than the observation time. Five minutes after the accident, another observation reported that the winds were gusting to 21 knots, visibility was 1 1/2 miles with moderate rain, and broken and overcast ceilings at 2,100 feet and 4,700 feet respectively. The crew of a Boeing 757 making the approach 10 minutes after the accident reported a 45-knot crosswind shear at 100 feet, and light to moderate turbulence throughout the approach. An analysis of the weather conditions at the time of the accident, including radar and satellite sensor imagery, disclosed that strong weather echoes existed near the accident site with embedded areas of intense to extreme echoes. The tops were in excess of 33,000 feet. The analysis indicated that several low level wind shear layers were present with moderate to severe turbulence.

Probable cause

the pilot's encounter with forecast severe turbulence during an inadvertent penetration of an intense weather cell, which resulted in the pilot exceeding the design structural limits of the airplane. A factor in the accident was the pilot's inadequate preflight planning and preparation, and his failure to obtain a complete weather briefing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03FA051
Event ID
20021226X05638
Case number
LAX03FA051
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, 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: 1f0b15f2e8e28135df2cab7fc5a75f3bbf01fc8cc2d9bfdbb6c260a9d341a1ad; retrieved 2026-09-20T19:33:53.356Z.