# NTSB CEN14LA333: Cessna 172R, N468CM, Joplin, MO, July 1, 2014 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: July 1, 2014, 17:26 local (22:26 UTC) - Place: Joplin, MO - Coordinates: 37.151943, -94.498336 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.1519&lon=-94.4983&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report January 21, 2016 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Federal Aviation Administration - Kansas City FSDO - NTSB case key (mKey): 89586 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN14LA333 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/89586/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=89586 - Page: https://openairdocs.org/ntsb/CEN14LA333 ## Probable cause The partial loss of engine power for reasons that could not be determined because an operational test run of the engine did not reveal any anomalies that would have precluded normal operation. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Cessna 172R, 7 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=2072401), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) - [Object/animal/substance: runway/taxi/approach light](https://openairdocs.org/ntsb-findings/03022012): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Cessna 172R, 2 cases](https://openairdocs.org/ntsb-findings/03022012/cases.md?model=2072401), [All aircraft, 106 cases](https://openairdocs.org/ntsb-findings/03022012/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342) (defining event); cases with it: [Cessna 172R, 3 cases](https://openairdocs.org/ntsb-events/342/sequence.md?model=2072401), [All aircraft, 1,858 cases](https://openairdocs.org/ntsb-events/342/sequence.md) - [Landing: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 172R, 8 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=2072401), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172R, 39 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072401), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172R, 46 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072401), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot stated that the accident occurred as he was completing a touch-and-go landing following a cross-country flight. He reported that, after an uneventful landing and during the subsequent initial climb, the engine "grumbled" and began to "cut in and out." The pilot immediately told the airport tower controller that the airplane had an engine issue, reduced engine power, and fully extended the wing flaps for landing on the remaining runway. During the landing roll, the airplane overran the end of the runway before it collided with a light pole associated with the runway approach lighting system. Following the accident, the pilot was able to taxi the airplane back onto the runway, under normal engine power, before he shut down the engine on a nearby taxiway. A postaccident examination established that the fuel system contained about 42 gallons of aviation fuel that was evenly distributed between the two wing fuel tanks. The engine was started by following the normal checklist procedure, and it developed takeoff power during an operational test run. No hesitation or engine roughness was experienced during the operational test run, and the engine responded to corresponding throttle movements throughout the test run. Thus, the postaccident operational test run did not reveal any anomalies with the fuel-injected engine that would have prevented normal operation. The reason for the partial loss of engine power could not be determined. ## Factual narrative On July 1, 2014, about 1726 central daylight time, a Cessna model 172R airplane, N468CM, was substantially damaged during a forced landing at the Joplin Regional Airport (JLN), Joplin, Missouri. The private pilot was not injured. The airplane was registered to and operated by University of Central Missouri under the provisions of 14 Code of Federal Regulations Part 91 without a flight plan. Day visual meteorological conditions prevailed for the instructional cross-country flight that departed from Downtown Airport (3DW), Springfield, Missouri, about 1700.The pilot reported that he was cleared for the option landing on runway 31 (6,501 feet by 150 feet, asphalt) and that the prevailing wind was aligned with the runway heading at 11 knots. The pilot stated that he performed a touch-and-go landing. He reported that he made an uneventful landing and that shortly after the following takeoff, during initial climb, the engine "grumbled" and began to "cut in and out." The pilot immediately told the tower controller that the airplane had an engine issue, reduced engine power, and fully extended the wing flaps for a landing on the remaining runway. During the landing roll, the airplane overran the end of the runway before it collided with a light pole associated with the runway approach lighting system. Following the accident, the pilot was able to taxi back onto runway, under normal engine power, before he shut down the engine on a nearby taxiway. The right wing was substantially damaged during the on-ground collision with the light pole. A postaccident examination was completed by the airplane operator's chief pilot and the director of maintenance. Their examination established that the airplane fuel system contained about 42 gallons of 100 low-lead aviation fuel that was evenly distributed between the two wing fuel tanks. An external examination of the engine did not reveal any anomalies or fluid leaks. The oil quantity dip-stick established that the engine contained about 8 quarts of oil. The engine was started by following the normal checklist procedure, and then demonstrated the ability to develop takeoff power during an operational test run. No hesitation or engine roughness was experienced during the operational test run. The engine responded to corresponding throttle movements throughout the test run. A functional magneto check did not reveal any anomalies with engine operation. Following the operational test run, there were no fluid leaks observed on the engine exterior. The postaccident operational test run did not reveal any anomalies with the engine, a fuel-injected Lycoming model IO-360, that would have prevented normal operation. ## Aircraft - Registration: [N468CM](https://openairdocs.org/aircraft/N468CM), registered now, S/N 17280860, built 2000 (OpenAirDocs) - Reported make and model: CESSNA 172R - Registry model: [Cessna 172R](https://openairdocs.org/model/cessna-172r) (registry code 2072401) (OpenAirDocs) - Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17280860 - Year built: 2000 - Airframe hours: 6842.2 - Engines: Lycoming IO-360 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: University of Central Missouri - Registered owner: University of Central Missouri - Airworthiness certificate: Standard, Utility - Last inspection: AAIP, June 27, 2014, 6 hours before - Departed: 3DW, Springfield, MO - Destination: JLN, Joplin, MO - Flight plan: VFR - Airport: JLN, Joplin Regional Airport, runway 31, 6,501 × 150 ft, asphalt - Equipment: Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 20; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review April 23, 2014; seat: left; restraint: 3-point; flight hours: 135.3 total, 124 in this make and model, 82 as pilot in command, 28.7 in the last 90 days, 18.7 in the last 30 days, 3.7 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 270° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 84 °F, dew point 61 °F - Altimeter: 29.93 inHg - Observed at: JLN ## 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 20140701010849A](https://openairdocs.org/incident/20140701010849A), Jul 1, 2014: Cessna 172R, Joplin, MO, Substantial damage. Pilot was landing (touch and go) at kjln. On the first attempt, at approximately 100 feet AGL, the pilot stated that the engine began to "grumble/cut in and… ## Docket (2 files) The files NTSB released with the investigation on December 7, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=89586. 948 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 898 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434590&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Engine Examination and Operational Test Run Report (item 2, .PDF, 50 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434591&FileExtension=.PDF&FileName=Engine%20Examination%20and%20Operational%20Test%20Run%20Report-Master.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.