ERA09CA484 · Piper PA-34 200T
Coastal Empire Flight Training Piper PA-34 200T · Accident: abnormal runway contact during landing
From Savannah Hilton Head International Airport (SAV) to Savannah Hilton Head International Airport (SAV)
Event
- NTSB case
- ERA09CA484
- 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-34 200T
- Aircraft type
- Piper PA-34
- 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
- N47611
- Operator
- Coastal Empire Flight Training
- Onboard fatalities
- Unknown
- Route
- From Savannah Hilton Head International Airport (SAV), Savannah, GATo Savannah Hilton Head International Airport (SAV), Savannah, GA
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor and student pilot were returning to the airport for landing after practicing maneuvers. The student pilot was flying the airplane and after a normal approach, just prior to touchdown on the runway, he abruptly pulled back on the control yoke. The airplane climbed approximately 10 feet as the flight instructor assumed control and pushed the control yoke forward. The airplane subsequently landed hard, which resulted in damage to the nose gear, the right engine propeller, and the nose cone structure at the base of the windshield. The flight instructor further stated that he did not experience any flight control malfunctions and weather was not a factor during the accident.
Probable cause
The student pilot's failure to maintain pitch control during landing and the flight instructor's delayed remedial action, resulting in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA484
- Event ID
- 20090827X83825
- Case number
- ERA09CA484
- 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, 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: edee48eaa5d7bcd2f4fe3af1b5b349fa2e2e7173668698af3dff45c12f38d3f6; retrieved 2026-09-15T12:51:24.715Z.