- Date
- July 19, 1972
- Place
- Hazen, AR · HAZEN, AR
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N6579Grumman G-164A
- Status
- Completed · report February 28, 1973
- Report
- Brief approved by the director
- Case key
- 168078
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-2605 72/7/19 HAZEN,ARK GRUMMAN G-164A CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 30, 7000 TIME - 1415 N6579 PX- 0 0 0 ASSOC CROP CTL ACTIVITY TOTAL HOURS, 4000 IN DAMAGE-SUBSTANTIAL OT- 0 0 0 TYPE, NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION HAZEN,ARK LOCAL TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: INITIAL CLIMB COLLIDED WITH: CROP LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) POWERPLANT - ENGINE STRUCTURE: BLOWER,IMPELLER ASSEMBLY MISCELLANEOUS ACTS,CONDITIONS - MATERIAL FAILURE TERRAIN - ROUGH/UNEVEN COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 2000 KIND OF OPERATION - FERTILIZING (DUST) KIND OF CROP - RICE TYPE OF CHEMICAL USED - DRY CHEMICAL-NONTOXIC GLOVES - NOT USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE-NOT USED COCKPIT CRASHPAD - INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - *ERROR-INVALID CODE*
Aircraft
- Registration
- N6579
- Reported as
- Grumman G-164A
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
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.