- Date
- June 2, 1967
- Place
- Rangely, CO · RANGELY, CO
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N4428JPiper PA-28
- Status
- Completed · report September 21, 1967
- Report
- Brief approved by the director
- Case key
- 116591
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-1834 67/6/2 RANGELY,COLO PIPER PA-28 CR- 0 0 1 INSTRUCTIONAL STUDENT, AGE 43, 38 TOTAL TIME - 1015 N4428J PX- 0 0 0 TRAINING HOURS, 23 IN TYPE, NOT DAMAGE-SUBSTANTIAL OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - RANGELY TYPE OF ACCIDENT PHASE OF OPERATION STALL: MUSH LANDING: GO-AROUND PROBABLE CAUSE(S) PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED WEATHER - UNFAVORABLE WIND CONDITIONS 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 TEMPERATURE-F WIND DIRECTION-DEGREES 73 180 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 15 VFR TYPE OF FLIGHT PLAN NONE REMARKS- 60 DEGREE LEFT XWIND 15KT.ACFT SETTLED ONTO ROUGH AREA TO RT OF RNWY.
Aircraft
- Registration
- N4428J
- Reported as
- Piper PA-28
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Rangely
N4428JRegistered now · Piper PA-28-140Airframe modelPiper PA-28-140Engine modelLycoming 0-320 series
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.