LAX89FA106 · Piper PA-24-260
Piper PA-24-260 · Accident: in flight encounter with weather en route
From Palm Springs International Airport (PSP) to Montgomery-Gibbs Executive Airport (MYF)
Event
- NTSB case
- LAX89FA106
- 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
- 3 · all aircraft and ground
- Ground fatalities
- 0
- 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-260
- 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
- N9240P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Palm Springs International Airport (PSP), Palm Springs, CATo Montgomery-Gibbs Executive Airport (MYF), San Diego, 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 · cruise
- 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
- Pilot in command › Flight into known adverse weather, intentional
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE NON-INSTRUMENT RATED PILOT FIRST FILED AN IFR FLIGHT PLAN BEFORE OBTAINING A WEATHER BRIEFING. LIGHT TO MODERATE RIME ICING WAS FORECAST FROM 5,000 TO 16,000 FT. AT 1541 THE ARTCC CONTROLLER NOTICED THE MODE C ALTITUDE REPORT WAS 1,300 FT LOWER THAN THE ASSIGNED ALTITUDE OF 10,000 FT, AND DESCENDING. THE PILOT RESPONDED TO THE CONTROLLER'S INQUIRY THAT 'I CANNOT MAINTAIN ALTITUDE'. AT 1543 RADIO AND RADAR CONTACT WAS LOST. AN AIRLINE FLIGHT REPORTED PICKING UP MODERATE RIME ICE WHILE FLYING IN THE AREA OF THE ACCIDENT SITE. A GROUND WITNESS REPORTED THAT AT THE TIME OF THE ACCIDENT A THUNDERSTORM WAS OVERHEAD, ACCOMPANIED BY LIGHTNING, THUNDER, HAIL, AND MODERATE SNOW AND RAIN SHOWERS. THE WITNESS ALSO HEARD A LOUD 'WINDING UP ENGINE SOUND FOLLOWED BY A LARGE BANG'. THE LAST PITOT STATIC SYSTEM TEST AND CALIBRATION WAS RECORDED ON 7/8/86. THE PILOT HAD RECEIVED ABOUT 44 HRS DUAL INSTRUMENT TRAINING DURING THE FIRST 6 MONTHS OF 1986.
Probable cause
THE PILOT'S POOR JUDGEMENT OF INTENTIONALLY FLYING INTO AN AREA OF KNOWN FORECAST ICING CONDITIONS WHICH RESULTED IN A LOSS OF CONTROL AND AN INFLIGHT BREAKUP OF THE AIRCRAFT. CONTRIBUTING FACTORS WERE THE PILOT'S OVERCONFIDENCE IN HIS PERSONAL ABILITY BY ATTEMPTING FLIGHT INTO INSTRUMENT METEOROLOGICAL CONDITIONS, AND THE ADVERSE WEATHER CONDITIONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX89FA106
- Event ID
- 20001213X27740
- Case number
- LAX89FA106
- 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: 86eb39895c6004c2d3cd8d1f349b777fadab82b3ff7c5567db25a71273caac5a; retrieved 2026-09-21T03:24:25.029Z.