CHI82DA191 · Convair 240
Convair 240 · Accident: in flight encounter with weather on approach
From Buffalo, NY to Detroit, MI
Event
- NTSB case
- CHI82DA191
- 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
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Convair 240
- Aircraft type
- Convair 240
- 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
- N153PA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Buffalo, NYTo Detroit, MI
- 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 121: Air Carrier
- 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 · IFR final 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
- 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
- Copilot/second pilot › Raising of flaps, improper
- Pilot in command › Supervision, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE CAPTAIN STATED THAT DURING AN ILS APPROACH, HE SAW THE APPROACH LIGHTS ABOUT 3 MILES FROM THE TOUCHDOWN POINT. REPORTEDLY, THE PLANE WAS ON THE GLIDE SLOPE AND LOCALIZER AS HE CONTINUED ON FINAL APPROACH. AFTER PASSING MINUMUMS, THE AIRCRAFT WENT INTO A FOG LAYER. THE CAPTAIN LOST FORWARD VISIBILITY AND ELECTED TO G0-AROUND. DURING THE GO-AROUND, THE CAPTAIN MADE A SHALLOW LEFT TURN AND CALLED FOR APPROACH FLAPS. AS THE FLAPS RAISED, THE AIRCRAFT SETTLED AND THE MAIN GEAR CONTACTED THE GROUND. AT THAT TIME, THE CAPTAIN MOVED THE THROTTLES TO IDLE. WHILE ROLLING OUT IN AN AREA OF GRASS BETWEEN 2 RUNWAYS, THE NOSE GEAR COLLAPSED. DURING THE INVESTIGATION, THE FLAPS WERE FOUND AT A 10 DEGREE SETTING. THE CAPTAIN STATED THAT THE FLAPS SHOULD HAVE BEEN PLACED AT 16.5 DEGREES FOR THE GO-AROUND.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI82DA191
- Event ID
- 20020917X02937
- Case number
- CHI82DA191
- 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: 599acb8b92b6191c1828ec0f31a1424f4f0abb1e1e67fffce8667aca1d47c899; retrieved 2026-09-18T21:09:32.270Z.