# NTSB LAX76DUG36: Naval Fcty N3N, N44846, Ripley, CA, February 18, 1976

- Type: NTSB accident investigation
- Classification: Accident · Serious injuries · Closed
- Date: February 18, 1976
- Place: Ripley, CA · RIPLEY, CA
- Location: 33.5238° N, 114.6530° W: Placed by OpenAirDocs: center of Ripley, CA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.5238&lon=-114.6530&mi=10
- Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping)
- Highest injury: Serious injuries
- Injuries: 1 serious
- Status: Completed, report March 29, 1976
- Report: Brief approved by the director
- NTSB case key (mKey): 152295
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX76DUG36
- Page: https://openairdocs.org/ntsb/LAX76DUG36

## NTSB brief

```
----------------------------------------------------------------------------------------------------------------------------
 FILE    DATE          LOCATION          AIRCRAFT DATA       INJURIES       FLIGHT                        PILOT DATA
                                                               F  S M/N     PURPOSE
----------------------------------------------------------------------------------------------------------------------------
3-0233  76/2/18  NR.RIPLEY,CA          NAVAL FCTY N3N      CR-  0  1  0  COMMERCIAL                COMMERCIAL, AGE 53, 11100
        TIME - 1725                    N44846              PX-  0  0  0  AERIAL APPLICATION        TOTAL HOURS, 457 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
         RIPLEY,CA                    LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     IN FLIGHT: PROCEDURE TURNAROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
           PILOT IN COMMAND - DIVERTED ATTENTION FROM OPERATION OF AIRCRAFT
        FACTOR(S)
           TERRAIN - HIGH OBSTRUCTIONS
         SPECIAL DATA
          TOTAL HOURS IN CROP CONTROL - 9999                       KIND OF OPERATION - SPRAYING CROPS
          KIND OF CROP - LETTUCE                                   TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC
          PILOT' S SEAT BELT -FASTENED-PROPERLY                    GLOVES - NOT USED
          GOGGLES - NOT USED                                       CRASH HELMET - AVAILABLE USED
          COCKPIT CRASHPAD - NOT INSTALLED                         TANK/HOPPER-LOCATION - FORWARD OF PILOT
          TERRAIN-TYPE -LEVEL,FLAT                                 ELEVATION-AREA BEING TREATED-FEET -  260
          SWATH RUN-HOW FLOWN - DOWNWIND                           PROCEDURE TURNAROUND - FIRST 1/3 TURN
        REMARKS- LOOKING FOR FLAG MAN.
```

## Aircraft

- Registration: [N44846](https://openairdocs.org/deregistered/N44846-1976-04-08), registration cancelled 1976-04-08, S/N 3042 (OpenAirDocs)
- Reported make and model: NAVAL FCTY N3N
- Registry model: [Naval Aircraft Factory N3N-3](https://openairdocs.org/model/naval-aircraft-factory-n3n-3) (registry code 6120202) (OpenAirDocs)
- Category: Airplane
- Engines: reciprocating
- Damage: Destroyed

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 19760218003509A](https://openairdocs.org/incident/19760218003509A), Feb 18, 1976: Naval N3N3, Ripley, CA, Destroyed. Looking for flag man.

## Other investigations on N44846 (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX68D0354](https://openairdocs.org/ntsb/LAX68D0354), Mar 3, 1968: Naval Fcty N3N-3 (N44846), Yuma, AZ, substantial damage

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.