ATL82FKQ10 · Piper PA-23-250
Piper PA-23-250 · Accident: in flight collision with object on approach
From Jackson, MS to McComb, MS
Event
- NTSB case
- ATL82FKQ10
- 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
- 1 · 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
- Instrument Meteorological Cond
Piper PA-23-250
- Aircraft type
- Piper PA-23
- 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
- N6242Y
- Operator
- Thomas M. Casey · private individual
- Onboard fatalities
- Unknown
- Route
- From Jackson, MSTo McComb, MS
- 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 · 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 collision with object
- 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
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Minimum descent altitude, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
BEFORE TAKING OFF FROM JACKSON, MS, THE PILOT RECEIVED A WEATHER BRIEFING BY RADIO AND FILED AN IFR FLIGHT PLAN TO MCCOMB, MS. DURING ARRIVAL AT MCCOMB, THE WEATHER WAS IFR WITH AN INDEFINITELY OBSCURED CEILING AT ZERO FT, VISIBILITY 1/2 MILE IN FOG, WIND 160 DEGREES AT 7 KNOTS. DURING AN ILS LOCALIZER APPROACH, THE AIRCRAFT MADE CONTACT WITH TREES ABOUT 2900 FT FROM THE APPROACH END OF THE RUNWAY. THE TREES WERE ABOUT 50 TO 60 FT TALL AND THE GROUND LEVEL WAS APPROXIMATELY 400 FT MSL. THE MINIMUM DESCENT ALTITUDE (MDA) FOR THE APPROACH WAS 800 FT MSL. THE INITIAL IMPACT POINT WAS ALONG THE CENTERLINE OF THE APPROACH TO RUNWAY 15. AFTER THE INITIAL IMPACT, THE AIRCRAFT FLEW ABOUT 630 FT AND THEN CRASHED IN A WOODED AREA ABOUT 400 FT LEFT OF THE CENTERLINE OF THE APPROACH. AN INVESTIGATION REVEALED NO INDICATION OF A MALFUNCTION OR FAILURE OF THE ENGINES.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82FKQ10
- Event ID
- 20020917X01751
- Case number
- ATL82FKQ10
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 16262b71ad4ba8643d4cc49adb90681a24b8c99fd4036b9a38d137941b1d1156; retrieved 2026-09-21T08:38:58.624Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: destination. The narrative states "BEFORE TAKING OFF FROM JACKSON, MS, THE PILOT RECEIVED A WEATHER BRIEFING BY RADIO AND FILED AN IFR FLIGHT PLAN TO MCCOMB, MS" and the airplane crashed on the ILS approach there; the record showed Pontiac, MI.