NYC05LA130 · Raytheon A36
Raytheon A36 · Accident: loss of engine power en route
From Laconia Municipal Airport (LCI) to Worcester Regional Airport (ORH)
Event
- NTSB case
- NYC05LA130
- 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
Raytheon A36
- Aircraft type
- Beechcraft 36
- 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
- N838DM
- Operator
- David Massad
- Onboard fatalities
- Unknown
- Route
- From Laconia Municipal Airport (LCI), Laconia, NHTo Worcester Regional Airport (ORH), Worcester, 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel exhaustion; Tree(s)
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Approximately 10 minutes after takeoff, the airplane experienced a loss of engine power, and subsequently impacted trees during the ensuing forced landing. Examination of the airplane did not reveal any mechanical malfunctions. Both fuel tanks were compromised; however, there was no evidence of a fuel spill in the area surrounding the accident site. At the time of the accident, the airplane had been operated for about 95 total hours, and 10 hours since its most recent annual inspection, which was performed about 4 months prior to the accident. The airplane was owned by the pilot and sold about 5 months prior the accident. With regard to the accident, the pilot informed the new owner and a mechanic that the airplane did not have any mechanical problems, and he thought that he could make it back to his home airport when he experienced a power loss due to fuel exhaustion.
Probable cause
The pilot's inadequate preflight planning, which resulted in a loss of engine power due to fuel exhaustion, and subsequent collision with trees during a forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC05LA130
- Event ID
- 20050815X01242
- Case number
- NYC05LA130
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-08-07.
- API snapshot SHA-256: b71cb43d93102de4ed108c105d0625ad6ed2da4e2e20d22711ae65bffad7b9b5; retrieved 2026-09-21T18:55:56.971Z.