- Date
- June 19, 1969
- Place
- Texarkana, AR · TEXARKANA, AR
- Injuries
- 1 uninjured
- Damage
- Destroyed
- Phase of flight
- Initial climb
- Aircraft
- N4559YPiper PA-25
- Status
- Completed · report August 8, 1969
- Report
- Brief approved by the director
- Case key
- 174927
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-1789 69/6/19 TEXARKANA,ARK PIPER PA-25 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 38, 4200 TIME - 1400 N4559Y PX- 0 0 0 ASSOC CROP CTL ACTIVITY TOTAL HOURS, 1200 IN DAMAGE-DESTROYED OT- 0 0 0 TYPE, NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: INITIAL CLIMB COLLIDED WITH: DITCHES LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) POWERPLANT - MISCELLANEOUS: POWERPLANT FAILURE FOR UNDETERMINED REASONS PARTIAL POWER LOSS - PARTIAL LOSS OF POWER - 1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 55 KIND OF OPERATION - FERTILIZING (LIQUID) KIND OF CROP - GRAIN FIELDS TYPE OF CHEMICAL USED - LIQUID CHEMICAL-NONTOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - NOT USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT
Aircraft
- Registration
- N4559Y
- Reported as
- Piper PA-25
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
N4559YRegistration cancelled Jul 19, 2012 · Piper PA-25-235Airframe modelPiper PA-25-235Engine 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.