FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI99LA295 · Cessna 182H

15 Aug 1999 · Eagle River, WI, United States

Cessna 182H · Accident: loss of control in flight during landing

From Lewis University Airport (LOT) to Eagle River Union Airport (EGV)

Report a problem

Event

NTSB case
CHI99LA295
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
0
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 182H

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
N2498X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lewis University Airport (LOT), Romeoville, ILTo Eagle River Union Airport (EGV)
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
Landing · flare/touchdown
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 control in flight
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 › Compensation for wind conditions, inadequate
  • Pilot in command › Directional control, not maintained

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

NTSB narrative

The pilot reported that after touching down, the crosswind pushed the airplane off the side of the runway into the grass. The airplane traveled approximately 100 to 150 feet off the right side of the runway where it contacted a small hill in the terrain. The nose gear collapsed and the airplane nosed over and came to rest inverted. About 37 minutes before the accident, the reported winds 23 miles southwest of the accident site were from 180 degrees at 11 knots gusting to 17 knots. The pilot reported the local winds were from 180 degrees at 12 knots gusting to 14 knots.

Probable cause

the pilot's inadequate compensation for the crosswind conditions and the subsequent failure to maintain directional control of the airplane. Factors associated with the accident were the gusty, crosswind conditions, and the rough/uneven terrain encountered.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI99LA295
Event ID
20001212X19446
Case number
CHI99LA295
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: b7cc21b60f99d2fda06a12de0c5ff4b850598b69c8942d843d1755a828409640; retrieved 2026-09-21T20:26:03.496Z.