- Date
- July 24, 1968
- Place
- Muleshoe, TX · MULESHOE, TX
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N4522NBoeing B75N1
- Status
- Completed · report January 21, 1970
- Report
- Brief approved by the director
- Case key
- 108083
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-4914 68/7/24 MULESHOE,TEX BOEING B75N1 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 45, 12000 TIME - 0900 N4522N PX- 0 0 0 ASSOC CROP CTL ACTIVITY TOTAL HOURS, 500 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION MULESHOE,TEX MULESHOE,TEX TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: INITIAL CLIMB NOSE OVER/DOWN LANDING: ROLL PROBABLE CAUSE(S) POWERPLANT - MISCELLANEOUS: POWERPLANT FAILURE FOR UNDETERMINED REASONS FACTOR(S) TERRAIN - WET,SOFT GROUND PARTIAL POWER LOSS - PARTIAL LOSS OF POWER - 1 ENGINE 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 - USED GOGGLES - USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT REMARKS- PLT STATED ENG LOST POWER. INVEST FAILED TO DISCLOSE REASON. T/O MADE FROM PASTURE.
Aircraft
- Registration
- N4522N
- Reported as
- Boeing B75N1
- 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.