# NTSB NYC08CA257: Cessna 172S, N331ME, Stevensville, MD, July 26, 2008 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: July 26, 2008, 09:30 local (13:30 UTC) - Place: Stevensville, MD - Coordinates: 38.976387, -76.329719 - Nearby events: https://openairdocs.org/map.md?lat=38.9764&lon=-76.3297&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: Minor injuries - Injuries: 1 minor, 1 uninjured - Status: Completed, report September 26, 2008 - Report: Approved by Office Director - Parties: FAA/FSDO - NTSB case key (mKey): 68524 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC08CA257 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/68524/pdf - Page: https://openairdocs.org/ntsb/NYC08CA257 ## Probable cause The flight instructor's inadequate remedial action following 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: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained; cases with it: [Cessna 172S, 99 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072439), [All aircraft, 1,287 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; cases with it: [Cessna 172S, 206 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072439), [All aircraft, 9,308 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Instructor/check pilot (probable cause); cases with it: [Cessna 172S, 32 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2072439), [All aircraft, 1,387 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: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cessna 172S, 49 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2072439), [All aircraft, 5,010 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172S, 117 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072439), [All aircraft, 10,154 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Landing-landing roll: Nose over/nose down](https://openairdocs.org/ntsb-events/096); cases with it: [Cessna 172S, 34 cases](https://openairdocs.org/ntsb-events/096/sequence.md?model=2072439), [All aircraft, 2,289 cases](https://openairdocs.org/ntsb-events/096/sequence.md) ## Analysis The certificated flight instructor and the student pilot were practicing crosswind takeoffs and landings with an 8 knot, 90-degree crosswind. During the second landing attempt, as the airplane crossed the runway threshold, the student reduced power "more abruptly" than he had on the previous landing. The airplane "bounced," and the flight instructor told the student to add power. The student then "took out the wind correction on the ailerons and tensed up." The flight instructor attempted to re-apply the left aileron control, and told the student "don't fight me." The student then added power while the flight instructor retracted the flaps 10 degrees, from the 20-degree setting. The flight instructor expected the student to increase the engine power to full for a go-around, as they had practiced in the previous lessons, but he did not and the airplane bounced a second time. The airplane was at the far right edge of the runway when the flight instructor assumed the flight controls and reduced the engine power to idle. The airplane continued off the right side of the runway, and onto a grass area, where it struck an embankment, and nosed over, resulting in substantial damage to the fuselage, wing spar, and firewall. ## Factual narrative According to the certificated flight instructor, he and the student pilot of the Cessna 172S were practicing crosswind takeoffs and landings with an 8 knot, 90-degree crosswind. During the second landing attempt, as the airplane crossed the runway threshold, the student reduced power "more abruptly" than he had on the previous landing. The airplane "bounced," and the flight instructor told the student to add power. The student then "took out the wind correction on the ailerons and tensed up." The flight instructor then attempted to re-apply the left aileron control, and told the student "don't fight me." The student then added power while the flight instructor retracted the flaps from the 10-degree setting. The flight instructor expected the student to increase the engine power to full for a go-around, but he did not and the airplane bounced a second time. The airplane was at the far right edge of the runway, when the flight instructor assumed the flight controls and reduced the engine power to idle. The airplane continued off the right side of the runway, and onto a grass area, where it struck an embankment, and nosed over, resulting in substantial damage to the fuselage, wing spar, and firewall. ## Aircraft - Registration: [N331ME](https://openairdocs.org/aircraft/N331ME), registered now, S/N 172S8464, built 2000 (OpenAirDocs) - Reported make and model: Cessna 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming O&VO-360 series](https://openairdocs.org/engine/lycoming-o-vo-360-series) (registry code 41514, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S8464 - Airframe hours: 3454 - Engines: Lycoming IO-360 reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Chesapeake ProFlight, Inc. - Registered owner: FWM Aviation, LLC. - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: 100 hour, May 1, 2008 - Departed: BWI, Baltimore, MD - Destination: W29, Stevensville, MD - Flight plan: VFR - Airport: W29, Bay Bridge Airport, runway 29, 2,903 × 60 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Flight instructor; age 35; injuries: minor; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; last flight review January 1, 2008; seat: right; flight hours: 510 total, 205 in this make and model, 429 as pilot in command, 164 in the last 90 days, 62 in the last 30 days - Student pilot; age 22; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; flight hours: 8 total, 8 in this make and model, 8 in the last 90 days, 8 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 190° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 64 °F - Altimeter: 30.03 inHg - Observed at: W29 ## 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 20080726843819A](https://openairdocs.org/incident/20080726843819A), Jul 26, 2008: Cessna 172S, Stevensville, MD, Substantial damage. (-23) The CFI and his student were practicing crosswind landings on runway 29 with an eight knot crosswind from the left (200 deg.). The aircraft bounced upon… 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.