FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

St Charles Flying Service Cessna R182 accident

28 Aug 1993 · ST LOUIS, MO, United States

Cessna R182 · Accident: in flight collision with terrain/water during landing

From Indianapolis International Airport (IND) to an unrecorded destination

Report a problem

Event

NTSB case
CHI93LA341
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
Charter & commuter
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 R182

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
N2623C
Onboard fatalities
Unknown
Route
From Indianapolis International Airport (IND), Indianapolis, INTo not recorded
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 135: Air Taxi & Commuter
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
In flight collision with terrain/water
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 › Gear extension, delayed

Approximate · Estimated position: the centre of St. Louis, MO, the place the record names. Not the accident site.

NTSB narrative

THE PILOT OF THE CARGO AIRPLANE STATED THE AIRPLANE BOUNCED DURING TOUCHDOWN AND WHEN THE AIRPLANE TOUCHED DOWN A SECOND TIME, THE MAIN LANDING GEAR COLLAPSED. THE PILOT STATED HE OBSERVED THE LEFT LANDING GEAR EXTENDING AND THE GREEN GEAR DOWNLIGHT ILLUMINATED WHEN HE LOWERED THE GEAR DURING THE APPROACH. DURING THE ON-SCENE INVESTIGATION THE LANDING GEAR WAS RETRACTED AND EXTENDED SEVERAL TIMES WITHOUT ANOMOLIES. THE LANDING GEAR DOWNLOCKS WERE INSPECTED FOR WEAR AND NONE WAS NOTED. THE DISTANCE BETWEEN TIRE TRACKS LEFT ON THE RUNWAY INDICATE THE GEAR WAS IN THE TRAIL POSITION. ACCORDING TO THE MANUFACTURER'S MAINTENCE MANUAL, ALL THREE LANDING GEAR LEGS MUST BE DOWN AND LOCKED BEFORE A GREEN GEAR DOWN LIGHT WILL ILLUMINATE.

Probable cause

the pilot's delay in lowering the landing gear prior to touchdown.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI93LA341
Event ID
20001211X13121
Case number
CHI93LA341
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1993-08-29.
  • API snapshot SHA-256: 7a4797a0dc0b3d806a7c1ffc6a70ef2fe34473c17d78b5c0d9c3456dc29a6c92; retrieved 2026-09-18T18:30:32.516Z.