- Date
- April 26, 1967
- Place
- Altair, TX · ALTAIR, TX
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N57958Boeing A75N1
- Status
- Completed · report September 7, 1967
- Report
- Brief approved by the director
- Case key
- 117680
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-1300 67/4/26 ALTAIR, TEX BOEING A75N1 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 40, 318 TIME - 1730 N57958 PX- 0 0 0 ASSOC CROP CTL ACTIVITY TOTAL HOURS, UNK/NR IN DAMAGE-SUBSTANTIAL OT- 0 0 0 TYPE, NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: NORMAL CRUISE GEAR COLLAPSED LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) POWERPLANT - MISCELLANEOUS: POWERPLANT FAILURE FOR UNDETERMINED REASONS FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND SPECIAL DATA TOTAL HOURS IN CROP CONTROL - UNKNOWN/NOT REPORTED KIND OF OPERATION - FERTILIZING (DUST) KIND OF CROP - RICE TYPE OF CHEMICAL USED - UNKNOWN/NOT REPORTED PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - NOT USED GOGGLES - USED CRASH HELMET - AVAILABLE-NOT USED COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT REMARKS- STRUCK LEVEE IN RICE FIELD.
Aircraft
- Registration
- N57958
- Reported as
- Boeing A75N1
- 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.