- Date
- November 30, 1967
- Place
- Enid, OK · ENID, OK
- Injuries
- 2 fatal
- Damage
- Destroyed
- Phase of flight
- Uncontrolled descent
- Aircraft
- N6020PPiper PA-24
- Status
- Completed · report May 7, 1968
- Report
- Brief approved by the director
- Case key
- 113630
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-1095 67/11/30 ENID,OKLA PIPER PA-24 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 43, 247 TIME - 1155 N6020P PX- 1 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 11 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - WOODRING TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: UNCONTROLLED IN FLIGHT: UNCONTROLLED DESCENT PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - SPATIAL DISORIENTATION FACTOR(S) WEATHER - LOW CEILING WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT EMERGENCY CIRCUMSTANCES - LOW ON FUEL SKY CONDITION CEILING AT ACCIDENT SITE OVERCAST 800 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F NONE 38 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 140 6 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR VFR REMARKS- NON INST PLT CONTINUED ON TOP OF OVERCAST.CRASHED ATTEMPTING FORMATION LET DOWN WITH AF CESSNA 310
Aircraft
- Registration
- N6020P
- Reported as
- Piper PA-24
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Woodring
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.