- Date
- July 9, 1968
- Place
- Stehekin, WA · STEHEKIN, WA
- Injuries
- 4 fatal
- Damage
- Destroyed
- Phase of flight
- Initial climb
- Aircraft
- N2854LCessna 172H
- Status
- Completed · report March 11, 1969
- Report
- Brief approved by the director
- Case key
- 109640
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-4597 68/7/9 STEHEKIN,WASH CESSNA 172H CR- 1 0 0 NONCOMMERCIAL COMMERCIAL, AGE 42, 305 TIME - 1650 N2854L PX- 3 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 75 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - STEHEKIN TYPE OF ACCIDENT PHASE OF OPERATION STALL TAKEOFF: INITIAL CLIMB PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED FACTOR(S) WEATHER - HIGH DENSITY ALTITUDE TERRAIN - HIGH OBSTRUCTIONS AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: OTHER 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 TEMPERATURE-F NONE 82 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 360 15 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE FIRE AFTER IMPACT REMARKS- STATE OWNED EMGCY LNDG STRIP.DENSITY ALT 3030 FT.ROUGH,UPSLOPE RNWY.HIGH TREES BEYOND RNWY OVERRUN
Aircraft
- Registration
- N2854L
- Reported as
- Cessna 172H
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Stehekin
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.