- Date
- July 16, 1965
- Place
- Quincy, WA · QUINCY, WA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Maneuvering
- Aircraft
- N6607ZPiper PA-25
- Status
- Completed · report April 14, 1966
- Report
- Brief approved by the director
- Case key
- 176244
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-3922 65/7/16 NR.QUINCY WASH PIPER PA-25 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 49, 10000 TIME - 2000 N6607Z PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 425 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: PULLUP FROM SWATH RUN GEAR COLLAPSED LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) POWERPLANT - MISCELLANEOUS: POWERPLANT FAILURE FOR UNDETERMINED REASONS FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 2000 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - CLOVER TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - NOT USED GOGGLES - NOT 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 - 1250 SWATH RUN-HOW FLOWN - WIND CALM PROCEDURE TURNAROUND - ENTRY TO PROCEDURE TURN
Aircraft
- Registration
- N6607Z
- Reported as
- Piper PA-25
- 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.