ERA11CA052 · Piper PA-28R-200
Seniram Air Piper PA-28R-200 · Accident: hard landing
From Lee Airport (ANP) to Cambridge Dorchester Airport (KCGE)
Event
- NTSB case
- ERA11CA052
- 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-28R-200
- 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
- N56101
- Operator
- Seniram Air
- Onboard fatalities
- Unknown
- Route
- From Lee Airport (ANP), Edgewater, MDTo Cambridge Dorchester Airport (KCGE), Cambridge, 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
- 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 certificated flight instructor (CFI), the purpose of the flight was for him to give instruction to the commercial pilot, who was working toward his flight instructor certificate. At the destination airport, the CFI demonstrated a power-off 180-degree approach to landing. The commercial pilot successfully demonstrated four of the same approaches and began the fifth approach. During the landing, the commercial pilot misjudged the landing flare which resulted in a firm touchdown. The CFI attempted to maneuver the airplane in a nose-high configuration, but was unable to apply enough back pressure to prevent a firm touchdown, due to the force being applied by the commercial pilot. Upon touchdown, the CFI executed a go-around maneuver and then flew to the home airport where they landed without incident. Postaccident examination of the airplane revealed substantial damage to the outboard and inboard ribs. The flight instructor stated that there were no mechanical malfunctions with the airplane prior to the hard landing.
Probable cause
The commercial pilot’s inadequate flare during landing and the certificated flight instructor's delayed remedial action, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA052
- Event ID
- 20101110X21415
- Case number
- ERA11CA052
- 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: 7ba7919b9efe932b4f241ff03d7f1b1a9af6e529e0490bd180f43905f16c51c1; retrieved 2026-09-15T15:33:13.841Z.