- Date
- June 12, 1966
- Place
- Rome, OR · ROME, OR
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Maneuvering
- Aircraft
- N45267Naval Fcty N3N-3
- Status
- Completed · report January 27, 1967
- Report
- Brief approved by the director
- Case key
- 171566
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-0485 66/6/12 NR.ROME OREG NAVAL FCTY N3N-3 CR- 1 0 0 COMMERCIAL COMMERCIAL, AGE 30, 436 TIME - 0630 N45267 PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 118 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - ROME-FLIGHT STRIP TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES IN FLIGHT: PULLUP FROM SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - MISJUDGED CLEARANCE SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 216 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - PASTURE TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - USED GOGGLES - USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 4000 SWATH RUN-HOW FLOWN - WIND CALM PROCEDURE TURNAROUND - ENTRY TO PROCEDURE TURN FIRE AFTER IMPACT
Aircraft
- Registration
- N45267
- Reported as
- Naval Fcty N3N-3
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Rome-Flight Strip
N45267Registration cancelled Aug 4, 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.