# NTSB DFW06CA008: Cessna 172P, N53795, Hitchcock, TX, October 17, 2005 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: October 17, 2005, 17:30 local (22:30 UTC) - Place: Hitchcock, TX - Coordinates: 29.36, -95.009719 - Nearby events: https://openairdocs.org/map.md?lat=29.3600&lon=-95.0097&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 1 minor, 3 uninjured - Status: Completed, report February 28, 2006 - Report: Approved by Office Director - NTSB case key (mKey): 62675 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=DFW06CA008 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/62675/pdf - Page: https://openairdocs.org/ntsb/DFW06CA008 ## Probable cause A loss of engine power due to a cracked cylinder. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of engine power(partial) - mech failure/malf, cruise - normal - engine assembly,cylinder - cracked (cause) - Forced landing, emergency descent/landing - On ground/water collision with object, emergency landing - object - hangar/airport building ## Analysis The 200-hour private pilot was conducting a local sightseeing flight. Approximately twenty-minutes after departing, the pilot reported hearing a loud bang and the engine began to run rough and lose power. The pilot located a private airport in close range and flew directly to it under partial power. Since he was high, the pilot decided to make a circular pattern to lose altitude. When he lined up with the runway, the airplane was still too high to land and the pilot elected to use full flaps and a slip to lose altitude. The pilot realized he was going to overshoot the runway and he pulled-up and added full power. The engine continued to run rough and the airplane was still losing airspeed and altitude, so the pilot decided to make another approach from the opposite direction, approaching from about 25 degrees to the right of the runway. Full flaps and a steep approach were used to lose altitude and the airplane touched down approximately two-thirds of the way down the 2,700 foot turf runway. After touching down, the pilot applied both brakes and the airplane skidded to the right, causing the right wing to come into contact with a hangar. The airplane nosed-over and come to rest in the upright position. Examination of the engine revealed a crack at the number one cylinder. ## Factual narrative The 200-hour pilot was conducting a local sightseeing flight. Approximately twenty-minutes after departing, the pilot reported hearing a loud bang and the engine began to run rough and lose power. The pilot located a private airport in close range and flew directly to it under partial power. Since he was high, the pilot elected to make a circular pattern to lose altitude. When he lined up with the runway, the airplane was still too high to land and the pilot elected to use full flaps and a slip to lose altitude. The pilot realized he was going to overshoot the runway and he pulled-up and added full power. The engine continued to run rough and the airplane was still losing airspeed and altitude, so the pilot decided to make another approach from the opposite direction, approaching from about 25 degrees to the right of the runway. Full flaps and a steep approach were used to lose altitude and the airplane touched down approximately two-thirds of the way down the 2,700 foot turf runway. The pilot applied both brakes and the airplane skidded to the right, causing the right wing to come into contact with a hangar. The airplane nosed-over coming to rest in the upright position. Examination of the airplane's engine revealed a crack at the number one cylinder. ## Aircraft - Registration: [N53795](https://openairdocs.org/deregistered/N53795-2013-01-30), registration cancelled 2013-01-30, S/N 17274817, built 1981 (OpenAirDocs) - Reported make and model: Cessna 172P - Registry model: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17274817 - Airframe hours: 18844 - Engines: Lycoming O-320 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: King Flight Service LLC - Registered owner: King Flight Service LLC - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, October 1, 2005 - Departed: T41, La Porte, TX - Airport: 37TE, Johnnie Volk Field Airport, runway 16, 2,700 × 60 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 36; injuries: none; private; airplane ratings: single-engine land; medical: class 3; last flight review February 1, 2004; seat: left; flight hours: 200 total, 175 in this make and model, 150 as pilot in command ## Weather - Conditions: Visual (VMC), Day - Wind: 160° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 86 °F, dew point 75 °F - Altimeter: 29.95 inHg - Observed at: GLS, 17 nm away ## 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 20051017026819A](https://openairdocs.org/incident/20051017026819A), Oct 17, 2005: Cessna 172P, Hitchcock, TX, Substantial damage. (-23) Pilot reported he heard a loud "bang" and the engine started to run rough, clanking and losing power and noticed a strong fuel odor. ## Other investigations on N53795 (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 FTW97LA247](https://openairdocs.org/ntsb/FTW97LA247), Jun 28, 1997: Cessna 172P (N53795), Fort Worth, TX, substantial damage. Probable cause: improper planning/decision by the flight instructor (CFI), which resulted in his inadvertent encounter with jet blast from a twin jet transport airplane. 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.