FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI03FA018 · Piper PA-24

4 Nov 2002 · Fond du Lac, WI, United States

Piper PA-24 · Accident: in flight collision with object on approach

From Porter County Municipal Airport (VPZ) to Fond du Lac County Airport (FLD)

Report a problem

Event

NTSB case
CHI03FA018
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
2 · 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-24

Aircraft type
Piper PA-24
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
N6606P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Porter County Municipal Airport (VPZ), Valparaiso, INTo Fond du Lac County Airport (FLD), Fond du Lac, WI
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
Approach
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
In flight collision with object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire, static
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

  • Pilot in command › Altitude/clearance, not maintained
  • Pilot in command › Low altitude flight/maneuver, performed

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

NTSB narrative

The airplane hit a 110 foot high power line 2.2 nautical miles south of the destination airport, and was destroyed by impact with the terrain and post-impact fire. Night visual meteorological conditions prevailed, and no flight plan was filed. A witness reported that he was about one mile south of the power lines, when he saw an airplane with it lights on flying from south to north at a very low altitude. He reported that the airplane's altitude would have been about 50 feet higher than the power lines. Inspection of the airplane revealed no pre-impact anomalies.

Probable cause

The pilot failed to maintain obstacle clearance from the power lines while on a night VFR approach. Factors to the accident included the dark night and the power lines.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI03FA018
Event ID
20021108X05450
Case number
CHI03FA018
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: 002f0fb1129a957786d27ffbfb0ff22edec7d79a6b7f89e4f72b36720163e71a; retrieved 2026-09-20T19:42:50.033Z.