- Date
- August 21, 1964
- Place
- New Lexington, AL · NEW LEXINGTON, AL
- Injuries
- 1 uninjured
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N6488ZPiper PA25
- Status
- Completed · report October 30, 1964
- Report
- Brief approved by the director
- Case key
- 181836
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-2553 64/8/21 NEW LEXINGTON ALA PIPER PA25 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 32, 940 TIME - 1615 N6488Z PX- 0 0 0 ASSOC CROP CTL ACTIVITY TOTAL HOURS, 38 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: EN ROUTE TO TREAT CROP COLLIDED WITH: TREES LANDING: FINAL APPROACH PROBABLE CAUSE(S) POWERPLANT - ENGINE STRUCTURE: VALVE ASSEMBLIES MISCELLANEOUS ACTS,CONDITIONS - STUCK PARTIAL POWER LOSS - PARTIAL LOSS OF POWER - 1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 650 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - COTTON 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 - NOT INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 300 FIRE AFTER IMPACT REMARKS- INTAKE VALVE NO. 4 CYLINDER STUCK.
Aircraft
- Registration
- N6488Z
- Reported as
- Piper PA25
- 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.