FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI02LA146 · Cessna 182J

31 May 2002 · Galesville, WI, United States

Cessna 182J · Accident: in flight collision with object on approach

From 4W18 · Galesville, WI to 4WI8 · Galesville, WI

Report a problem

Event

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

Cessna 182J

Aircraft type
Cessna 182
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
N3027F
Operator
Unknown
Onboard fatalities
Unknown
Route
From 4W18 · Galesville, WITo 4WI8 · Galesville, 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 · VFR pattern final
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
Substantial

Cause areas

  • Pilot in command › Altitude/clearance, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane collided with static wires on final approach to land. The pilot reported that he added power then the airplane encountered a downdraft while on base leg to land. He reported that on final approach another downdraft was encountered and he applied full power, but the airplane struck power lines with the nose gear. According to the pilot, a wire broke and another wire caught the aircraft and pulled it down. The pilot reported that after touchdown the nose gear folded back and the propeller struck the ground. The wind was reported to be 330 degrees at 9 knots at La Crosse Municipal Airport, La Crosse, Wisconsin which is 22 miles southeast of Carhart Farms Airport.

Probable cause

The pilot failed to maintain clearance with the wires while on final approach. Factors associated with the accident were the low altitude, the downdraft, and the wires which the airplane contacted.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02LA146
Event ID
20020604X00802
Case number
CHI02LA146
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, coordinates. 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: 769c8d93280707c2164be748327ae683c4cbdf3a62d37d89c404316c8e1e1feb; retrieved 2026-09-22T10:53:37.209Z.