NYC01LA156 · Piper J3F-65
Piper J3F-65 · Accident: total loss of engine power (non-mechanical) during initial climb
From 7D5 · Findlay, OH to 7D5 · Findlay, OH
Event
- NTSB case
- NYC01LA156
- 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 J3F-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
- N40782
- Operator
- Hal Durbin
- Onboard fatalities
- Unknown
- Route
- From 7D5 · Findlay, OHTo 7D5 · Findlay, OH
- 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 (non-mechanical)
- 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
- Utility pole
- 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
- Ignition system, ignition lead › Chafed
Approximate · Estimated position: the centre of Findlay, OH, the place the record names. Not the accident site.
NTSB narrative
Shortly after takeoff, the engine lost all power, and the pilot performed a forced landing to a soybean field. Examination of the wreckage revealed that when the magneto switch was in the "BOTH" position, an ohmmeter showed the connection as grounded. Further examination revealed that two ignition switch leads were chafed, and grounded against a screw. The airplane was manufactured in 1941, and the chafing appeared to have occurred over a long period of time.
Probable cause
Two chafed ignition switch leads, which resulted in a failure of the ignition system and subsequent total loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01LA156
- Event ID
- 20010705X01307
- Case number
- NYC01LA156
- 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: f35f4c5f3ae37c318bd9b45c7927a0cb102fe71647be9b2ef11a7efb0f46dc99; retrieved 2026-09-22T11:49:26.125Z.