NYC08CA257 · Cessna 172S
Chesapeake Proflight Cessna 172S · Accident: loss of control in flight during landing
From Baltimore/Washington International Thurgood Marshall Airport (BWI) to Bay Bridge Airport (W29)
Event
- NTSB case
- NYC08CA257
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172S
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N331ME
- Operator
- Chesapeake ProFlight
- Onboard fatalities
- Unknown
- Route
- From Baltimore/Washington International Thurgood Marshall Airport (BWI), Baltimore, MDTo Bay Bridge Airport (W29), Stevensville, MD
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
The flight instructor's inadequate remedial action following the student pilot's improper recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC08CA257
- Event ID
- 20080829X01355
- Case number
- NYC08CA257
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 0606bca0449e37f05382e692ac64d8144e111f6e8097b13a38af6ad918b15e66; retrieved 2026-09-15T10:07:59.373Z.