DFW07CA035 · Piper J3C-65
Piper J3C-65 · Accident: loss of engine power during initial climb
From Humnoke, AR to Humnoke, AR
Event
- NTSB case
- DFW07CA035
- 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
- N7054H
- Operator
- Delbert E Brown · private individual
- Onboard fatalities
- Unknown
- Route
- From Humnoke, ARTo Humnoke, AR
- 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 engine power
- 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
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The non-certificated pilot reported that he departed his private airstrip to the north to "ride over his farm." He added that he noticed that the engine was "running strange as if it had water in the fuel." During the initial takeoff climb, the engine lost power while climbing through 300 feet. The best suitable forced landing was a cultivated rice field, so the pilot attempted to land the tailwheel equipped airplane in the field. During the landing roll on the soft terrain, the airplane nosed over and came to rest in the inverted position. The pilot was assisted out of the airplane by his grandson, who witnessed the accident. Examination of the airplane revealed that the airplane sustained structural damage. The reason for the reported loss of engine power could not be determined. Weather was reported as clear skies with light and variable winds.
Probable cause
The loss of engine power during initial takeoff climb for undetermined reasons. A factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW07CA035
- Event ID
- 20070118X00065
- Case number
- DFW07CA035
- 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, 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: 72129b21dd5cb203eabbdf195829b10f4c8aaa56e335da648ac80ce20c9541ea; retrieved 2026-09-22T04:10:16.663Z.