IAD04CA038 · Piper PA-28R-180
Stafford Flying Club Piper PA-28R-180 · Accident: hard landing
From Sanford Seacoast Regional Airport (SFM) to Seacoast Airfield (3B4)
Event
- NTSB case
- IAD04CA038
- 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-180
- 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
- N4631J
- Operator
- Stafford Flying Club
- Onboard fatalities
- Unknown
- Route
- From Sanford Seacoast Regional Airport (SFM), Sanford, METo Seacoast Airfield (3B4), Eliot, ME
- 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 › Level off, improper
- Pilot in command(cfi) › Supervision, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While turning to align with the runway during a simulated forced landing, the airplane overshot the runway, and the turn was continued to the right to come back to the landing surface. The flight instructor and the pilot each reported that about 6 feet above the runway, the airplane "stalled", "plummeted", and experienced a hard landing. The airplane shook during the landing roll, then veered right and departed the landing surface. The landing gear collapsed, the airplane came to rest, and the instructor and pilot egressed the airplane. When asked if they experienced any problems with the performance or handling of the airplane, each said no.
Probable cause
The pilot's failure to maintain airspeed above stall which resulted in a hard landing and collapse of the landing gear. Also causal was the flight instructor's inadequate supervision.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD04CA038
- Event ID
- 20040927X01492
- Case number
- IAD04CA038
- 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: 459607d5e3a722be5b1d9183f1bdb4d98699f8e3e1759b0f6e57e2bf73ea41c9; retrieved 2026-09-22T06:52:59.983Z.