FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI97LA229 · Piper PA-28-140

26 Jul 1997 · Mapleton, IA, United States

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

From West Bend Municipal Airport (ETB) to Rocky Mountain Metropolitan Airport (BJC)

Report a problem

Event

NTSB case
CHI97LA229
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
N1690J
Operator
Unknown
Onboard fatalities
Unknown
Route
From West Bend Municipal Airport (ETB), West Bend, WITo Rocky Mountain Metropolitan Airport (BJC), Denver, CO
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

  • Reason for occurrence undetermined

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

NTSB narrative

The pilot reported he had been flying for about four hours. Everything was operating normally when the engine suddenly quit, and he made a forced landing into a cornfield. The airplane was certified in the Experimental category and had modifications to include: vortex generators, propeller tip modifications, gap seals, new stabilizer tips, electronic ignition, oversized pistons, modified nose cowl, wheel pants, and add-on wingtip fuel tanks. The fuel system and electrical ignition system continuity were checked after the accident and no discrepancies were found. The pilot ran the engine before the airplane was removed from the cornfield. He reported that the engine started but ran rough. He put the wires back on properly, which had been damaged during the accident. He reported that it ran 'beautifully,' and that he could not find anything mechanically wrong with the airplane.

Probable cause

the loss of engine power for undetermined reasons. A factor was the cornfield in which the pilot was forced to land.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI97LA229
Event ID
20001208X08341
Case number
CHI97LA229
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: 3442417120328d97342e91db62615b2240c3a3212d48441bc98cc038dbe362cc; retrieved 2026-09-21T21:18:42.584Z.