- Date
- February 2, 1971
- Place
- Corcoran, CA · CORCORAN, CA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Takeoff
- Aircraft
- N4848YPiper PA-25
- Status
- Completed · report December 14, 1971
- Report
- Brief approved by the director
- Case key
- 159814
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-0838 71/2/2 CORCORAN,CALIF PIPER PA-25 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 34, 5600 TIME - 1600 N4848Y PX- 0 0 0 ASSOC CROP CTL ACTIVITY TOTAL HOURS, 1200 IN DAMAGE-SUBSTANTIAL OT- 0 0 0 TYPE, INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION CORCORAN,CALIF LOCAL TYPE OF ACCIDENT PHASE OF OPERATION GEAR COLLAPSED TAKEOFF: RUN PROBABLE CAUSE(S) AIRFRAME - LANDING GEAR: MAIN GEAR-SHOCK ABSORBING ASSY,STRUTS,ATTACHMENTS,ETC. MISCELLANEOUS ACTS,CONDITIONS - MATERIAL FAILURE SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 1200 KIND OF OPERATION - FERTILIZING (DUST) KIND OF CROP - GRAIN FIELDS TYPE OF CHEMICAL USED - DRY 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 TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 200 SWATH RUN-HOW FLOWN - WIND CALM REMARKS- BOTTOM LUG ON SHOCK ABSORBER,PIPER P/N 486-606,BROKE THROUGH BOLT HOLE.
Aircraft
- Registration
- N4848Y
- Reported as
- Piper PA-25
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
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.