FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI02LA065 · Piper PA-18

20 Jan 2002 · Clear Lake, MN, United States

Piper PA-18 · Accident: loss of engine power during takeoff

From Leaders Clear Lake Airport (8Y6) to an unrecorded destination

Report a problem

Event

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

Piper PA-18

Aircraft type
Piper PA-18
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
N7113K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Leaders Clear Lake Airport (8Y6), Clear Lake, 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
Takeoff
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
  • Unsuitable terrain or takeoff/landing/taxi area › Encountered

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

NTSB narrative

The airplane collided with two fences during a forced landing to a field following an engine failure while in the traffic pattern. The pilot said that he had performed three "run ups" and was going to perform "...some take-offs and landings after the annual." He said that after take-off, at about 400 feet agl, the engine lost power and quit. He said that he had just turned from the crosswind leg of the traffic pattern to the downwind leg. The pilot stated that he could not make it back to the airport, and could not land directly ahead due to obstructions. The pilot said that he attempted to land in a field but the field did not have enough room for the landing and he hit two fences before coming to rest. A postaccident examination of the airplane revealed no anomalies that could be associated with a pre-impact condition. The engine was subsequently test run on the airframe and no anomalies were found. The weather observing station located about 7 miles and 330 degrees from the accident recorded the temperature as -3 degrees Celsius and the dewpoint as -7 degrees Celsius at 1453. According to a Transport Canada carburetor icing probability chart, the temperature and dewpoint fall in the range for light icing at cruise or descent power.

Probable cause

The loss of engine power for undetermined reasons and the unsuitable terrain for the forced landing. Factors were the low altitude and the fences.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02LA065
Event ID
20020129X00148
Case number
CHI02LA065
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: db2e089edf3cfcea61e55357c3d35be3ae987778c3335cb75963eb49a90b2729; retrieved 2026-09-22T11:11:28.412Z.