LAX82FA347 · Piper PA-28RT-201T PA-28RT-20
Piper PA-28RT-201T PA-28RT-20 · Accident: total loss of engine power (mechanical failure) en route
From Santa Monica, CA to Santa Monica, CA
Event
- NTSB case
- LAX82FA347
- 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
- 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
- Visual Meteorological Cond
Piper PA-28RT-201T PA-28RT-20
- Aircraft type
- Piper PA-28
- 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
- N8094F
- Operator
- Danforth & Assoc
- Onboard fatalities
- Unknown
- Route
- From Santa Monica, CATo Santa Monica, 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
- Total loss of engine power (mechanical 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
- Company maintenance personnel › Maintenance, inspection, inadequate
- Company maintenance personnel › Maintenance, service bulletin/letter, not followed
- Engine assembly, connecting rod › Failure, total
- Ignition system, distributor › Shorted
- Ignition system, magneto › Inoperative
- Ignition system, spark plug › Corroded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ENG SEIZED APPROXIMATELY 3500 FT & THE ACFT WAS DITCHED OFF THE BEACH. THE RIGHT MAG DISTRIBUTOR BLOCK SHOWED EVIDENCE OF CARBON TRACKING & CROSS FIRING. NEITHER END OF THE RIGHT MAG HAD BREATHER PLUGS INSTALLED. ALL SPARK PLUGS WERE EXCESSIVELY FOULED & SEVERELY ERODED. SPRINGS ON THE SPARK PLUGS LEADS WERE BURNED & DIRTY. THE #1 CONROD WAS SPLITLENGTHWISE & WAS IN SEVERAL PIECES. EXAMINATION OF THE LOG BOOK SHOWED IMPROPER MAINTENANCE PRACTICES SUCH AS OVERHAULING A CYLINDER & INSTALLING DETERGENT TYPE OIL. NO EVIDENCE OF COMPLIANCE WITH TELEDYNE SERVICE BULLETIN #612 COULD BE FOUND. THIS BULLETIN RECOMMENDS PERIODIC MAINTENANCE PROCEDURES TO ESTABLISH CLEANING & INSPECTION GUIDELINES GOVERNING BENDIX MAGNETOS & IGNITION HARNESSES.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX82FA347
- Event ID
- 20020917X04767
- Case number
- LAX82FA347
- 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: e124940220dd628ff4f068c91425a2fd76e152eef5d15f6692ab5f28d558bb63; retrieved 2026-09-24T00:47:57.058Z.