FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL98LA091 · Piper J3C-65

4 Jul 1998 · Zellwood, FL, United States

Piper J3C-65 · Accident: loss of engine power during initial climb

From Bob White Field (X61) to an unrecorded destination

Report a problem

Event

NTSB case
ATL98LA091
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
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

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
N42760
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bob White Field (X61)To not recorded
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the pilot, he was conducting touch and go landings at the Bob White Field. Just prior to turning crosswind on the fourth departure, the engine lost power. The pilot applied carburetor heat and full throttle, but the engine continued to lose power until it quit. A forced landing was made in a farm field. The wheels sank into the soft ground, and the airplane nosed over. After the accident, the engine and fuel were tested. The engine started, ran at a low revolutions per minute (RPM), and was able to produce maximum RPM. The magnetos were checked while the engine was operating, with no discrepancies noted. According to the FAA inspector, there was no problem with the operation of the engine during the test run. There was fuel in the airplane, approximately 3/4 of a tank. It was drained and examined, with no water or sediment found.

Probable cause

The loss of engine power for undetermined reasons which led to a forced landing and nose over. A factor affecting the severity of the damage was the soft terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL98LA091
Event ID
20001211X10469
Case number
ATL98LA091
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: 0487343259e01093e9fd34a30af1338af1dbb71bd5c48e77f41c52f848f92954; retrieved 2026-09-22T17:34:54.390Z.