ERA10CA241 · Cessna 172P
Waco Transport Business Trust Cessna 172P · Accident: abnormal runway contact during landing
From Wurtsboro-Sullivan County Airport (N82) to Wurtsboro-Sullivan County Airport (N82)
Event
- NTSB case
- ERA10CA241
- 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
- 0
- 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
- Instrument 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
- N51231
- Operator
- Waco Transport Business Trust
- Onboard fatalities
- Unknown
- Route
- From Wurtsboro-Sullivan County Airport (N82), Wurtsboro, NYTo Wurtsboro-Sullivan County Airport (N82), Wurtsboro, NY
- 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
- Abnormal runway contact
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the student pilot, he departed from the airport and was performing supervised solo takeoffs and landings. During the first landing, the airplane impacted the runway with the nose landing gear first and bounced several times; he subsequently initiated a go-around and landed again uneventfully. The student pilot's flight instructor, who witnessed the event, stated that the accident was "a matter of judgment call and inexperience." While putting the airplane away, the student pilot and his flight instructor noticed damage to the nose landing gear and the propeller. An inspection performed by a Federal Aviation Administration inspector revealed damage to the firewall. No mechanical malfunctions or failures were reported by the student pilot and his flight instructor.
Probable cause
The student pilot's improper flare and recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA241
- Event ID
- 20100425X34040
- Case number
- ERA10CA241
- 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. 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: 6291de8d23d44371201bbb42b29ecac4b0758bca67b2b73c17eb3cff61ace8f6; retrieved 2026-09-15T13:54:23.011Z.