FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA00LA157 · Hamer LANCAIR 235 LANCAIR 23

10 Aug 2000 · Chiloquin, OR, United States

Hamer LANCAIR 235 LANCAIR 23 · Accident: loss of engine power en route

From Chiloquin State Airport (2S7) to 2S7

Report a problem

Event

NTSB case
SEA00LA157
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

Hamer LANCAIR 235 LANCAIR 23

Aircraft type
Hamer LANCAIR 235
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
N84LH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chiloquin State Airport (2S7), Chiloquin, ORTo 2S7
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
Loss of engine power
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

  • Engine assembly, crankshaft › Failure

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Shortly after takeoff, at an altitude of approximately 150 feet above ground level (AGL), the airplane developed a rough running engine and the pilot initiated a forced landing to a nearby highway. The pilot stated that he planned on landing the airplane on a non-congested area of the highway, however, the aircraft collided with a flatbed tractor-trailer combination that was traveling on the Interstate. Post-accident inspection and teardown of the airplane's engine revealed that the engine's crankshaft was fractured and had separated between the number three and number four crankpins.

Probable cause

Loss of engine power due to a fracture and separation of the engine's crankshaft. A factor was a vehicle on the roadway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA00LA157
Event ID
20001212X21863
Case number
SEA00LA157
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: 0d3a626b9a8c374338aa7eb2ff3254b99d41459078bf329f1ca7af8b7da52c24; retrieved 2026-09-22T12:36:46.645Z.