# NTSB CEN14CA457: Cessna 172N, N737SY, Murphysboro, IL, July 16, 2014

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: July 16, 2014
- Place: Murphysboro, IL
- Coordinates: 37.778057, -89.251945 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=37.7781&lon=-89.2519&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092)
- Highest injury: No injuries
- Status: Completed, report May 13, 2015
- Report: Approved by Office Director
- NTSB office: Central Region
- NTSB case key (mKey): 89959
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN14CA457
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/89959/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=89959
- Page: https://openairdocs.org/ntsb/CEN14CA457

## Probable cause

A hard landing by person(s) unknown.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Not specified (probable cause); cases with it: [Cessna 172N, 29 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2072434), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cessna 172N, 46 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072434), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md)

## Analysis

According to a written statement from maintenance personnel, a pilot discovered the airplane's nose wheel at an "unusual angle" during a preflight inspection. The pilot reported the damage to the fixed based operator (FBO) who asked maintenance to examine the airplane. Examination of the airplane revealed damage to the nose wheel and underside of the fuselage aft of the main landing gear, and substantial damage to the rudder. The FBO contacted the certificated flight instructors and pilots of the three flights that occurred preceding the damage report. The first and third flights were airplane checkout flights with the flight instructor; the second flight was a personal flight conducted by a senior flight instructor. Written statements provided to the FBO from the two flight instructors of those flights failed to reveal who was responsible for the damage, when or where it occurred, or how it was caused. Also unknown, is why the flight instructors did not observe the damage prior to their respective flights.

## Factual narrative

According to a written statement from maintenance personnel, a pilot discovered the airplane's nose wheel at an "unusual angle" during a preflight inspection. The pilot reported the damage to the fixed based operator (FBO) who asked maintenance to examine the airplane. Examination of the airplane revealed damage to the nose wheel and underside of the fuselage aft of the main landing gear, and substantial damage to the rudder. The FBO contacted the certificated flight instructors and pilots of the three flights that occurred preceding the damage report. The first and third flights were airplane checkout flights with the flight instructor; the second flight was a personal flight conducted by a senior flight instructor. Written statements provided to the FBO from the two flight instructors of those flights failed to reveal who was responsible for the damage, when or where it occurred, or how it was caused. Also unknown, is why the flight instructors did not observe the damage prior to their respective flights.

## Aircraft

- Registration: [N737SY](https://openairdocs.org/deregistered/N737SY-2022-08-13), registration cancelled 2022-08-13, S/N 17269650, built 1977 (OpenAirDocs)
- Reported make and model: CESSNA 172N (N)
- Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17269650
- Year built: 1977
- Engines: LYCOMING 0-320 SERIES reciprocating
- Damage: Substantial damage
- Flight: Part 91
- Operator: Flightline
- Registered owner: Dunn William J
- Airworthiness certificate: Standard, Normal
- Destination: MDH, Murphysboro, IL
- Flight plan: Unknown
- Airport: MDH, Southern Illinois

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Other flight crew; medical: unknown, unknown; flight hours: 0 total, 0 in this make and model

## Weather

- Conditions: Not reported

## 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 20140716015799A](https://openairdocs.org/incident/20140716015799A), Jul 16, 2014: Cessna 172N, Murphysboro, IL, Substantial damage. Preflight inspection showed evidence of a hard landing with damage to the nose gear and firewall.

## Other investigations on N737SY (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 CEN22LA120](https://openairdocs.org/ntsb/CEN22LA120), Feb 12, 2022: Cessna 172N (N737SY), Murphysboro, IL, substantial damage. Probable cause: The pilot’s failure to maintain clearance from power lines during approach for landing.

## Docket (3 files)

The files NTSB released with the investigation on April 27, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=89959. 260 KB in all.

- Statement From Maintenance Personnel (item 1, .PDF, 39 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40425603&FileExtension=.PDF&FileName=Statement%20From%20Maintenance%20Personnel-Redacted.PDF
- Statement From Flight Instructor - Fischer (item 2, .PDF, 112 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40425604&FileExtension=.PDF&FileName=Statement%20From%20Flight%20Instructor%20-%20Fischer-Redacted.PDF
- Statement From Flight Instructor - Kampe (item 3, .PDF, 109 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40425605&FileExtension=.PDF&FileName=Statement%20From%20Flight%20Instructor%20-%20Kampe-Redacted.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.
