# NTSB CEN24LA366: Cessna 172M, N73154, Ackerman, MS, September 20, 2024 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 3 · Limited · Final report - Date: September 20, 2024, 15:48 local (20:48 UTC) - Place: Ackerman, MS - Coordinates: 33.303458, -89.2284 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.3035&lon=-89.2284&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Central Region - Parties: Textron Aviation, Federal Aviation Administration, Mississippi FSDO - NTSB case key (mKey): 195165 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN24LA366 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/195165/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=195165 - Page: https://openairdocs.org/ntsb/CEN24LA366 ## 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Not specified (probable cause); cases with it: [Cessna 172M, 24 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=2072418), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md) - [Aircraft capability: landing distance](https://openairdocs.org/ntsb-findings/01061030): Aircraft › Aircraft oper/perf/capability · Capability exceeded (probable cause); cases with it: [Cessna 172M, 1 case](https://openairdocs.org/ntsb-findings/01061030/cases.md?model=2072418), [All aircraft, 68 cases](https://openairdocs.org/ntsb-findings/01061030/cases.md) - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172M, 19 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2072418), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Electrical power system: electrical pwr sys wiring](https://openairdocs.org/ntsb-findings/01022497): Aircraft › Aircraft systems · Damaged/degraded (probable cause); cases with it: [Cessna 172M, 1 case](https://openairdocs.org/ntsb-findings/01022497/cases.md?model=2072418), [All aircraft, 44 cases](https://openairdocs.org/ntsb-findings/01022497/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-cruise: Electrical system malf/failure](https://openairdocs.org/ntsb-events/332); cases with it: [Cessna 172M, 1 case](https://openairdocs.org/ntsb-events/332/sequence.md?model=2072418), [All aircraft, 182 cases](https://openairdocs.org/ntsb-events/332/sequence.md) - [Enroute-cruise: Flight control sys malf/fail](https://openairdocs.org/ntsb-events/333); cases with it: [Cessna 172M, 3 cases](https://openairdocs.org/ntsb-events/333/sequence.md?model=2072418), [All aircraft, 410 cases](https://openairdocs.org/ntsb-events/333/sequence.md) - [Emergency descent: Flight control sys malf/fail](https://openairdocs.org/ntsb-events/333); cases with it: [Cessna 172M, 3 cases](https://openairdocs.org/ntsb-events/333/sequence.md?model=2072418), [All aircraft, 410 cases](https://openairdocs.org/ntsb-events/333/sequence.md) - [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380) (defining event); cases with it: [Cessna 172M, 4 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=2072418), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) ## Analysis 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. ## Factual narrative On September 20, 2024, at 1548 central daylight time, a Cessna 172M, N73154, was substantially damaged when it was involved in an accident near Ackerman, Mississippi. The private pilot and two passengers were uninjured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot rented the airplane for a cross-country flight to the destination airport. During the flight, the control yoke became hard to move, and the airplane lost electrical power. The pilot reported that the yoke could only be moved forward and aft about one half inch. The pilot also stated that the pitch trim wheel became loose and moved without resistance. The pilot diverted to Ackerman Choctaw County Airport (9M4), Ackerman, Mississippi, and circled the airport with the engine power at idle to reduce the airplane’s altitude. After circling the airport twice, the pilot attempted a landing on runway 19 (3,000 ft by 75 ft, with dry asphalt), but the airplane was too high to land. The pilot performed a go-around and circled the airport a third time before attempting a second landing. During the second approach for landing, the pilot placed the airplane into a slip to further reduce its altitude and landed the airplane about halfway down the runway at a speed of 83 knots with the wing flaps fully retracted. The pilot said the wing flaps were retracted due a lack of electrical power. 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 that included damage to the left wing and vertical stabilizer. During the recovery of the airplane from the accident site, there was no control interference when the elevator was moved, with full travel, to the upper and lower control stops. Recovery personnel moved the elevator in both directions and a corresponding movement of the left control yoke was present while the airplane was inverted. When the airplane was placed into an upright position, the elevator was again moved and there was about 6 inches of free play before the left control yoke would move. The fuselage had longitudinal deformation from accident impact forces, which reduced the supportive length of the elevator control cable. Postaccident examination of the airplane flight control system revealed that the elevator trim control cable was found separated in the area underneath the cockpit seats. The elevator trim cable separation exhibited rust. Examination of the elevator control cable did not display separation, distortion, fraying, localized wear, or asymmetric wear. The elevator flight control cable pulleys did not display abnormal wear features and rotated freely. The instrument panel wiring near the control column had excess length and wiring that was within ½ inch of the flight control cables and pulleys. One of the wires near a pulley of the control column exhibited chaffing. The autopilot pitch servoclutch was not engaged and testing of the servo revealed that it met test specifications. Testing of the autopilot disconnect switch revealed normal operation. Examination of the electrical system revealed the alternator had power and the ground wires that were frayed were covered with electrical tape. One terminal fell off the alternator when it was disconnected from the alternator during the examination. Testing and examination of the alternator revealed the alternator case bolts were automotive bolts due to their greater length than the prescribed aviation bolts. The alternator brushes were copper, which was consistent with automotive brushes rather than silver aviation brushes. The alternator ran on a test bench with no anomalies that would have precluded normal operation. The pilot reported that she had received her pilot certificate in 1997 and returned to flying in 2020 and had flown with instructors to relearn how to fly. She reported that the owner provided her a checkout in the airplane and had last flown 12 days before the accident flight. She had texted the owner several days before the accident flight asking the owner the model of GPS and autopilot and watched YouTube videos on how to operate the Garmin 650 and to refresh her memory on the autopilot and avionics. ## Aircraft - Registration: [N73154](https://openairdocs.org/aircraft/N73154), registered now, S/N 17267293, built 1976 (OpenAirDocs) - Reported make and model: CESSNA 172M - Registry model: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17267293 - Year built: 1976 - Airframe hours: 10360 - Engines: Lycoming O-320-E2D 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Bishop Services LLC - Registered owner: Bishop Services LLC - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, August 7, 2024 - Departed: PIB, Moselle, MS - Destination: UOX, Oxford, MS - Flight plan: VFR - Airport: 9M4, Ackerman Choctaw County, runway 19, 3,000 × 75 ft, asphalt - Equipment: Electronic multifunction display, Electronic primary flight display, Onboard weather, Satellite tracking device, Electronic flight bag or handheld device, Stall warning system, ADS-B, Auto-pilot ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 47; injuries: none; private; airplane ratings: single-engine land; medical: basicmed, with waivers/limitations; last flight review December 17, 2023; seat: left; restraint: 3-point; flight hours: 148 total, 68 in this make and model, 90 as pilot in command, 9 in the last 90 days, 8 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 88 °F, dew point 68 °F - Altimeter: 29.91 inHg - Observed at: LMS, 13 nm away - METAR: KLMS 202135Z AUTO 00000KT 10SM CLR 31/20 A2991 RMK AO2 ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20240920012819A](https://openairdocs.org/incident/20240920012819A), Sep 20, 2024: Cessna 172M, Ackerman, MS, Substantial damage. [privacy data omitted], C172, declared an Emergency due to electrical failure and flight Control issues. Aircraft landed runway 1, Overran the runway, and came… ## Docket (15 files) The files NTSB released with the investigation on April 1, 2025, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=195165. 58.2 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 10 pages, 8.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17717140&FileExtension=pdf&FileName=6120%20Master_Redacted-Rel.pdf - Memorandum for record a�� record of conversation with pilot (item 2, PDF, 4 pages, 80 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18376480&FileExtension=pdf&FileName=Record%20of%20Conversation%20ver2-Rel.pdf - Flight track plot of jpi and ADS-B (item 3, KMZ, 176 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18358333&FileExtension=kmz&FileName=CEN24LA366%20-%20Ackerman,%20MS%20-%20ADS-B%20Data%20%26%20JPI%20GPS%20Data-Rel.kmz - Email from the pilot regarding touchdown speed (item 4, PDF, 1 page, 118 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18345240&FileExtension=pdf&FileName=Email%20from%20pilot%20regarding%20touchdown%20speed_Redacted-Rel.pdf - Memorandum for record a�� aircraft examination (item 5, PDF, 5 pages, 776 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18369715&FileExtension=pdf&FileName=MOR%20Exam-Rel.pdf - Memorandum for record a�� autopilot pitch servo testing (item 6, PDF, 1 page, 64 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18344659&FileExtension=pdf&FileName=MOR%20Thom%20Duncan%20Avionics-Rel.pdf - Memorandum for record a�� record of conversation regarding alternator (item 7, PDF, 1 page, 63 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18343366&FileExtension=pdf&FileName=MOR%20RLB%20Accesory-Rel.pdf - Memorandum for record a�� autopilot checklist(s) in N73154 (item 8, PDF, 1 page, 63 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18345325&FileExtension=pdf&FileName=MOR%20Autopilot%20Checklist(s)%20in%20N73154-Rel.pdf - Memorandum for record a�� autopilot disconnect switch examination (item 9, PDF, 1 page, 63 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18361429&FileExtension=pdf&FileName=MOR%20Autopilot%20Disconnect%20Switch%20Testing-Rel.pdf - Memorandum for record a�� brake system examination (item 10, PDF, 1 page, 63 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18345343&FileExtension=pdf&FileName=MOR%20Brake%20System%20Examination-Rel.pdf - Jpi download (item 11, CSV, 151 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18344434&FileExtension=csv&FileName=N73154%20JPI%20Data-Rel.csv - Maintenance records - airframe (item 12, PDF, 58 pages, 7.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18377193&FileExtension=pdf&FileName=Airframe%20Log%20Master_Redacted-Rel.pdf - Maintenance records - engine (item 13, PDF, 19 pages, 39.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18376490&FileExtension=pdf&FileName=Engine%20Logs_Redacted-Rel.pdf - Photos (item 14, PDF, 2 pages, 386 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18376677&FileExtension=pdf&FileName=Photo%20Template-Rel.pdf - Statement of party representatives to NTSB investigation (item 15, PDF, 1 page, 238 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18377944&FileExtension=pdf&FileName=Party%20Statement_Redacted-Rel.pdf From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.