- Date
- September 2, 1965
- Place
- Inverness, MS · INVERNESS, MS
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Maneuvering
- Aircraft
- N7504KPiper PA-18
- Status
- Completed · report December 21, 1965
- Report
- Brief approved by the director
- Case key
- 176408
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 ---------------------------------------------------------------------------------------------------------------------------- 2-0777 65/9/2 NR.INVERNESS,MISS. PIPER PA-18 CR- 1 0 0 COMMERCIAL COMMERCIAL, AGE 24, 666 TIME - 1613 N7504K PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 304 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: TREES IN FLIGHT: PROCEDURE TURNAROUND PROBABLE CAUSE(S) PILOT IN COMMAND - MISJUDGED ALTITUDE AND CLEARANCE MISCELLANEOUS ACTS,CONDITIONS - PILOT FATIGUE MISCELLANEOUS ACTS,CONDITIONS - SUNGLARE SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 304 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - COTTON TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - BELLY TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 112 SWATH RUN-HOW FLOWN - DOWNWIND PROCEDURE TURNAROUND - THIRD 1/3 TURN FIRE AFTER IMPACT REMARKS- ACCIDENT OCCURED DURING REENTRY TO SWATH RUN FROM LEFT TURNAROUND.PILOT FLEW 9.5 HRS.ON DAY OF ACC
Aircraft
- Registration
- N7504K
- Reported as
- Piper PA-18
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
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.