NYC94LA032 · Piper PA-28-140
Piper PA-28-140 · Accident: airframe, component or system failure en route
From Knox County Regional Airport (RKD) to an unrecorded destination
Event
- NTSB case
- NYC94LA032
- 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
- 0
- 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
- N55719
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Knox County Regional Airport (RKD), Rockland, METo not recorded
- 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
- En route · climb to cruise
- 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
- Airframe, component or system failure
- 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 › Airspeed, excessive
- Pilot in command › Altitude, excessive
Approximate · Estimated position: the centre of North Haven, ME, the place the record names. Not the accident site.
NTSB narrative
THE PILOT HEARD A NOISE FROM THE ENGINE WHICH HE DESCRIBED AS, 'VERY LOUD AND PERSISTENT RATTLE WITH SOME ATTENDING VIBRATION.' HE SET UP FOR A PRECAUTIONARY LANDING; HOWEVER, HE SAID HE WAS HIGH AND FAST AND TOUCHED DOWN OVER HALF WAY DOWN THE 2000 FOOT LONG RUNWAY WITH WET GRASS. THE PILOT WAS UNABLE TO STOP THE AIRPLANE ON THE REMAINING RUNWAY AND STEERED THE AIRPLANE OFF THE LEFT SIDE OF THE RUNWAY WHERE IT WENT DOWN AN EMBANKMENT AND STOPPED. POST ACCIDENT INVESTIGATION FOUND THE EXHAUST STACK ON THE NUMBER ONE CYLINDER HAD BROKEN AT THE MOUNTING FLANGE.
Probable cause
The pilot's use of excessive speed and altitude during the approach which resulted in a landing overrun of the runway. Factors were a precautionary landing and a ravine.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC94LA032
- Event ID
- 20001211X13908
- Case number
- NYC94LA032
- 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. 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: e1aed23453ac60d65235bf6de82b1ab02f080f51d6431f1d5caa07312487fe2a; retrieved 2026-09-23T01:26:48.986Z.