- Date
- March 30, 1971
- Place
- Vidal, CA · VIDAL, CA
- Injuries
- 1 serious
- Damage
- Destroyed
- Phase of flight
- Maneuvering
- Aircraft
- N5260Grumman G-164A
- Status
- Completed · report February 14, 1972
- Report
- Brief approved by the director
- Case key
- 160805
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-2107 71/3/30 VIDAL,CALIF GRUMMAN G-164A CR- 0 1 0 COMMERCIAL COMMERCIAL, FL.INSTR., TIME - 0845 N5260 PX- 0 0 0 AERIAL APPLICATION AGE 32, 5000 TOTAL HOURS, DAMAGE-DESTROYED OT- 0 0 0 1000 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - RIO MESA RANCH DEPARTURE POINT INTENDED DESTINATION VIDAL,CALIF LOCAL TYPE OF ACCIDENT PHASE OF OPERATION STALL: MUSH IN FLIGHT: PULLUP FROM SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED FACTOR(S) TERRAIN - HIGH OBSTRUCTIONS SPECIAL DATA TOTAL HOURS IN CROP CONTROL - UNKNOWN/NOT REPORTED KIND OF OPERATION - DUSTING CROPS KIND OF CROP - FRUIT ORCHARDS TYPE OF CHEMICAL USED - DRY CHEMICAL-NONTOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY CRASH HELMET - AVAILABLE USED CRASH BAR - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 700 SWATH RUN-HOW FLOWN - WIND CALM FIRE AFTER IMPACT REMARKS- 2ND PASS,PULLED UP OVR PWR LINES,PLT UN CK SINK RATE.ACFT SETTLED INTO TREES 150FT BEYOND WIRES.
Aircraft
- Registration
- N5260
- Reported as
- Grumman G-164A
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Rio Mesa Ranch
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.