NYC08CA303 · Cessna 172
Cessna 172 · Accident: abnormal runway contact during landing
From Franklinton Airport (2R7) to James H Easom Field (M23)
Event
- NTSB case
- NYC08CA303
- 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
- Unknown
- 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 172
- Aircraft type
- Cessna 172
- 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
- N6478E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Franklinton Airport (2R7), Franklinton, LATo James H Easom Field (M23), Newton, 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
- Landing · flare/touchdown
- Defining eventThe 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
- Abnormal runway contact
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot of the Cessna 172, the purpose of the cross-country flight was to move the airplane away from the potential path of a hurricane. While on the final leg of the approach, the airplane was configured with "30 degrees of flaps, the descent rate and airspeed were normal." While in the flare, the right main landing gear and right wingtip impacted the runway, damaging the wing spar. Subsequently, the nose wheel collapsed damaging the firewall, and the airplane skidded approximately 100 feet down runway 31. The winds reported about the time of the accident, approximately 22 miles to the east, were 030 degrees at 6 knots, with no wind gusts. The pilot reported that there were no mechanical malfunctions of the airplane.
Probable cause
The pilot's failure to maintain aircraft control while landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC08CA303
- Event ID
- 20081003X17826
- Case number
- NYC08CA303
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 2e514637a8d3d07a348d0d3c08c44b0908cd13030d85c74cb956574f16af2f0e; retrieved 2026-09-15T10:18:41.148Z.