- Date
- November 7, 1969
- Place
- Accident, MD · ACCIDENT, MD
- Injuries
- 2 fatal, 1 serious
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N5765RCessna 172G
- Status
- Completed · report January 19, 1970
- Report
- Brief approved by the director
- Case key
- 180903
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-2800 69/11/7 ACCIDENT,MD CESSNA 172G CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 20, 200 TIME - 2215 N5765R PX- 1 1 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 83 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION PITTSBURGH,PA COLLEGE PARK,MD TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: TREES IN FLIGHT: OTHER PROBABLE CAUSE(S) PILOT IN COMMAND - ATTEMPTED OPERATION BEYOND EXPERIENCE/ABILITY LEVEL PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - MISJUDGED ALTITUDE AND CLEARANCE WEATHER - LOW CEILING WEATHER - FOG WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, IN PERSON WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED 0 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE ZERO DRIZZLE OBSTRUCTIONS TO VISION AT ACCIDENT SITE WIND VELOCITY-KNOTS FOG CALM TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR VFR REMARKS- MTN RIDGES OBSCD,ACFT STRUCK TREE APRX 40FT AGL.
Aircraft
- Registration
- N5765R
- Reported as
- Cessna 172G
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
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.