- Date
- May 31, 1972
- Place
- Talihina, OK · TALIHINA, OK
- Injuries
- 3 uninjured
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N9437SBeech 35
- Status
- Completed · report February 15, 1973
- Report
- Brief approved by the director
- Case key
- 167453
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-2188 72/5/31 TALIHINA,OKLA BEECH 35 CR- 0 0 3 NONCOMMERCIAL PRIVATE, AGE 39, 755 TIME - 1500 N9437S PX- 0 0 0 BUSINESS TOTAL HOURS, 9 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - DRESSER STRIP DEPARTURE POINT INTENDED DESTINATION TALIHINA,OKLA OKLAHOMA CITY,OKLA TYPE OF ACCIDENT PHASE OF OPERATION STALL: MUSH TAKEOFF: INITIAL CLIMB PROBABLE CAUSE(S) PILOT IN COMMAND - PREMATURE LIFT-OFF FACTOR(S) AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: OTHER WEATHER - HIGH TEMPERATURE AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: HIGH VEGETATION WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE CLEAR UNLIMITED VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F NONE 82 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE REMARKS- RWY BUMPY WITH HI GRASS. BECAME AIRBORNE AND VEERED L INTO FENCE.
Aircraft
- Registration
- N9437S
- Reported as
- Beech 35
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Dresser Strip
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.