- Date
- January 18, 1968
- Place
- Harding, SD · HARDING, SD
- Injuries
- 4 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N8057ACessna 170
- Status
- Completed · report March 7, 1968
- Report
- Brief approved by the director
- Case key
- 112210
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-0068 68/1/18 HARDING,S DAK CESSNA 170 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 70, 3500 TIME - 1100 N8057A PX- 0 0 3 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 160 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - TJ RANCH TYPE OF ACCIDENT PHASE OF OPERATION GROUND-WATER LOOP-SWERVE LANDING: ROLL GEAR COLLAPSED LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS WEATHER - UNFAVORABLE WIND CONDITIONS FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE 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 RELATIVE BEARING OF WIND NONE RIGHT QUARTERING HEAD WIND 023-067 DEGREES WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 225 30 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE REMARKS- RT QUARTERING HEADWIND 30K,GUSTING.
Aircraft
- Registration
- N8057A
- Reported as
- Cessna 170
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Tj Ranch
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.