# NTSB CEN17CA140: Cessna 172R, N51827, Cahokia, IL, February 23, 2017 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: February 23, 2017 - Place: Cahokia, IL - Coordinates: 38.570278, -90.154998 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.5703&lon=-90.1550&mi=10 - Phase of flight: [Unknown](https://openairdocs.org/ntsb-phases/990) (OpenAirDocs' grouping) - Defining event: [Unknown: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) - Highest injury: No injuries - Status: Completed, report June 7, 2017 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Federal Aviation Administration; STL FSDO - NTSB case key (mKey): 94925 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN17CA140 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/94925/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=94925 - Page: https://openairdocs.org/ntsb/CEN17CA140 ## Probable cause A hard landing for reasons that could not be determined based on the available evidence. ## 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) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Unknown: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) (defining event); cases with it: [Cessna 172R, 2 cases](https://openairdocs.org/ntsb-events/000/sequence.md?model=2072401), [All aircraft, 1,703 cases](https://openairdocs.org/ntsb-events/000/sequence.md) ## Analysis The airplane was parked on the operator's ramp when Federal Aviation Administration inspector(s), during a routine ramp inspection, found that the airplane had substantial damage to the firewall and structure aft of the firewall. Airplane maintenance records showed an entry stating that the damage was due to a suspected hard landing. The operator stated that the damage must have occurred between the airplane's 100-hour inspection on September 27 and an oil change performed on October 24, 2016. The operator's mechanic stated that the damage was found when the engine cowl was removed for the oil change. A review of airplane flight logs showed about 20 different people had flown the airplane over 48 flights between the time of the 100-hour inspection and the oil change. On October 8, 2016, a student pilot was performing touch and gos when the airplane bounced two or three times during the flight's final landing. The student pilot stated that, when she turned off the runway onto the taxiway, she noticed the airplane was not steering properly and reported to the air traffic control tower that she had some mechanical difficulty that required maintenance assistance. The student pilot's flight instructor and a company lineman responded and noticed that the airplane had a flat nosewheel tire. The lineman inflated the tire, and the student pilot and flight instructor taxied the airplane to the operator's maintenance facility. The flight instructor informed the operator's mechanic of the bounced landing and flat tire. The mechanic stated that he replaced the nose tire, performed a brief exterior walk-around visual inspection of the airplane, noting it appeared airworthy, and returned it to service. A hard landing inspection was not performed. Other than the bounced landing reported on October 8, 2016, no other concerns about the other flights were reported to the operator. ## Factual narrative The airplane was parked on the operator's ramp when Federal Aviation Administration Inspector(s), on a routine ramp inspection, found that the airplane had substantial damage to the firewall and structure aft of the firewall. Airplane maintenance records showed an entry stating that the damage was due to a suspected hard landing. The operator stated that the damage must have occurred between the airplane's 100-hour inspection and oil change performed September 27 and October 24, 2016, respectively. The operator's mechanic stated the damage was found when the engine cowl was removed for the oil change. A review of airplane flight logs showed approximately 20 different people had flown the airplane over 48 flights between the time of the 100-hour inspection and the oil change. On October 8, 2016, a student pilot was performing touch and go's when the airplane bounced 2 or 3 times during the flight's final landing. The student pilot stated that when she turned off the runway onto the taxiway, she noticed the airplane was not steering properly and reported to air traffic control tower that she had some mechanical difficulty that required maintenance assistance. The student pilot's flight instructor and a company lineman responded and noticed that the airplane had a flat nose wheel tire. The lineman inflated the tire, and the student pilot and flight instructor taxied the airplane to the operator's maintenance facility. The flight instructor informed the operator's mechanic of the bounced landing and flat tire. The mechanic stated he replaced the nose tire, performed a brief exterior walk-around visual inspection of the aircraft, noting it appeared airworthy and returned it to service. A hard landing inspection was not performed. Other than the bounced landing reported on October 8, 2016, there were no other operator concerns of the 48 separate flights conducted between inspections. ## Aircraft - Registration: [N51827](https://openairdocs.org/aircraft/N51827), registered now, S/N 17281108, built 2002 (OpenAirDocs) - Reported make and model: CESSNA 172R - Registry model: [Cessna 172R](https://openairdocs.org/model/cessna-172r) (registry code 2072401) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17281108 - Year built: 2002 - Engines: Lycoming IO-360-L2A 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Ideal Aviation - Registered owner: B D Aviation LLC - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: 100 hour, September 27, 2016 - Flight plan: Unknown - Airport: CPS, St Louis Downtown Airport - Equipment: Auto-pilot, Stall warning system ## Weather - Conditions: Not reported ## Other investigations on N51827 (1) 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. - [NTSB CHI07LA164](https://openairdocs.org/ntsb/CHI07LA164), May 7, 2007: Cessna 172R (N51827), Chesterfield, MO, substantial damage. Probable cause: Inadequate flare during landing. The induced oscillation, not performing a go-around, the pilot's lack of experience and the failure to perform remedial action were factors. ## Docket (2 files) The files NTSB released with the investigation on May 10, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=94925. 810 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 746 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40451249&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - FAA Inspector Statement (item 2, .PDF, 64 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40451250&FileExtension=.PDF&FileName=FAA%20Inspector%20Statement-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.