NYC01LA219 · Cessna 172M
North American Aviation Cessna 172M · Accident: loss of control on ground/water during landing
From Danbury Municipal Airport (DXR) to Danbury Municipal Airport (DXR)
Event
- NTSB case
- NYC01LA219
- 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 172M
- 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
- N9869Q
- Operator
- North American Aviation
- Onboard fatalities
- Unknown
- Route
- From Danbury Municipal Airport (DXR), Danbury, CTTo Danbury Municipal Airport (DXR), Danbury, CT
- 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 on ground/water
- 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
- Flight/nav instruments, airspeed indicator › Inoperative
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the airspeed indicator was operative during the takeoff roll. However, after becoming airborne, it returned to zero, and stayed there. The pilot remained in the traffic pattern and returned for a landing. Full flaps were added prior to touchdown. Upon initial touchdown, the airplane bounced. The pilot added power, and when he removed the power, the airplane bounced again. The pilot reported that the airplane bounced at least twice prior to departing the right side of the runway. Witnesses reported it bounced five or six times. The nose landing gear tire was blown, the firewall was wrinkled, and the supporting structure behind the firewall was bent.
Probable cause
An inoperative airspeed indicator and the pilot's improper recovery from the bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01LA219
- Event ID
- 20010904X01855
- Case number
- NYC01LA219
- 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: a6f6a48553dcedb1c65e1ce624b853ff16b374a02d3f6b4fca8637ccb57ec982; retrieved 2026-09-22T11:37:12.085Z.