- Date
- March 13, 1972
- Place
- Shishmaref, AK · SHISHMAREF, AK
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N2604YCessna 180
- Status
- Completed · report February 7, 1973
- Report
- Brief approved by the director
- Case key
- 166272
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-1561 72/3/13 SHISHMAREF,ALAS CESSNA 180 CR- 0 0 1 NONCOMMERCIAL COMMERCIAL, AGE 38, 1500 TIME - 0900 N2604Y PX- 0 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, ALL IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - SHISHMAREF DEPARTURE POINT INTENDED DESTINATION SHISHMAREF,ALAS LOCAL TYPE OF ACCIDENT PHASE OF OPERATION GROUND-WATER LOOP-SWERVE LANDING: ROLL COLLIDED WITH: OBJECT LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL FACTOR(S) WEATHER - UNFAVORABLE WIND CONDITIONS TERRAIN - HIGH OBSTRUCTIONS 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 WIND DIRECTION-DEGREES NONE 310 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 12 VFR TYPE OF FLIGHT PLAN NONE REMARKS- ACFT HIT A FUEL STORAGE TANK.WIND GUSTING 20K.
Aircraft
- Registration
- N2604Y
- Reported as
- Cessna 180
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Shishmaref
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.