CHI95LA209 · Cessna 182S
Cessna 182S · Accident: overrun during landing
From Dalton Airport (3DA) to Ray Community Airport (57D)
Event
- NTSB case
- CHI95LA209
- 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 182S
- 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
- N2423Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dalton Airport (3DA), Flushing, MITo Ray Community Airport (57D)
- 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 · aborted
- 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
- Overrun
- 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/mush
- 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 › Raising of flaps, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT SAID HE INITIATED A GO AROUND AFTER REALIZING HE COULD NOT STOP ON THE REMAINING RUNWAY AFTER MAKING A DOWNWIND LANDING. HE SAID HE HAD 20 DEGREES OF FLAPS EXTENDED WHEN HE STARTED THE GO AROUND. AFTER LIFTOFF THE PILOT RETRACTED THE FLAPS AT AN AIRSPEED BETWEEN 55 AND 60 KNOTS INDICATED AIRSPEED. THE AIRPLANE SETTLED INTO BRUSH AT THE RUNWAY'S DEPARTURE END AND SLOWED DOWN, ACCORDING TO THE PILOT. HE SAID HE LEFT FULL POWER IN FOR A SHORT DISTANCE BUT CLOSED THE THROTTLE AFTER HE NOTICED THE AIRPLANE WAS NOT ACCELERATING. THE AIRPLANE CONTINUED THROUGH 5 FOOT HIGH WEEDS, STRIKING 2 FENCE POSTS AND COMING TO A REST IN A DITCH. DURING AN INTERVIEW THE PILOT SAID HE OBSERVED THE WIND SOCK SHOWING RUNWAY 18 WAS THE RUNWAY IN USE. HE SAID HE LANDED ON RUNWAY 36.
Probable cause
THE PILOT'S IMPROPER RAISING OF THE FLAPS DURING THE ABORTED LANDING. FACTORS ASSOCIATED WITH THIS ACCIDENT WERE THE PILOT SELECTING THE WRONG RUNWAY, NOT ATTAINING THE APPROPRIATE TOUCHDOWN POINT ON THE RUNWAY, AND DELAY IN ABORTING THE LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI95LA209
- Event ID
- 20001207X03886
- Case number
- CHI95LA209
- 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: 4541b59c2ee165d3dde36a46b1fbc9cac830485047f83cdaaee2cb55f3dccd7a; retrieved 2026-09-22T23:41:59.928Z.