NYC04CA189 · Cessna 172P
Century Flight Academy Cessna 172P · Accident: hard landing
From Sullivan County International Airport (MSV) to Wilkes-Barre/Scranton International Airport (AVP)
Event
- NTSB case
- NYC04CA189
- 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
- N4599D
- Operator
- Century Flight Academy
- Onboard fatalities
- Unknown
- Route
- From Sullivan County International Airport (MSV), Monticello, NYTo Wilkes-Barre/Scranton International Airport (AVP), Wilkes-Barre, PA
- 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
- Hard landing
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot contacted air traffic control (ATC), and was instructed to enter a right downwind for runway 4, a 7,501-foot-long, 150-foot-wide, asphalt runway. Shortly thereafter, the airplane's radio's stopped working. The student pilot attempted to troubleshoot the problem, and was able to receive, but not transmit over the radio. He elected to land on runway 4, however, he overheard ATC clear another airplane to land, that was on a 5 mile final approach. The student pilot stated that he was "nervous" about the other airplane, turned a very early base leg, and approached "high and fast." The airplane contacted the runway hard, and began to bounce. It then departed the right side of the runway. Examination of the airplane, which included a radio check, did not reveal any discrepancies. A weather observation taken at the airport, about the time of the accident, included winds from 340 degrees at 8 knots.
Probable cause
The student pilot's improper flare and improper recover from a bounced landing. Factors in this accident were the crosswind condition and the partial failure of the airplane's transceiver, as reported by the pilot.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC04CA189
- Event ID
- 20040903X01349
- Case number
- NYC04CA189
- 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, 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: 554380124a0012deb61cded577911ed6022606e22973e4c5aaef7b9525e328e7; retrieved 2026-09-22T06:54:39.857Z.