- Date
- June 4, 1973
- Place
- Minter City, MS · MINTER CITY, MS
- Injuries
- 1 uninjured
- Damage
- Destroyed
- Phase of flight
- Maneuvering
- Aircraft
- N5333Grumman G-164A
- Status
- Completed · report June 25, 1973
- Report
- Brief approved by the director
- FAA report
- 19730604012329A
- Case key
- 190524
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-1214 73/6/4 MINTER CITY,MISS GRUMMAN G-164A CR- 0 0 1 COMMERCIAL AIRLINE TRANSPORT, AGE TIME - 1500 N5333 PX- 0 0 0 AERIAL APPLICATION 30, 3140 TOTAL HOURS, 300 DAMAGE-DESTROYED OT- 0 0 0 IN TYPE, NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION MINTER CITY,MISS LOCAL TYPE OF ACCIDENT PHASE OF OPERATION STALL: MUSH IN FLIGHT: PULLUP FROM SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED FACTOR(S) TERRAIN - HIGH OBSTRUCTIONS SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 1200 KIND OF OPERATION - FERTILIZING (DUST) KIND OF CROP - RICE TYPE OF CHEMICAL USED - DRY CHEMICAL-NONTOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - NOT USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 110 SWATH RUN-HOW FLOWN - DOWNWIND PROCEDURE TURNAROUND - SECOND 1/3 TURN REMARKS- DNWND SWATH RUN.ADDED FULL PWR TO CLR TREES APRX 40FT HI,UN CK DSCNT.
Aircraft
- Registration
- N5333
- Reported as
- Grumman G-164A
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
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.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.
Other investigations on N5333 · 2
Matched to the same aircraft by N-number and date.