# Accident 20260602006599A: Piper J3C-65, Granby, CT, June 2, 2026

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 2, 2026, 12:51 local time
- Place: Granby, CT
- Airport: Simsbury
- Damage: Substantial damage
- Phase of flight: Takeoff: Climb Out
- Operating rules: General operating rules (Part 91)
- Location: 41.9266° N, 72.7766° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=41.9266&lon=-72.7766&mi=10
- Aircraft: N331JM, registered now (https://openairdocs.org/aircraft/N331JM) (OpenAirDocs)
- Registry model: Piper J3C-65 (registry code 7100510, https://openairdocs.org/model/piper-j3c-65) (OpenAirDocs)
- Registry engine: Continental C90 series (registry code 17009, https://openairdocs.org/engine/continental-c90-series) (OpenAirDocs)
- Reported make and model: PIPER J3C-65
- Reported engine: CONT MOTOR C90-8F
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 3,600 total
- NTSB investigation: [NTSB ERA26LA225](https://openairdocs.org/ntsb/ERA26LA225) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260602006599A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON 06/02/2026 AT 1251 EDT, THE FAA RECEIVED A PRELIMINARY NOTICE REGARDING AN ACCIDENT INVOLVING PIPER J-3 CUB. THE AIRCRAFT EXPERIENCED A REPORTED LOSS OF ENGINE POWER SHORTLY AFTER DEPARTURE FROM SIMSBURY AIRPORT (4B9) AND CAME TO REST IN A FIELD NORTH OF THE AIRPORT NEAR 41 FLOYDVILLE ROAD, SIMSBURY, CT.

THE FAA INSPECTOR-IN-CHARGE (IIC) ARRIVED ON SCENE AT 1422 EDT. THE AIRCRAFT WAS OBSERVED IN ITS FINAL RESTING POSITION. NO FUEL LEAKAGE, FIRE, OR BIOHAZARD CONDITIONS WERE OBSERVED.

THE PILOT REPORTED ENGINE POWER LOSS SHORTLY AFTER DEPARTURE AT APPROXIMATELY 400 FEET AGL WITH RPM BETWEEN 2100 AND 2300. A RETURN TO THE AIRPORT WAS INITIATED. DURING THE TURN, RPM DECAYED BELOW 2000 AND AIRSPEED DECREASED.

THE PILOT SELECTED A FIELD NORTH OF THE AIRPORT FOR A FORCED LANDING. AT APPROXIMATELY 250 FEET AGL, TOTAL ENGINE POWER WAS LOST. THE AIRCRAFT WAS CONFIGURED FOR A FORCED LANDING TO A FIELD WITH FURROWS. CONTROL WAS MAINTAINED THROUGH TOUCHDOWN. THE AIRCRAFT CAME TO REST IN AN AGRICULTURAL FIELD AND CONTACTED AN AGRICULTURAL STRUCTURE. THE PILOT AND PASSENGER EXITED THE AIRCRAFT.

A CURSORY EXAMINATION OF THE AIRCRAFT AT THE ACCIDENT SCENE REVEALED DAMAGE TO THE LEFT WING TIP, PROPELLER, AND LANDING GEAR.

A FOLLOW-UP EXAMINATION OF THE AIRCRAFT BY THE INSPECTOR-IN-CHARGE (IIC) WAS CONDUCTED ON JUNE 5, 2026, WHILE THE AIRCRAFT REMAINED IN ITS ORIGINAL RESTING POSITION. THE EXAMINATION REVEALED BENT ENGINE MOUNTS AND A FIREWALL DISPLACED AFT. NO WING SPAR DAMAGE WAS OBSERVED. BASED ON THESE FINDINGS, THE AIRCRAFT WAS DETERMINED TO HAVE SUSTAINED SUBSTANTIAL DAMAGE.

REPORTED METAR WEATHER AT THE TIME OF THE OCCURRENCE WAS KBDL 021651Z 03004KT 10SM FEW065 BKN090 BKN250 23/06 A3012. CONDITIONS WERE REPORTED AS VMC.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB ERA26LA225](https://openairdocs.org/ntsb/ERA26LA225), Jun 2, 2026: Piper J5C-65 (N331JM), East Granby, CT, substantial damage, investigation ongoing

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.