- Date
- June 5, 1971
- Place
- Schoolcraft, MI · SCHOOLCRAFT, MI
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N55062Boeing A75
- Status
- Completed · report January 27, 1972
- Report
- Brief approved by the director
- Case key
- 161413
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-1825 71/6/5 SCHOOLCRAFT,MICH BOEING A75 CR- 0 0 1 COMMERCIAL COMMERCIAL, FL.INSTR., TIME - 2030 N55062 PX- 0 0 0 ASSOC CROP CTL ACTIVITY AGE 41, 4500 TOTAL HOURS, DAMAGE-SUBSTANTIAL OT- 0 0 0 500 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - MARVIN FORSYTH DEPARTURE POINT INTENDED DESTINATION SCHOOLCRAFT,MICH LOCAL TYPE OF ACCIDENT PHASE OF OPERATION NOSE OVER/DOWN LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - PHYSICAL IMPAIRMENT EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING ON AIRPORT SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 2800 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - BEANS TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -NOT FASTENED GLOVES - NOT USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - INSTALLED CRASH BAR - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT ELEVATION-AREA BEING TREATED-FEET - 860 SWATH RUN-HOW FLOWN - UNKNOWN/NOT REPORTED REMARKS- HOPPER TANK SPLIT.CHEMICAL SPRAYED INTO PLT EYES.SPRAYING GUITHION.
Aircraft
- Registration
- N55062
- Reported as
- Boeing A75
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Marvin Forsyth
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.