FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14CA250 · Piper PA-28-140

21 May 2014 · Sussex, NJ, United States

Piper PA-28-140 · Accident: hard landing

From Linden Airport (LDJ) to Sussex Airport (FWN)

Report a problem

Event

NTSB case
ERA14CA250
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-140

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
N9592W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Linden Airport (LDJ), Linden, NJTo Sussex Airport (FWN), Sussex, NJ
Aircraft age
About 47 years (built 1967)
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 › 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 private pilot was landing on a 3,499-foot-long, asphalt runway. He reported that the airplane's final approach speed was "too fast" and upon landing, the airplane began to bounce. After the third bounce, the airplane landed hard which resulted in substantial damage to the nose landing gear and firewall. The pilot further reported he did not experience any preaccident malfunctions or failures that would have precluded normal operation, and that he should have aborted the landing after the first bounce. Winds reported at the airport, about the time of the accident, were variable at 7 knots.

Probable cause

The pilot's failure to maintain proper airspeed while on approach, and his subsequent failure to recover from a bounced landing, which resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14CA250
Event ID
20140522X84359
Case number
ERA14CA250
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: a1c151b71bb9a3b31365561bb01ee92be8b35530aaa1a9d33686a901b22fab7c; retrieved 2026-09-15T23:39:24.932Z.