# NTSB ERA15CA038: Cessna 172P, N97277, Miami, FL, October 30, 2014 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 30, 2014, 07:48 local (11:48 UTC) - Place: Miami, FL - Coordinates: 25.643054, -80.434448 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=25.6431&lon=-80.4344&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 - Injuries: 1 uninjured - Status: Completed, report December 15, 2014 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 90342 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA15CA038 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/90342/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=90342 - Page: https://openairdocs.org/ntsb/ERA15CA038 ## Probable cause The failure of the student pilot to achieve a proper touchdown during a touch-and-go landing resulting in a hard landing and substantial damage. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Landing gear system: nose/tail gear attach section](https://openairdocs.org/ntsb-findings/01023221): Aircraft › Aircraft systems · Capability exceeded; cases with it: [Cessna 172P, 1 case](https://openairdocs.org/ntsb-findings/01023221/cases.md?model=2072436), [All aircraft, 29 cases](https://openairdocs.org/ntsb-findings/01023221/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Student/instructed pilot (probable cause); cases with it: [Cessna 172P, 76 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072436), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172P, 38 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072436), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Student/instructed pilot (probable cause); cases with it: [Cessna 172P, 20 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2072436), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/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 172P, 39 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072436), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) ## Analysis The student pilot had performed three uneventful landings with his instructor on board; his certified flight instructor later stated that the student, "… performed way above the standards needed to show me he would be safe during solo flight." While flying solo for the first time, the student performed one uneventful touch-and-go landing and remained in the traffic pattern for runway 9R. With a calm wind, the student pilot reported that the approach was normal; however, the landing was harder than normal. He continued the takeoff roll for another touch-and-go landing but reported hearing a weird sound. He added power, and believe that was the moment when the nose landing gear tire deflated. He then felt a, "strange movement and I felt the nose falling." He reduced power to abort the takeoff and then heard and felt something touching the floor. After coming to rest he contacted the air traffic control tower and reported what occurred. Postaccident inspection of the airplane by several FAA inspectors revealed the wings, upper fuselage, cabin, tail, main landing gear, primary flight controls, engine, and engine mount were intact. The nose landing gear inner cylinder was pushed up through the upper housing, and the firewall was damaged on the left, right, and aft sides of the nose landing gear mount. The upper quadrant of the firewall also exhibited a seven inch buckle. Following recovery of the airplane, the engine was started and found to operate normally. The operator also reported that the cabin floor was bent. ## Factual narrative The student pilot had performed three uneventful landings with his instructor on board; his certified flight instructor later stated that the student, "… performed way above the standards needed to show me he would be safe during solo flight." While flying solo for the first time, the student performed one uneventful touch-and-go landing and remained in the traffic pattern for runway 9R. With a calm wind, the student pilot reported that the approach was normal; however, the landing was harder than normal. He continued the takeoff roll for another touch-and-go landing but reported hearing a weird sound. He added power, and believe that was the moment when the nose landing gear tire deflated. He then felt a, "strange movement and I felt the nose falling." He reduced power to abort the takeoff and then heard and felt something touching the floor. After coming to rest he contacted the air traffic control tower and reported what occurred.Postaccident inspection of the airplane by several FAA inspectors revealed the wings, upper fuselage, cabin, tail, main landing gear, primary flight controls, engine, and engine mount were intact. The nose landing gear inner cylinder was pushed up through the upper housing, and the firewall was damaged on the left, right, and aft sides of the nose landing gear mount. The upper quadrant of the firewall also exhibited a seven inch buckle. Following recovery of the airplane, the engine was started and found to operate normally. The operator also reported that the cabin floor was bent. ## Aircraft - Registration: [N97277](https://openairdocs.org/deregistered/N97277-2017-02-24), registration cancelled 2017-02-24, S/N 17276172, built 1984 (OpenAirDocs) - Reported make and model: CESSNA 172P - Registry model: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436) (OpenAirDocs) - Registry engine: [Continental I0-470 series](https://openairdocs.org/engine/continental-i0-470-series) (registry code 17027, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17276172 - Year built: 1984 - Airframe hours: 13239.4 - Engines: Lycoming O-320-D2J 150 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: ADF Airways - Registered owner: Elide Leasing Inc - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: 100 hour, October 22, 2014, 20 hours before - Departed: TMB, Miami, FL - Destination: TMB, Miami, FL - Airport: KTMB, Kendall-Tamiami Executive Airp, runway 9R, 5,999 × 1,500 ft, asphalt - Equipment: Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 18; injuries: none; student; medical: class 1, without waivers/limitations; seat: left; restraint: 3-point; flight hours: 51 total, 51 in this make and model, 0 as pilot in command, 51 in the last 90 days, 25 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Altimeter: 29.96 inHg - Observed at: TMB ## 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 20141030021859A](https://openairdocs.org/incident/20141030021859A), Oct 30, 2014: Cessna 172P, Kendall, FL, Substantial damage. Cessna 172P single engine airplane sustained substantial damage when it hard landed on its nose landing gear, on runway 9R during touch and go's at the… ## Other investigations on N97277 (2) 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 GAA16CA047](https://openairdocs.org/ntsb/GAA16CA047), Nov 9, 2015: Cessna 172M (N97277), Miami, FL, substantial damage. Probable cause: The student pilot's failure to maintain pitch control during the landing flare, which resulted in a hard landing. - [NTSB ATL96LA086](https://openairdocs.org/ntsb/ATL96LA086), May 6, 1996: Cessna 172 (N97277), Winston-Salem, NC, substantial damage. Probable cause: The pilot's improper use of the elevator in response to a bounced landing. ## Docket (7 files) The files NTSB released with the investigation on December 9, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=90342. 7.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40419814&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Weather Report and Record (item 2, .PDF, 78 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40419815&FileExtension=.PDF&FileName=Weather%20Report%20and%20Record-Master.PDF - FAA Inspector Statements (item 3, .PDF, 117 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40419816&FileExtension=.PDF&FileName=FAA%20Inspector%20Statements-Redacted.PDF - Postaccident Engine Run Results (item 4, .PDF, 116 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40419817&FileExtension=.PDF&FileName=Postaccident%20Engine%20Run%20Results-Redacted.PDF - Student Pilot Initial Statement (item 5, .PDF, 135 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40419818&FileExtension=.PDF&FileName=Student%20Pilot%20Initial%20Statement-Redacted.PDF - Photo 1 - Airplane Following Recovery (Photo Courtesy of FAA) (item 6, .PDF, 2.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40419819&FileExtension=.PDF&FileName=Photo%201%20-%20Airplane%20Following%20Recovery%20(Photo%20Courtesy%20of%20FAA)-Master.PDF - Photo 2 - Buckle to Firewall (Photo Courtesy of FAA) (item 7, .PDF, 2.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40419820&FileExtension=.PDF&FileName=Photo%202%20-%20Buckle%20to%20Firewall%20(Photo%20Courtesy%20of%20FAA)-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.