- Date
- June 29, 1966
- Place
- Bakersville, NC · BAKERSVILLE, NC
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N7234TCessna 172
- Status
- Completed · report August 24, 1966
- Report
- Brief approved by the director
- Case key
- 170835
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-1729 66/6/29 BAKERSVILLE NC CESSNA 172 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 38, 565 TIME - 1415 N7234T PX- 0 0 1 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 237 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES LANDING: FINAL APPROACH PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS FACTOR(S) WEATHER - LOW CEILING WEATHER - THUNDERSTORM ACTIVITY WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, IN PERSON WEATHER FORECAST - WEATHER SLIGHTLY WORSE THAN FORECAST EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING OFF AIRPORT LOW ON FUEL ADVERSE/UNFAVORABLE WEATHER SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED UNKNOWN/NOT REPORTED VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 4 MILES OR LESS RAIN OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F HAZE 75 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR VFR FLIGHT FOLLOWING SERVICE
Aircraft
- Registration
- N7234T
- Reported as
- Cessna 172
- 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.