- Date
- July 5, 1969
- Place
- Grnd Canyon, AZ · GRND CANYON, AZ
- Injuries
- 2 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N4649JPiper PA-28R
- Status
- Completed · report February 6, 1970
- Report
- Brief approved by the director
- Case key
- 165401
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-2917 69/7/5 NR.GRND CANYON,ARIZ PIPER PA-28R CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 44, 201 TIME - 0900 N4649J PX- 1 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 12 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION GRND CANYON,ARIZ BRYCE CANYON,UT TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: TREES IN FLIGHT: CLIMB TO CRUISE PROBABLE CAUSE(S) PILOT IN COMMAND - IMPROPER IN-FLIGHT DECISIONS OR PLANNING FACTOR(S) AIRFRAME - LANDING GEAR: NORMAL RETRACTION/EXTENSION ASSEMBLY WEATHER - HIGH DENSITY ALTITUDE 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 TYPE OF WEATHER CONDITIONS NONE VFR TYPE OF FLIGHT PLAN NONE FIRE AFTER IMPACT REMARKS- PLT SHOULD HAVE RETURNED TO ARPT OR CHOSE LOWER ALT.REPORTED DIFFICULT TO CLIMB,GR WILL NOT RETRCT
Aircraft
- Registration
- N4649J
- Reported as
- Piper PA-28R
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
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.