- Date
- June 8, 1966
- Place
- Anasco, PR · ANASCO, PR
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Maneuvering
- Aircraft
- N9407FHughes 269B
- Status
- Completed · report November 16, 1966
- Report
- Brief approved by the director
- Case key
- 171525
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-0391 66/6/8 NR.ANASCO PR HUGHES 269B CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 23, 295 TIME - 1755 N9407F PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 60 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES 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 - 260 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - OTHER TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -UNKNOWN/NOT REPORTED GLOVES - USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - SIDES TERRAIN-TYPE -HILLY ELEVATION-AREA BEING TREATED-FEET - 150 SWATH RUN-HOW FLOWN - WIND CALM REMARKS- POSITION OF WIRES CHECKED PRIOR TO FLIGHT. BLENDED INTO CLOUD BACKGROUND DURING SWATH RUN.
Aircraft
- Registration
- N9407F
- Reported as
- Hughes 269B
- Category
- Helicopter
- Engine
- reciprocating
- Damage
- Substantial damage
N9407FRegistration cancelled Mar 23, 2018 · Hughes 269BAirframe modelHughes 269BEngine modelLycoming I0360 series
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.