- Date
- July 13, 1965
- Place
- Hunter, AR · HUNTER, AR
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N714YGruman G-164
- Status
- Completed · report September 10, 1965
- Report
- Brief approved by the director
- Case key
- 177017
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-2023 65/7/13 HUNTER ARK GRUMAN G-164 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 36, 1940 TIME - 1700 N714Y PX- 0 0 0 ASSOC CROP CTL ACTIVITY TOTAL HOURS, 657 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: INITIAL CLIMB COLLIDED WITH: DITCHES LANDING: ROLL PROBABLE CAUSE(S) MISCELLANEOUS ACTS,CONDITIONS - FUEL EXHAUSTION PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 900 KIND OF OPERATION - FERTILIZING (LIQUID) KIND OF CROP - RICE TYPE OF CHEMICAL USED - DRY CHEMICAL-NONTOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - USED GOGGLES - USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT
Aircraft
- Registration
- N714Y
- Reported as
- Gruman G-164
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
N714YRegistered now · Grumman G-164Airframe modelGrumman G-164Engine modelPratt & Whitney R-985 series
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.