- Date
- August 1, 1966
- Place
- Yates City, IL · YATES CITY, IL
- Injuries
- 1 minor
- Damage
- Destroyed
- Phase of flight
- Maneuvering
- Aircraft
- N6379HPiper J3C-65
- Status
- Completed · report October 31, 1966
- Report
- Brief approved by the director
- Case key
- 121634
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-2409 66/8/1 YATES CITY ILL PIPER J3C-65 CR- 0 0 1 COMMERCIAL COMMERCIAL, FL.INSTR., TIME - 0850 N6379H PX- 0 0 0 AERIAL APPLICATION AGE 32, 3922 TOTAL HOURS, DAMAGE-DESTROYED OT- 0 0 0 217 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - TRI-COUNTY TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES IN FLIGHT: PULLUP FROM SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS FACTOR(S) TERRAIN - HIGH OBSTRUCTIONS SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 150 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - CORN TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - NOT USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE-NOT USED COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - AFT OF PILOT TERRAIN-TYPE -ROLLING ELEVATION-AREA BEING TREATED-FEET - 700 SWATH RUN-HOW FLOWN - CROSSWIND
Aircraft
- Registration
- N6379H
- Reported as
- Piper J3C-65
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Tri-County
N6379HRegistration cancelled Mar 14, 2012 · Piper J3C-65Airframe modelPiper J3C-65Engine modelContinental A&C65 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.