- Date
- October 24, 1968
- Place
- Dixon, CA · DIXON, CA
- Injuries
- 2 fatal
- Phase of flight
- Maneuvering
- Status
- Completed · report November 27, 1968
- Report
- Brief approved by the director
- Case key
- 107775
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-3398 68/10/24 DIXON,CALIF PIPER PA-25 CR- 1 0 0 COMMERCIAL COMMERCIAL, AGE 24, 300 TIME - 1045 N7742Z PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, UNK/NR IN DAMAGE-DESTROYED OT- 1 0 0 TYPE, NOT INSTRUMENT RATED. NAME OF AIRPORT - MAIN PRAIRIE TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH AIRCRAFT: BOTH IN FLIGHT IN FLIGHT: PULLUP FROM SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO SEE AND AVOID OTHER AIRCRAFT SPECIAL DATA TOTAL HOURS IN CROP CONTROL - UNKNOWN/NOT REPORTED KIND OF OPERATION - SEEDING CROPS KIND OF CROP - GRAIN FIELDS PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - USED GOGGLES - USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - INSTALLED CRASH BAR - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT ELEVATION-AREA BEING TREATED-FEET - 40 SPECIAL DATA SEGMENTS OF AVIATION INVOLVED - SMALL US GEN.AV.-SMALL US GEN.AV. CONTROLLING AGENCY - NO CONTROL RADAR CTL/SURVEILLANCE - NOT UNDER RADAR CONTACT TRAFFIC ADVISORY ISSUED - NONE CONTROL ZONE/AREA - NO EVASIVE ACTION TAKEN - NO FIRE AFTER IMPACT REMARKS- N7742Z OVERTOOK N4688Y DURING LT CLIMBING TURN TO RETURN TO AG STRIP.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-3398 68/10/24 DIXON,CALIF PIPER PA-25 CR- 1 0 0 COMMERCIAL COMMERCIAL, AGE 25, 1400 TIME - 1045 N4688Y PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, UNK/NR IN DAMAGE-DESTROYED OT- 1 0 0 TYPE, NOT INSTRUMENT RATED. NAME OF AIRPORT - MAIN PRAIRIE TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH AIRCRAFT: BOTH IN FLIGHT IN FLIGHT: PROCEDURE TURNAROUND PROBABLE CAUSE(S) PERSONNEL - MISCELLANEOUS-PERSONNEL: PILOT OF OTHER AIRCRAFT SPECIAL DATA TOTAL HOURS IN CROP CONTROL - UNKNOWN/NOT REPORTED KIND OF OPERATION - SEEDING CROPS KIND OF CROP - GRAIN FIELDS PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - USED GOGGLES - USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - INSTALLED CRASH BAR - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 40 SWATH RUN-HOW FLOWN - UPWIND SPECIAL DATA SEGMENTS OF AVIATION INVOLVED - SMALL US GEN.AV.-SMALL US GEN.AV. CONTROLLING AGENCY - NO CONTROL RADAR CTL/SURVEILLANCE - NOT UNDER RADAR CONTACT TRAFFIC ADVISORY ISSUED - NONE CONTROL ZONE/AREA - NO VERTICAL COLLISION ANGLE-DEGREES - *ERROR-INVALID CODE* EVASIVE ACTION TAKEN - NO FIRE AFTER IMPACT
Aircraft · 2
- Registration
- N4688Y
- Reported as
- Piper PA-25
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Main Prairie
N4688YRegistration cancelled Apr 18, 2013 · Piper PA-25-235Airframe modelPiper PA-25-235Engine modelLycoming 0-540 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.
- Registration
- N7742Z
- Reported as
- Piper PA-25
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Main Prairie
N7742ZRegistration cancelled Jun 11, 2003 · Piper PA-25-235Airframe modelPiper PA-25-235Engine modelLycoming 0-540 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.