- Date
- January 21, 1971
- Place
- Watford Cty, ND · WATFORD CTY, ND
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N35583Cessna 172
- Status
- Completed · report December 2, 1971
- Report
- Brief approved by the director
- Case key
- 159843
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-0649 71/1/21 WATFORD CTY,N DAK CESSNA 172 CR- 0 0 1 NONCOMMERCIAL STUDENT, AGE 37, 118 TIME - 1700 N35583 PX- 0 0 0 BUSINESS TOTAL HOURS, 10 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - WATFORD CITY DEPARTURE POINT INTENDED DESTINATION MINOT,N DAK WATFORD CTY,N DAK TYPE OF ACCIDENT PHASE OF OPERATION GROUND-WATER LOOP-SWERVE LANDING: ROLL NOSE OVER/DOWN LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL FACTOR(S) WEATHER - UNFAVORABLE WIND CONDITIONS WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, IN PERSON 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 RELATIVE BEARING OF WIND NONE LEFT QUARTERING HEAD WIND 293-337 DEGREES WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 250 13 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR VFR
Aircraft
- Registration
- N35583
- Reported as
- Cessna 172
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Watford City
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.