- Date
- April 26, 1968
- Place
- Brawley, CA · BRAWLEY, CA
- Injuries
- 1 serious
- Damage
- Destroyed
- Phase of flight
- Maneuvering
- Aircraft
- N44861Naval Fcty N3N-3
- Status
- Completed · report September 10, 1968
- Report
- Brief approved by the director
- Case key
- 110521
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-2113 68/4/26 BRAWLEY,CALIF NAVAL FCTY N3N-3 CR- 0 1 0 COMMERCIAL COMMERCIAL, AGE 54, 18500 TIME - 0830 N44861 PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 2000 IN DAMAGE-DESTROYED OT- 0 0 0 TYPE, INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: OBJECT IN FLIGHT: SWATH RUN 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 - DUSTING CROPS KIND OF CROP - OTHER TYPE OF CHEMICAL USED - DRY CHEMICAL-NONTOXIC PILOT' S SEAT BELT -UNKNOWN/NOT REPORTED GLOVES - NOT USED GOGGLES - USED CRASH HELMET - AVAILABLE-NOT USED COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 0 SWATH RUN-HOW FLOWN - WIND CALM FIRE AFTER IMPACT REMARKS- RT LOWER WING STRUCK HAY LOADING CRANE BOOM. DUSTING SUGAR BEETS.
Aircraft
- Registration
- N44861
- Reported as
- Naval Fcty N3N-3
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
N44861Registration cancelled Jun 14, 1968 · 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.