NYC02LA132 · Beech C23
General Aviation Services Beech C23 · Accident: loss of engine power en route
From Plum Island Airport (2B2) to Beverly Regional Airport (BVY)
Event
- NTSB case
- NYC02LA132
- 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
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
- N823DA
- Operator
- General Aviation Services
- Onboard fatalities
- Unknown
- Route
- From Plum Island Airport (2B2), Newburyport, MATo Beverly Regional Airport (BVY), Beverly, MA
- 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
- Loss of engine power
- 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
- Reason for occurrence undetermined
- Terrain condition › None suitable
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot-rated passenger performed the takeoff and downwind departure. As he reduced the engine power to cruise, the engine lost power. The commercial pilot immediately took control of the airplane, but was unable to restore engine power. He set up for a forced landing on a road; however, a vehicle on the road prevented the landing. The commercial pilot then side-stepped the airplane and performed a forced landing in the adjacent marsh. During ground roll, the nose wheel collapsed and the airplane nosed over. Fuel system continuity was confirmed with no evidence of contamination observed. The engine was test run, utilizing the airplane fuel system. However, the engine power was kept low due to damaged engine mounts and vibration. The carburetor was examined and found to run rich at all power settings. The richness varied from 17 percent at idle to 2 1/2 percent at takeoff power.
Probable cause
A power loss for undetermined reason(s), which resulted in a subsequent forced landing to unsuitable terrain. A factor was the unsuitable terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02LA132
- Event ID
- 20020718X01162
- Case number
- NYC02LA132
- 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: 069b6761a7084d378811ae51aacadfd4e335be429e04afee593720f64becb7de; retrieved 2026-09-22T10:45:39.531Z.