IAD96LA115 · Piper PA-46-310P
Piper PA-46-310P · Accident: loss of control in flight during initial climb
From Hartford Brainard Airport (HFD) to Block Island State Airport (BID)
Event
- NTSB case
- IAD96LA115
- 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-46-310P
- Aircraft type
- Piper PA-46
- 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
- N234DM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hartford Brainard Airport (HFD)To Block Island State Airport (BID), BLOCK ISLAND, RI
- 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
- Initial climb
- 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 control in flight
- 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
- Stall/mush
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Airspeed(vlof), not attained
- Pilot in command › Preflight planning/preparation, inadequate
- Pilot in command › Stall/mush, inadvertent
Approximate · Estimated position: the centre of Hartford, CT, the place the record names. Not the accident site.
NTSB narrative
The pilot reported that he performed a rolling takeoff from the 2315 ft runway. He said that as soon as the airplane broke ground on the takeoff roll, he experienced a loss of engine power. The pilot said that he retracted the gear to help clear a 42 ft dike at the departure end of the runway. Also, he reported that after clearing the dike, he turned gradually to the left, and the left wing stalled. Two witnesses reported hearing loud, steady sounds from the airplane's engine and propeller. They said they saw the airplane in a high nose-up attitude, and watched the airplane descend behind the dike. The engine could be heard until the airplane contacted the river. During an operational check after the accident, the engine performed at recommended levels. According to performance data provided by the FAA, at the given takeoff weight, with a zero degree flap setting, the airplane required 2850 feet of runway to clear a 50 ft obstacle. The charts were based on full power before brake release.
Probable cause
the pilot's inadequate preflight planning/preparation, and his failure to attain the proper lift-off airspeed, which resulted in a stall and collision with the terrain (river).
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD96LA115
- Event ID
- 20001208X06260
- Case number
- IAD96LA115
- 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: 04c993e46d3e4aa1329cdf89f5b79480fa951e11cb92bfd3b5e5abf70f29aa1d; retrieved 2026-09-21T12:38:17.452Z.