FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI03LA089 · Champion 7ECA

22 Mar 2003 · Raymond, MN, United States

Champion 7ECA · Accident: in flight collision with object while maneuvering

From Willmar Municipal Airport John L Rice Field (2006) (ILL) to Clara City, MN

Report a problem

Event

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

Champion 7ECA

Aircraft type
Champion 7
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
N1814G
Operator
Unknown
Onboard fatalities
Unknown
Route
From Willmar Municipal Airport John L Rice Field (2006) (ILL), Willmar, MNTo Clara City, MN
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
Maneuvering
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, transmission
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

  • Pilot in command › Altitude/clearance, not maintained
  • Pilot in command › Ostentatious display

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

NTSB narrative

The airplane impacted power lines and terrain after being observed by witnesses to be "hot dogging around in front of us and stuff." When questioned if the pilot was "showing off" the witness responded, "Yeah, I suppose." The inspection of the airplane revealed no preexisting anomalies that would have precluded normal operation.

Probable cause

The altitude/clearance not maintained by the pilot and his ostentatious display. The power lines and the pilot's maneuvering at low altitude were contributing factors.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI03LA089
Event ID
20030326X00397
Case number
CHI03LA089
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: 5440b25adcd11d7c573b667c742e5b281bfd797ca5f297e9ad59107af8d3722f; retrieved 2026-09-21T09:30:43.219Z.