- Date
- August 29, 1971
- Place
- Glenrose, TX · GLENROSE, TX
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Maneuvering
- Aircraft
- N6368ZPiper PA-25
- Status
- Completed · report June 28, 1971
- Report
- Brief approved by the director
- Case key
- 164136
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-4107 71/8/29 GLENROSE,TEX PIPER PA-25 CR- 0 0 1 COMMERCIAL COMMERCIAL, FL.INSTR., TIME - 0800 N6368Z PX- 0 0 0 AERIAL APPLICATION AGE 28, UNK/NR TOTAL DAMAGE-SUBSTANTIAL OT- 0 0 0 HOURS, UNK/NR IN TYPE, NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION GLENROSE,TEX LOCAL TYPE OF ACCIDENT PHASE OF OPERATION STALL IN FLIGHT: PROCEDURE TURNAROUND PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 100 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - COTTON TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -UNKNOWN/NOT REPORTED GLOVES - 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 - 650 SWATH RUN-HOW FLOWN - WIND CALM PROCEDURE TURNAROUND - THIRD 1/3 TURN
Aircraft
- Registration
- N6368Z
- Reported as
- Piper PA-25
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
N6368ZRegistration cancelled Dec 26, 2018 · Piper PA-25Airframe modelPiper PA-25Engine 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.