- Date
- August 7, 1968
- Place
- Glendive, MT · GLENDIVE, MT
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N5224DCessna 180
- Status
- Completed · report January 2, 1969
- Report
- Brief approved by the director
- Case key
- 108597
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-3808 68/8/7 GLENDIVE,MONT CESSNA 180 CR- 0 0 1 MISCELLANEOUS PRIVATE, AGE 53, 220 TIME - 1400 N5224D PX- 0 0 0 TOWING GLIDERS TOTAL HOURS, 18 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - HILGER FIELD TYPE OF ACCIDENT PHASE OF OPERATION GROUND-WATER LOOP-SWERVE LANDING: ROLL GEAR COLLAPSED LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL FACTOR(S) WEATHER - UNFAVORABLE WIND CONDITIONS MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - UNKNOWN/NOT REPORTED 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 350 15 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE REMARKS- RT QUARTERING HEAD WIND 40 DEG 15 K GUSTING.
Aircraft
- Registration
- N5224D
- Reported as
- Cessna 180
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Hilger Field
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.