SEA94LA035 · Piper PA-28-180
Piper PA-28-180 · Accident: total loss of engine power (non-mechanical) en route
From Salem-Willamette Valley Airport/McNary Field (SLE) to Palo Alto Airport (PAO)
Event
- NTSB case
- SEA94LA035
- 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
- Instrument Meteorological Cond
Piper PA-28-180
- 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
- N8829J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Salem-Willamette Valley Airport/McNary Field (SLE), Salem, ORTo Palo Alto Airport (PAO), Palo Alto, 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 (non-mechanical)
- 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
- Induction air control, air filter/screen › Ice
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE EN ROUTE ON AN IFR FLIGHT PLAN, THE PILOT ENCOUNTERED ICING CONDITIONS. THE AIRCRAFT EXPERIENCED BOTH STRUCTURAL AND INDUCTION ICING, AND THE PILOT INITIATED A DESCENT AS THE AIRCRAFT BEGAN TO LOSE POWER. EVENTUALLY THE ENGINE LOST ALL POWER, AND THE PITOT TUBE ICED OVER. THE AIRCRAFT IMPACTED THE TERRAIN WHILE THE PILOT WAS ATTEMPTING A FORCED LANDING IN A SMALL UNFORESTED AREA. BECAUSE THE PILOT HAD LIMITED HIS 'WEATHER BRIEFING' TO SELECTED DUAT SYSTEM DATA AND AN ABBREVIATED FLIGHT SERVICE STATION BRIEFING, HE FAILED TO RECEIVE AN AIRMET WARNING OF OCCASIONAL ICING CONDITIONS ALONG HIS ROUTE OF FLIGHT.
Probable cause
THE PILOT'S INADEQUATE PREFLIGHT PLANNING/PREPARATION, AND ICING OF THE INDUCTION AIR FILTER/SCREEN. FACTORS INCLUDE WEATHER CONDITIONS CONDUCIVE TO ICING, AND ROUGH/UNEVEN TERRAIN IN THE AREA OF ATTEMPTED LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA94LA035
- Event ID
- 20001211X13804
- Case number
- SEA94LA035
- 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: 012fece60d7f25d04bb72e705d6df83a7dfd50e8a79195ca93f725628a4ef25b; retrieved 2026-09-21T14:06:54.159Z.