- Date
- October 29, 1964
- Place
- Shelbyville, TN · SHELBYVILLE, TN
- Injuries
- 3 fatal
- Damage
- Destroyed
- Phase of flight
- Approach
- Aircraft
- N3799BBeechcraft C-50
- Status
- Completed · report April 2, 1965
- Report
- Brief approved by the director
- Case key
- 181190
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-0954 64/10/29 SHELBYVILLE TENN BEECHCRAFT C-50 CR- 1 0 0 NONCOMMERCIAL COMMERCIAL, AGE 33, 4010 TIME - 0850 N3799B PX- 2 0 0 CORP/EXEC TOTAL HOURS, 230 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - BOMAR TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: TREES LANDING: INITIAL APPROACH PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - EXERCISED POOR JUDGMENT PILOT IN COMMAND - IMPROPER IFR OPERATION FACTOR(S) WEATHER - FOG WEATHER - LOW CEILING WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OVERCAST 250 VISIBILITY AT ACCIDENT SITE OBSTRUCTIONS TO VISION AT ACCIDENT SITE 3 MILES OR LESS FOG TEMPERATURE-F WIND DIRECTION-DEGREES 57 180 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 7 IFR TYPE OF FLIGHT PLAN NONE FIRE AFTER IMPACT REMARKS- PILOT ATTEMPTD IFR APP ON MHW NON-DIR RADI BCN FOR WHICH THERE IS NO PUBLISHED LET-DOWN PROCEDURE.
Aircraft
- Registration
- N3799B
- Reported as
- Beechcraft C-50
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Bomar
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.