NYC06LA219 · Beech F33A
Beech F33A · Accident: partial loss of engine power (mechanical failure) en route
From Nashua Airport / Boire Field (ASH) to Hartford Brainard Airport (HFD)
Event
- NTSB case
- NYC06LA219
- 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 F33A
- Aircraft type
- Beechcraft 33
- 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
- N3708B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Nashua Airport / Boire Field (ASH), Nashua, NHTo Hartford Brainard Airport (HFD), Hartford, CT
- 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 · descent
- 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
- Partial loss of engine power (mechanical failure)
- 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
- 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
- Fuel system, line › Loose
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While leveling the airplane after a descent from 3,000 feet to 1,500 feet, the pilot increased the throttle to level the airplane; however, engine power did not return, and the airplane continued to descend. The airplane subsequently impacted trees and terrain during a forced landing attempt. Witnesses reported hearing the engine "popping" and "sputtering" as the airplane descended. Following the accident, the engine was removed from the airframe and test run. During the first test run the engine exhibited varying interruptions of power, and when the throttle was increased to full, it reached a maximum rpm of 1,450. Troubleshooting revealed that all six fuel injector lines were loosely attached to the fuel manifold valve. After all of the lines were tightened, the engine ran without any interruption of power, and reached a maximum rpm of 2,644. Examination of maintenance records revealed that significant maintenance had been performed on the engine 7 months, and 246 flight hours, prior to the accident flight. Additionally, four of the six fuel injector nozzles were replaced about 6 months before the accident flight.
Probable cause
A loosening of the fuel injector lines from the fuel manifold valve, which resulted in a partial loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC06LA219
- Event ID
- 20060925X01394
- Case number
- NYC06LA219
- 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: c708acefb32b3cb9a75e49d9bf91e82ddd83a35f0699f824e7ffa004e7abe9ab; retrieved 2026-09-21T18:41:07.676Z.