FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI04LA064 · Piper PA-28R-200

7 Feb 2004 · Lone Rock, WI, United States

Piper PA-28R-200 · Accident: in flight encounter with weather on approach

From John H Batten Airport (RAC) to Tri-County Regional Airport (LNR)

Report a problem

Event

NTSB case
CHI04LA064
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-28R-200

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
N5039S
Operator
Unknown
Onboard fatalities
Unknown
Route
From John H Batten Airport (RAC), Racine, WITo Tri-County Regional Airport (LNR), Lone Rock, 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 encounter with weather
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
Stall
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 › Airspeed, 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 was substantially damaged during an in-flight collision with terrain following an inadvertent stall on short final. The pilot reported that the instrument flight rules (IFR) flight had initially been operating above a broken to overcast cloud layer. However, about the mid-point of the trip the flight encountered instrument meteorological conditions (IMC) and light rime ice. The pilot stated that he requested a higher altitude in an attempt to avoid the icing conditions, but air traffic control cleared him to a lower altitude due to the flight's proximity to its intended destination. The flight remained in IMC as it was vectored for an instrument approach. At the missed approach point, the pilot did not have the airport in sight due ground snow cover and his unfamiliarity with the area. He executed a missed approach. While being provided with radar vectors for another approach, the pilot obtained visual contact with the airport. When he entered visual flight rules (VFR) conditions, he cancelled the IFR flight plan and entered a traffic pattern for runway 36. The pilot reported that on short final the airplane drifted left of the runway centerline. He applied a little power in an attempt to get re-aligned. The pilot stated: "The aircraft started rolling left. I applied full power and attempted to abort my landing. The aircraft engine responded but we completely rolled until inverted and subsequently made contact with the ground." In a follow-up interview, the pilot stated that the aircraft had accumulated rime ice along the leading edges of the wings. An AIRMET for occasional moderate rime or mixed icing below 10,000 feet mean sea level was in effect at the time of the flight. A certified re-recording of the weather briefing was provided to the NTSB. During the briefing, the pilot was informed of the AIRMET and of a pilot report of light rime ice along his route of flight. The pilot had received his instrument rating seven weeks prior to the accident. He reported 2.5 hours of actual instrument flight time and minimal experience with in-flight icing conditions. Federal Aviation Administration publications state that ice formation on an aircraft's flight surfaces may adversely affect performance and control. They note that with ice accretion an "aerodynamic stall may occur with little or none of the usual cues in advance of the stall or at the occurrence of stall."

Probable cause

The pilot's continued flight into icing conditions resulting in ice accretion on the wing and his failure to maintain airspeed resulting in a stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04LA064
Event ID
20040210X00178
Case number
CHI04LA064
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: a4a212833b2fead2ae2f40b2bdb3aeda73b4efd1225c5a3cc2a8890c9d095a34; retrieved 2026-09-21T19:17:48.209Z.