CEN24LA366 · Cessna 172M
Bishop Services Cessna 172M · Accident: landing area overshoot
From Hattiesburg Laurel Regional Airport (PIB) to University Oxford Airport (UOX)
Event
- NTSB case
- CEN24LA366
- 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
- Event fatalities
- Unknown
- 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 172M
- 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
- N73154
- Operator
- Bishop Services
- Onboard fatalities
- Unknown
- Route
- From Hattiesburg Laurel Regional Airport (PIB), Moselle, MSTo University Oxford Airport (UOX), Oxford, MS
- Aircraft age
- About 48 years (built 1976)
- 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
- 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
- Landing area overshoot
- 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
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during cruise flight, the airplane control yoke became hard to move, the pitch trim control wheel became loose, and the airplane lost electrical power. The pilot diverted to a nearby airport with a 3,000-ft long runway for a precautionary landing but performed a go-around because the airplane was too high. During the second approach for landing, the pilot placed the airplane into a slip to further reduce its altitude and landed about halfway down the runway at a speed of 83 knots with the wing flaps fully retracted. The pilot applied brakes to try to stop the airplane, but the airplane overran the departure end of the runway and nosed over in a grass field. The airplane sustained substantial damage to the left wing and the vertical stabilizer. Postaccident examination of the airplane revealed that the alternator power and ground terminals were not securely attached to the alternator, which would have resulted in an interruption of electrical power delivery to the electrical system and prevented the extension of the electrically operated wing flaps. Examination of the pitch control system revealed a separated pitch trim cable. There was no impingement of the pitch control system at the time of recovery and examination; however, one of the wires behind the instrument panel exhibited chafing indicative of interference with the flight control system’s cables and pulleys. The circumstances of the accident are consistent with excessive airspeed during the no-flap landing, which resulted in a runway overrun.
Probable cause
The excessive airplane speed during a no-flap landing, and the pilot’s failure to attain a proper touchdown point, which resulted in a runway overrun. Contributing to the accident was the interference of the instrument panel wiring with the flight control system.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA366
- Event ID
- 20240923195165
- Case number
- CEN24LA366
- 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, cause areas. 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: 2574048e6468cb2163e0faf10b59e3d7f34bbf8e64d0f38a50c0295555a51f7d; retrieved 2026-09-16T19:17:57.017Z.