SEA83LA079 · Erco 415C
Erco 415C · Accident: total loss of engine power (non-mechanical) en route
From Vancouver, WA to Oregon City, OR
Event
- NTSB case
- SEA83LA079
- 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
Erco 415C
- Aircraft type
- Erco 415
- 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
- N87110
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Vancouver, WATo Oregon City, OR
- 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)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel contamination
- 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
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCRAFT COLLIDED WITH A FENCE AND COLLAPSED THE NOSE GEAR DURING A FORCED LANDING AFTER THE ENGINE LOST POWER IN CRUISE FLIGHT. THE PILOT HAD DEPARTED OREGON CITY EARLIER TO FLY TO EVERGREEN AIRPORT TO FUEL THE AIRCRAFT AND THEN TO RETURN TO OREGON CITY. AFTER FUELING HE STARTED THE RETURN FLIGHT. EARLY IN THE FLIGHT THE ENGINE STARTED SPUTTERING. A FORCED LANDING WAS MADE IN A PASTURE. THE ACFT HIT A FENCE AND THE NOSE GEAR DUG IN DURING ROLLOUT AND COLLAPSED. THE ACFT HAD BEEN PARKED OUTDOORS AT EVERGREEN DURING THE WINTER WITH ONLY 2 GALLONS OF FUEL IN THE MAIN WING TANKS. THE FUSELAGE TANK HAD BEEN KEPT FULL AND PROVIDED A TROUBLE-FREE FLIGHT TO EVERGREEN WHERE THE MAIN TANKS WER FILLED. AFTER THE ACCIDENT THE GASCOLATOR BOWL WAS DRAINED AND YEILDED ABOUT A TEASPOON OF WATER. THE PILOT STATED HE KEPT MINUMUM FUEL IN THE WING TANKS AT OREGON CITY BECAUSE OF FUEL THEFT. HE HAD NOT CHECKED THE TANKS FOR WATER AFTER FUELING. NO WATER WAS FOUND IN THE EVERGREEN FUEL SUPPLY.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA83LA079
- Event ID
- 20001214X42831
- Case number
- SEA83LA079
- 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: 3ddbaac8bd1b00fbc35143a544b561158b55fa22bf905bd4083b5a4af5723c1b; retrieved 2026-09-23T22:32:44.517Z.