- Date
- August 1, 1968
- Place
- Fayetteville, TN · FAYETTEVILLE, TN
- Injuries
- 1 serious
- Damage
- Destroyed
- Phase of flight
- Initial climb
- Aircraft
- N2411PPiper PA-18A
- Status
- Completed · report October 21, 1968
- Report
- Brief approved by the director
- Case key
- 108961
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-2911 68/8/1 FAYETTEVILLE,TENN PIPER PA-18A CR- 0 1 0 COMMERCIAL ATP,FLIGHT INSTR., AGE TIME - 1514 N2411P PX- 0 0 0 ASSOC CROP CTL ACTIVITY 32, 5800 TOTAL HOURS, 150 DAMAGE-DESTROYED OT- 0 0 0 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - FAYETTEVILLE TYPE OF ACCIDENT PHASE OF OPERATION STALL: MUSH TAKEOFF: INITIAL CLIMB PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - IMPROPERLY LOADED AIRCRAFT-WEIGHT-AND/OR C.G. SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 19 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - COTTON TYPE OF CHEMICAL USED - LIQUID CHEMICAL-NONTOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - NOT USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - AFT OF PILOT ELEVATION-AREA BEING TREATED-FEET - 983 REMARKS- FORWARD C.G.LIMIT EXCEEDED.
Aircraft
- Registration
- N2411P
- Reported as
- Piper PA-18A
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Fayetteville
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.