FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI00LA103 · Piper PA-28-140

2 Apr 2000 · Pine City, MN, United States

Piper PA-28-140 · Accident: loss of engine power en route

From Mora Municipal Airport (JMR) to an unrecorded destination

Report a problem

Event

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

Piper PA-28-140

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
N54454
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mora Municipal Airport (JMR), Mora, MNTo not recorded
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

  • Terrain condition › None suitable

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

NTSB narrative

The airplane encountered an in-flight loss of engine power and sustained substantial damage on impact with a fence and vegetation during a forced landing in a field. The pilot had minor injury. The passenger was uninjured. The engine's number four cylinder's exhaust valve spring and valve were found failed. The valve spring had a 45-degree fracture approximately 0.75 inches from an end. The valve head was found with approximately a third of its' face fractured off. A section of valve head was found within the cylinder. The valve head's face and head section had indentations. The pilot stated, 'With the lake to our west, a bunch of trees to our north, a house to our south behind us, when the engine quit. I chose to turn 90[degrees] to the east fly under some high tension wires, which I knew I could do safely, to a field on the other side. The field was not very wide, but I felt it was safer for landing without any houses close by. Being 200 to 300 feet above the ground I didn't have the altitude to turn 180[degrees] and land in the field below. I could not get stopped in the narrow field, so consequently we went through the barb wire fence on the east side and hit a clump of bushes with our left wing, which brought us to a stop.'

Probable cause

A loss of engine power due to the failure of the number four cylinder's exhaust valve spring and exhaust valve. Contributing to the accident were, the barbwire fence and the clump of high vegetation encountered by the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI00LA103
Event ID
20001212X20773
Case number
CHI00LA103
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: 43492e2129e3a43b0994053af4ff1451263341a17bf3a118797ebd3752372923; retrieved 2026-09-21T20:16:24.822Z.