- Date
- July 29, 1967
- Place
- King, NC · KING, NC
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Maneuvering
- Aircraft
- N7158KPiper PA-18
- Status
- Completed · report October 25, 1967
- Report
- Brief approved by the director
- Case key
- 115707
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-2598 67/7/29 KING,NC PIPER PA-18 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 24, 3500 TIME - 1000 N7158K PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 902 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - KING 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 - 1300 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - TOBACCO TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -UNKNOWN/NOT REPORTED GLOVES - NOT USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - BELLY TERRAIN-TYPE -MOUNTAINOUS ELEVATION-AREA BEING TREATED-FEET - 1400 DENSE WITH TREES SWATH RUN-HOW FLOWN - CROSSWIND PROCEDURE TURNAROUND - SECOND 1/3 TURN
Aircraft
- Registration
- N7158K
- Reported as
- Piper PA-18
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- King
N7158KRegistered now · Piper PA-18-105 SPECIALAirframe modelPiper PA-18-105 SPECIALEngine modelLycoming 0-235 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.