- Date
- July 21, 1970
- Place
- Shallowater, TX · SHALLOWATER, TX
- Injuries
- 1 uninjured
- Damage
- Destroyed
- Phase of flight
- Initial climb
- Aircraft
- N4984YPiper PA-25
- Status
- Completed · report May 22, 1971
- Report
- Brief approved by the director
- Case key
- 109364
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-3076 70/7/21 SHALLOWATER,TEX PIPER PA-25 CR- 0 0 1 COMMERCIAL COMMERCIAL, FL.INSTR., TIME - 0600 N4984Y PX- 0 0 0 ASSOC CROP CTL ACTIVITY AGE 44, 4756 TOTAL HOURS, DAMAGE-DESTROYED OT- 0 0 0 2843 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - STRIP DEPARTURE POINT INTENDED DESTINATION SHALLOWATER,TEX LOCAL TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: DIRT BANK TAKEOFF: INITIAL CLIMB PROBABLE CAUSE(S) PILOT IN COMMAND - SELECTED WRONG RUNWAY RELATIVE TO EXISTING WIND FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SOFT SHOULDERS SPECIAL DATA TOTAL HOURS IN CROP CONTROL - UNKNOWN/NOT REPORTED KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - GRAIN FIELDS 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 FIRE AFTER IMPACT REMARKS- RWY LOWER AT MID-FLD. HIT 8 FT BANK.
Aircraft
- Registration
- N4984Y
- Reported as
- Piper PA-25
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Strip
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.