- Date
- July 23, 1966
- Place
- Picayune, MS · PICAYUNE, MS
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N2925KLuscombe 8F
- Status
- Completed · report August 24, 1966
- Report
- Brief approved by the director
- Case key
- 121968
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-1859 66/7/23 PICAYUNE MISS LUSCOMBE 8F CR- 0 0 2 INSTRUCTIONAL COMMERCIAL, AGE 45, 824 TIME - 1345 N2925K PX- 0 0 0 DUAL TOTAL HOURS, 235 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - PICAYUNE MUNICIPA TYPE OF ACCIDENT PHASE OF OPERATION GROUND-WATER LOOP-SWERVE LANDING: ROLL COLLIDED WITH: FENCE,FENCEPOSTS LANDING: ROLL PROBABLE CAUSE(S) DUAL STUDENT - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS PILOT IN COMMAND - INADEQUATE SUPERVISION OF FLIGHT FACTOR(S) WEATHER - UNFAVORABLE WIND CONDITIONS WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY RADIO WEATHER FORECAST - UNKNOWN/NOT REPORTED SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED 10000 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE RELATIVE BEARING OF WIND HAZE RIGHT CROSS WIND 068-112 DEGREES TEMPERATURE-F WIND DIRECTION-DEGREES 82 130 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 14 VFR TYPE OF FLIGHT PLAN VFR
Aircraft
- Registration
- N2925K
- Reported as
- Luscombe 8F
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Picayune Municipa
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.