- Date
- September 9, 1967
- Place
- Casa Grande, AZ · CASA GRANDE, AZ
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N45293Naval Fcty N3N
- Status
- Completed · report December 6, 1967
- Report
- Brief approved by the director
- Case key
- 114472
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 ---------------------------------------------------------------------------------------------------------------------------- 2-0732 67/9/9 NR.CASA GRANDE,ARIZ NAVAL FCTY N3N CR- 1 0 0 COMMERCIAL COMMERCIAL, FL.INSTR., TIME - 0955 N45293 PX- 0 0 0 ASSOC CROP CTL ACTIVITY AGE 45, 8200 TOTAL HOURS, DAMAGE-DESTROYED OT- 0 0 0 73 IN TYPE, NOT INSTRUMENT RATED. NAME OF AIRPORT - CASA GRANDE TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: ELECTRONIC TOWERS IN FLIGHT: EN ROUTE TO TREAT CROP PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS SPECIAL DATA TOTAL HOURS IN CROP CONTROL - UNKNOWN/NOT REPORTED KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - COTTON TYPE OF CHEMICAL USED - LIQUID CHEMICAL-NONTOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - USED GOGGLES - USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - INSTALLED CRASH BAR - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 1400 FIRE AFTER IMPACT
Aircraft
- Registration
- N45293
- Reported as
- Naval Fcty N3N
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Casa Grande
N45293Registration cancelled Nov 16, 1967 · Naval Aircraft Factory N3N-3Airframe modelNaval Aircraft Factory N3N-3
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.