- Date
- November 20, 1965
- Place
- Pearson, OK · PEARSON, OK
- Injuries
- 1 fatal
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N29718Taylorcraft BC-12
- Status
- Completed · report October 27, 1966
- Report
- Brief approved by the director
- Case key
- 175031
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-1077 65/11/20 PEARSON OKLA TAYLORCRAFT BC-12 CR- 1 0 0 NONCOMMERCIAL NO CERTIFICATE, AGE 43, TIME - 0930 N29718 PX- 0 0 0 BUSINESS UNK/NR TOTAL HOURS, DAMAGE-SUBSTANTIAL OT- 0 0 0 UNK/NR IN TYPE, NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: NORMAL CRUISE 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 - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING MISCELLANEOUS ACTS,CONDITIONS - FUEL EXHAUSTION FACTOR(S) WEATHER - FOG COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - UNKNOWN/NOT REPORTED EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND SKY CONDITION CEILING AT ACCIDENT SITE OBSCURATION 0 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE ZERO NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS FOG IFR TYPE OF FLIGHT PLAN NONE
Aircraft
- Registration
- N29718
- Reported as
- Taylorcraft BC-12
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
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.