CEN12CA035 · Houts Avid Mark IV
Houts Avid Mark IV · Accident: powerplant system/component malfunction/failure en route
From Eveleth–Virginia Municipal Airport (KEVM) to Eveleth–Virginia Municipal Airport (KEVM)
Event
- NTSB case
- CEN12CA035
- 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
- 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
- Visual Meteorological Cond
Houts Avid Mark IV
- Aircraft type
- Houts AVID MARK
- 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
- N43280
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Eveleth–Virginia Municipal Airport (KEVM), Eveleth, MNTo Eveleth–Virginia Municipal Airport (KEVM), Eveleth, MN
- 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
- Defining eventThe 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
- Powerplant system/component malfunction/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
- Aircraft › Aircraft power plant
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that during the local flight the engine lost oil pressure and the cockpit began to fill with smoke. He immediately reduced engine power to idle and performed a forced landing to a nearby field. The airplane collided with a barbed wire fence during the landing roll and subsequently nosed over. The fuselage, right wing, and vertical stabilizer were substantially damaged. A postaccident inspection revealed that the oil supply line to the oil cooler had ruptured, which allowed oil to come in contact with the engine's hot exhaust, producing smoke. The rubber, automobile-style oil line had failed immediately adjacent to its respective oil cooler inlet fitting. The hose clamp used to secure the oil line to the inlet fitting was not properly positioned over the fitting, which allowed the unsupported hose clamp to abrade through the oil line.
Probable cause
The improper installation of a hose clamp, which resulted in an oil line rupture and subsequent loss of engine oil pressure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12CA035
- Event ID
- 20111024X91908
- Case number
- CEN12CA035
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 533cfb4ac547792045f9e3b3f1b0f92e82414384929a3ba362c94657685e9c71; retrieved 2026-09-15T16:53:02.915Z.