# NTSB ERA11CA408: Cessna 172S, N789EP, Cambridge, MD, July 1, 2011 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 1, 2011, 11:30 local (15:30 UTC) - Place: Cambridge, MD - Coordinates: 38.536945, -76.024719 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.5369&lon=-76.0247&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 October 17, 2011 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA Baltimore FSDO - NTSB case key (mKey): 81149 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA11CA408 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/81149/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=81149 - Page: https://openairdocs.org/ntsb/ERA11CA408 ## Probable cause The student pilot's improper recovery from a bounced landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172S, 21 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=2072439), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172S, 206 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072439), [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 172S, 77 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072439), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-landing roll: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Cessna 172S, 22 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=2072439), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Landing-landing roll: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Cessna 172S, 21 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=2072439), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) ## Analysis The student pilot stated that she was completing her first solo cross-country flight. She landed the airplane on its main landing gear but it bounced. She then decreased the pitch of the airplane's nose, resulting in the nosewheel touching down independently of the main landing gear. The airplane's nosewheel strut broke loose from its attachments and was driven into the engine compartment, which resulted in substantial damage to the firewall. She was able to keep the airplane on the runway during the entire landing sequence and roll. She taxied the airplane off of the runway and did not report any mechanical anomalies with the aircraft. ## Factual narrative The student pilot stated she was completing her first solo cross-country flight. She set up for runway 34 and entered the final approach at an airspeed of 70 knots. She landed the airplane on its main landing gear but it bounced. She then decreased the pitch of the airplane's nose, resulting in the nose wheel touching down independently of the main landing gear. The airplane's nose wheel strut broke loose from its attachments and was driven into the engine compartment, which resulted in substantial damage to the firewall. She was able to keep the airplane on the runway during the entire landing sequence and roll. She taxied the airplane off of the runway and did not report any mechanical anomalies with the aircraft. Weather conditions recorded at the airport about the time of the accident included winds from 340 degrees true at 7 knots. ## Aircraft - Registration: [N789EP](https://openairdocs.org/aircraft/N789EP), registered now, S/N 172S8135, built 1999 (OpenAirDocs) - Reported make and model: CESSNA 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming I0360 SER A&C](https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (registry code 41511, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S8135 - Airframe hours: 3900 - Engines: LYCOMING IO360 SER A&C 200 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Brett Aviation - Registered owner: Dream Flight LLC - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: 100 hour, May 11, 2011 - Departed: MTN, Baltimore, MD - Destination: CGE, Cambridge, MD - Airport: CGE, Cambridge - Dorchester Airport, runway 34, 4,477 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 32; injuries: none; student; medical: class 1, without waivers/limitations; seat: left; flight hours: 41 total, 41 in this make and model, 3 as pilot in command, 41 in the last 90 days ## Weather - Conditions: Visual (VMC), Day - Wind: 340° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 77 °F, dew point 55 °F - Altimeter: 30.02 inHg - Observed at: KCGE ## 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 20110701014019A](https://openairdocs.org/incident/20110701014019A), Jul 1, 2011: Cessna 172S, Cambridge, MD, Substantial damage. Pilot bounced aircraft on landing. On the second bounce the nose came down hard and the prop hit the runway. The firewall was damaged and the forward belly… ## Other investigations on N789EP (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 GAA18CA326](https://openairdocs.org/ntsb/GAA18CA326), May 26, 2018: Cessna 172 (N789EP), Westminster, MD, substantial damage. Probable cause: The pilot’s improper landing flare, which resulted in a hard landing. - [NTSB ERA10CA305](https://openairdocs.org/ntsb/ERA10CA305), Jun 4, 2010: Cessna 172S (N789EP), Baltimore, MD, substantial damage. Probable cause: The pilot’s improper flare, which resulted in a hard landing. Contributing to the accident was the pilot’s improper decision to land during a thunderstorm. ## Docket (4 files) The files NTSB released with the investigation on September 9, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=81149. 771 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 441 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351784&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - FAA Pilot Statement (item 2, .PDF, 172 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351328&FileExtension=.PDF&FileName=FAA%20Pilot%20Statement-Redacted.PDF - Cambridge-Dorchester (CGE) Meteorological Observations (item 3, .PDF, 71 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351310&FileExtension=.PDF&FileName=Cambridge-Dorchester%20(CGE)%20Meteorological%20Observations-Master.PDF - Photo 1 - View of Damage to Firewall (Courtesy of FAA) (item 4, .PDF, 86 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351320&FileExtension=.PDF&FileName=Photo%201%20-%20View%20of%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.