NYC01LA163 · Cessna 172P
Cessna 172P · Accident: loss of control in flight during landing
From Freeway Airport (W00) to Bay Bridge Airport (W29)
Event
- NTSB case
- NYC01LA163
- 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 172P
- 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
- N54576
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Freeway Airport (W00), Mitchellville, 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
- First occurrenceThe 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
- Pilot in command › Flare, improper
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While on final approach for the runway, the airplane was "above glide path and remained too high throughout final." With a view of ample runway ahead, the pilot "decided to continue with the landing rather than go around." The airplane touched down, bounced back into the air, and "ballooned excessively." The pilot added power to recover from the bounced landing, touched down a second time, and the airplane began to porpoise. The nose wheel tire then ruptured and the propeller struck the asphalt. According to the Federal Aviation Administration Airplane Flying Handbook, the proper technique for recovery from "excessive" "Floating During Roundout", and "Ballooning During Roundout," was "EXECUTE A GO-AROUND IMMEDIATELY."
Probable cause
The pilot's improper flare and his improper recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01LA163
- Event ID
- 20010706X01316
- Case number
- NYC01LA163
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: f44b63f45a2d61c5a1181584cd31db8cfe5a1eeb71b11b943ba772828b5f95a1; retrieved 2026-09-22T11:48:41.050Z.