# NTSB ERA14CA354: Cessna 172P, N97528, Hagerstown, MD, July 17, 2014 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 17, 2014, 15:00 local (19:00 UTC) - Place: Hagerstown, MD - Coordinates: 39.680385, -77.65084 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.6804&lon=-77.6508&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report September 2, 2014 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - NTSB case key (mKey): 89730 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA14CA354 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/89730/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=89730 - Page: https://openairdocs.org/ntsb/ERA14CA354 ## Probable cause The student pilot's improper landing flare. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [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) - [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) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Cessna 172P, 16 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072436), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) ## Analysis The student pilot was conducting her first solo flight, and stated that during the first landing, all three of the landing gear contacted the runway simultaneously, and the airplane began to porpoise. She aborted the landing and noted that the engine sounded "slightly rougher and much louder" during the climb-out. She also noted that the airplane "struggled" to climb to traffic pattern altitude. The second approach and landing was uneventful, and after disembarking the airplane, damage was noted to the propeller. Further examination of the airplane by a Federal Aviation Administration inspector revealed substantial damage to the engine firewall. The pilot reported there were no mechanical malfunctions or anomalies of the airplane that would have precluded normal operation. ## Factual narrative The student pilot was conducting her first solo flight, and stated that during the first landing, all three of the landing gear contacted the runway simultaneously, and the airplane began to porpoise. She aborted the landing and noted that the engine sounded "slightly rougher and much louder" during the climb-out. She also noted that the airplane "struggled" to climb to traffic pattern altitude. The second approach and landing was uneventful, and after disembarking the airplane, damage was noted to the propeller. Further examination of the airplane by a Federal Aviation Administration inspector revealed substantial damage to the engine firewall. The pilot reported there were no mechanical malfunctions or anomalies of the airplane that would have precluded normal operation. ## Aircraft - Registration: [N97528](https://openairdocs.org/aircraft/N97528), registered now, S/N 17276308, built 1985 (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: 17276308 - Year built: 1985 - Engines: LYCOMING 0-320 SERIES reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Civil Air Patrol Inc - Registered owner: Civil Air Patrol Inc - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, April 23, 2014, 4,822 hours before - Departed: HGR, Hagerstown, MD - Destination: HGR, Hagerstown, MD - Airport: HGR, Hagerstown Regional Airport, runway 27, 7,000 × 150 ft, asphalt - Equipment: Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 17; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; restraint: 3-point; flight hours: 12 total, 12 in this make and model, 0.2 as pilot in command, 12 in the last 90 days, 12 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 270° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 70 °F, dew point 54 °F - Altimeter: 30.07 inHg - Observed at: HGR ## 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 20140717011979A](https://openairdocs.org/incident/20140717011979A), Jul 17, 2014: Cessna 172P, Hagerstown, MD, Substantial damage. A/c N97528 landed at Hagerstown on runway 27, and incurred a prop strike during student pilot's first solo flight. The propeller sustained damage due to… ## Docket (3 files) The files NTSB released with the investigation on August 14, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=89730. 2.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40415139&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Student Pilot Statement (item 2, .PDF, 107 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40415138&FileExtension=.PDF&FileName=Student%20Pilot%20Statement-Master.PDF - Photo 1 – Damage to firewall (Courtesy of FAA) (item 3, .PDF, 122 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40415140&FileExtension=.PDF&FileName=Photo%201%20%E2%80%93%20Damage%20to%20firewall%20(Courtesy%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.