ANC90FA134 · Helio COURIER H-295 COURIER H-
Helio COURIER H-295 COURIER H- · Accident: total loss of engine power (mechanical failure) en route
From Clear Airport (Z84) to Happy Valley, AK
Event
- NTSB case
- ANC90FA134
- 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
- Visual Meteorological Cond
Helio COURIER H-295 COURIER H-
- Aircraft type
- Helio COURIER H-295
- 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
- N6493V
- Operator
- Metheny, James R · private individual
- Onboard fatalities
- Unknown
- Route
- From Clear Airport (Z84), CLEAR, AKTo Happy Valley, AK
- 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
- Destroyed
Cause areas
- Engine assembly, connecting rod bolt › Separation
- Engine assembly, connecting rod cap › Separation
- Engine assembly, crankcase › Fractured
- Stabilizer › Loose
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT HAD INDICATED TO BETTLES FSS THAT HE HAD LOST POWER AND THAT HE HAD A FIRE ON BOARD. THE WRECKAGE WAS SUBSEQUENTLY LOCATED 40 MILES SE OF BETTLES. ON-SITE EXAMINATION SHOWES THAT THE RIGHT WING, BOTH AILERONS, LEFT FLAP, RUDDER, VERTICAL FIN AND STABILATOR HAD ALL SEPARATED FROM THE AIRPLANE IN FLIGHT. TWO OF THE THREE VERTICAL FIN/STABILATOR-TO-FUSELAGE MOUNTS HAD FAILED IN OVERLOAD; THE THIRD MOUNT WAS RELATIVELY UNDAMAGED WITH THE BOLT MISSING AND VISIBLE ELONGATION OF THE BOLT HOLE. ENGINE EXAM REVEALED EXTENSIVE FIRE DAMAGE TO THE #5 CYLINDER, THE HEAD AREA HAVING BEEN COMPLETELY CONSUMED BY FIRE. THE ROD CAP AND ONE BOLT COULD NOT BE FOUND AT THE WRECKAGE SITE. FOUR MONTHS PRIOR TO THE ACCIDENT MAJOR REPAIRS WERE MADE TO THE AIRFRAME, THE ENGINE NOSE CASE WAS REMOVED AND OVERHAULED, AND THE PROPELLER WAS OVERHAULED. AIRCRAFT AND PILOT INVOLVED IN LANDING ACCIDENT ON 6/29/88 SUBSTANTIALLY DAMAGING THE AIRCRAFT. LYCOMING SB RECOMMENDS ENGINE TEARDOWN AFTER SUDDEN STOPPAGE; NO RECORD OF COMPLIANCE.
Probable cause
THE FAILURE AND SEPARATION OF THE #5 CONNECTING ROD BOLT AND CAP WHICH RESULTED IN THE RUPTURE OF THE ENGINE HOUSING AND SUBSEQUENT ENGINE FIRE DUE TO OIL SPILLAGE, AND AN INADEQUATELY MOUNTED VERTICAL FIN/STABILATOR. A CONTRIBUTING FACTOR WAS THE INADEQUATE MAINTENANCE AND INSPECTION OF THE AIRCRAFT AFTER A PREVIOUS ACCIDENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC90FA134
- Event ID
- 20001212X23848
- Case number
- ANC90FA134
- 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: 65bee880598d0cc0008ccb37e090b7f9b31487e73ac7de331e23d1b143fae96a; retrieved 2026-09-21T02:24:15.772Z.