FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC95LA183 · Beech C23

7 Aug 1995 · Dublin, NH, United States

Beech C23 · Accident: total loss of engine power (mechanical failure) en route

From Beverly Regional Airport (BVY) to Dillant Hopkins Airport (EEN)

Report a problem

Event

NTSB case
NYC95LA183
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

Beech C23

Aircraft type
Beechcraft 23
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
N9310S
Operator
James D. Gregory · private individual
Onboard fatalities
Unknown
Route
From Beverly Regional Airport (BVY), Beverly, MATo Dillant Hopkins Airport (EEN), Keene, NH
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 · 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
Total loss of engine power (mechanical 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

  • Unknown › Maintenance, overhaul, improper

Approximate · Estimated position: the centre of Dublin, NH, the place the record names. Not the accident site.

NTSB narrative

THE PILOT WAS CRUISING AT 4500 FEET WHEN HE OBSERVED A LOW OIL PRESSURE INDICATION FOLLOWED BY A TOTAL LOSS OF ENGINE POWER. THE PILOT PERFORMED A FORCED LANDING ON AN OPEN FIELD, DURING WHICH THE NOSE GEAR COLLAPSED, AND THE FIREWALL BUCKLED. THE FAA INSPECTOR STATED THAT ALL PISTON PINS WERE REUSED AT LAST OVERHAUL, 121 HOURS PRIOR TO THE ACCIDENT. DURING POSTACCIDENT EXAMINATION, ALL PISTON PINS WERE FOUND TO BE BELOW SERVICE LIMITS. ADDITIONALLY, '...THE ENGINE FAILURE RESULTED FROM METAL PARTICLES GENERATED BY THE LOOSE FITTING PISTON PIN PLUGS, CAUSING PROGRESSIVE CONTAMINATION OF THE ENGINE LUBRICATION SYSTEM.'

Probable cause

THE LOSS OF ENGINE POWER DUE TO IMPROPER MAJOR OVERHAUL OF THE ENGINE BY THE REUSE OF WORN PISTON PINS. THE ROUGH/ UNEVEN TERRAIN IN THE EMERGENCY LANDING AREA WAS A FACTOR.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC95LA183
Event ID
20001207X04346
Case number
NYC95LA183
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: 6e92cc7db3c4f16365ac25400ddad370197bc0e90ec88233ec1ea5622756dac8; retrieved 2026-09-22T23:29:39.691Z.