ERA11LA379 · Piper J3C-65
Piper J3C-65 · Accident: collision during takeoff/landing
From Walter J. Koladza Airport (GBR) to Walter J. Koladza Airport (GBR)
Event
- NTSB case
- ERA11LA379
- 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
Piper J3C-65
- Aircraft type
- Piper J3
- 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
- N98550
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Walter J. Koladza Airport (GBR), Great Barrington, MATo Walter J. Koladza Airport (GBR), Great Barrington, 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
- Landing
- Defining eventThe 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
- Collision during takeoff/landing
- 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
- Aircraft › Aircraft power plant
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that the accident flight was the first flight in the airplane in 6 months. During the initial climb, the engine experienced a partial loss of power. The pilot checked the magnetos and carburetor heat but was unsuccessful in his attempts to regain full engine power. Subsequently, he chose to land the airplane between two houses. A postaccident engine compression test revealed that the Nos. 1 and 4 cylinders had low compression. The No. 1 rocker cover was removed, and the rocker arm was tapped with a mallet, which brought its compression to within normal range. Disassembly of the No. 4 cylinder revealed that it was leaking past the exhaust valve and through the exhaust system. In addition, disassembly revealed a scored intake valve stem and valve guide. The intake valve would not operate and had to be forcefully removed from the valve guide. According to the engine overhaul manual, scored valve stems can cause the engine to produce low power. The pilot did not report performing any of the procedures to return the engine to service from indefinite storage (that is, more than 90 days). Therefore, it is also likely that the engine was never prepared for indefinite storage and, thus, was not stored improperly for the 6 months it was not used before the accident flight. During storage, the No. 4 intake and exhaust valves most likely became lodged in the valve guides, which resulted in a partial loss of engine power and subsequent forced landing to a field. It is likely that, if the engine had been properly stored, the recommended lubrication would have prevented the valves from sticking and scoring and that, if the engine had been properly removed from storage, the scored valves may have been detected and replaced, either of which action could have prevented the accident.
Probable cause
A partial loss of engine power due to the No. 4 intake and exhaust valves becoming lodged in the valve guides, which resulted from a lack of use, improper engine storage preparation, and improper return to service from indefinite storage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11LA379
- Event ID
- 20110706X71714
- Case number
- ERA11LA379
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 6cd265862c2e62d68fc6302a02b81792518abd2af05bc8d42f98f635e317c28e; retrieved 2026-09-15T16:24:37.616Z.