NYC86FA196 · Grumman TBM-3E
Professional Aircraft Sales Grumman TBM-3E · Accident: total loss of engine power (mechanical failure) during initial climb
From 5B3 · Danielson, CT to Calverton Executive Airpark (CTO)
Event
- NTSB case
- NYC86FA196
- 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
- 1 · 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
Grumman TBM-3E
- Aircraft type
- Grumman TBM-3
- 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
- N6581D
- Operator
- Professional Aircraft Sales
- Onboard fatalities
- Unknown
- Route
- From 5B3 · Danielson, CTTo Calverton Executive Airpark (CTO), Calverton, NY
- 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
- 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
- Destroyed
Cause areas
- Engine assembly, piston › Burned
- Engine assembly, piston › Failure, total
Approximate · Estimated position: the centre of Brooklyn, CT, the place the record names. Not the accident site.
NTSB narrative
THE ACFT WAS BEING FLOWN TO THE OWNER'S RESIDENCE WHEN THE ACCIDENT OCCURRED. SHORTLY AFTER TAKEOFF BLACK AND WHITE SMOKE WAS OBSERVED EMITTING FROM THE ENG COWLING AND THE ENG WAS HEARD SPUTTERING. ACCORDING TO WITNESSES, THE ACFT LEVELED OFF AT AN ALT OF APRX 250-400 FT AGL AND BEGAN A LEFT TURN BACK TOWARD THE ARPT. A WITNESS STATED THE ACFT THEN ROLLED INVERTED AND DESCENDED TO IMPACT WITH THE TERRAIN. POST ACCIDENT INSPECTION OF THE WRECKAGE REVEALED THE #8 AND #10 PISTON HEADS EACH HAD A HOLE BURNED THROUGH THEM.PISTON #1, #13, #14, #2, AND #3 ALSO SHOWED SIGNS OF HEAT DAMAGE. THE LAST ANNUAL INSPECTION WAS PERFORMED ON SEPTEMBER 7, 1983. THE ACFT HAD BEEN ISSUED A FERRY PERMIT FOR THIS FLT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC86FA196
- Event ID
- 20001213X34583
- Case number
- NYC86FA196
- 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: a94d2d91454987d1ade6de5075edaf7498cb44e8b93c7ab73411565de6e783c8; retrieved 2026-09-21T04:27:29.165Z.