ERA11CA187 · Piper PA-28-161
Piper PA-28-161 · Accident: hard landing
From Waterbury Oxford Airport (OXC) to Waterbury Oxford Airport (OXC)
Event
- NTSB case
- ERA11CA187
- 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
Piper PA-28-161
- Aircraft type
- Piper PA-28
- 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
- N2838D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Waterbury Oxford Airport (OXC), Oxford, CTTo Waterbury Oxford Airport (OXC), Oxford, 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
- 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
- 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
- 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 was practicing crosswind landings with his certified flight instructor (CFI) when they planned to perform a full stop landing on runway 36. The airplane touched down hard in a level attitude and the CFI moved his hand to the throttle to add engine power but was too late. After impacting the runway, the nose gear collapsed, and the airplane incurred substantial damage to the firewall. After reviewing a security video of the accident, the airport manager reported that the airplane did not flare prior to landing. A postaccident examination of the wreckage revealed that there were no mechanical anomalies with the airplane. The reported wind conditions at an the airport around the time of the accident were variable from 240 degrees to 310 degrees at 10 knots gusting to 17 knots.
Probable cause
The student pilot's inadequate landing flare and the certified flight instructor's inadequate remedial action, resulting in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA187
- Event ID
- 20110313X52310
- Case number
- ERA11CA187
- 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: 655cfef7de02f511c81fb4e81919dab907848eafecd8cf89dc7bdd554e0350b2; retrieved 2026-09-15T15:54:16.376Z.