NTSB CAROL · Event
Event CEN17CA140
Registry · N51827
FAA Aircraft Registry record.
Make / Model
CESSNA 172R
Year of manufacture
2002 · 15 years old at event
Engine
LYCOMING IO-360-L2A (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
20020415
ADS-B equipped
Yes — Mode-S A681E5
Registrant of record
B D AVIATION LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
A hard landing for reasons that could not be determined based on the available evidence.
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. 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Not determined-Not determined-(general)-(general)-Unknown/Not determined - C
Verbatim from NTSB's published report. Source file
NTSB_2017_CEN17CA140.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗