- Date
- April 17, 1965
- Place
- Johnstown, PA · JOHNSTOWN, PA
- Injuries
- 2 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N7397PPiper PA-24
- Status
- Completed · report September 6, 1965
- Report
- Brief approved by the director
- Case key
- 179300
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 ---------------------------------------------------------------------------------------------------------------------------- 2-0361 65/4/17 NR.JOHNSTOWN PA PIPER PA-24 CR- 1 0 0 COMMERCIAL COMMERCIAL, FL.INSTR., TIME - 1945 N7397P PX- 1 0 0 AIR TAXI-PASSG AGE 38, 10000 TOTAL DAMAGE-DESTROYED OT- 0 0 0 HOURS, 224 IN TYPE, NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: TREES IN FLIGHT: NORMAL CRUISE COLLISION WITH GROUND/WATER: UNCONTROLLED IN FLIGHT: UNCONTROLLED DESCENT PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - EXERCISED POOR JUDGMENT FACTOR(S) WEATHER - LOW CEILING WEATHER - RAIN WEATHER - FOG WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT MISSING AIRCRAFT - LATER RECOVERED SKY CONDITION CEILING AT ACCIDENT SITE OVERCAST 1000 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 2 MILES OR LESS RAIN OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F FOG 53 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 350 25 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR NONE REMARKS- RECOVERY DATE-04/21/65
Aircraft
- Registration
- N7397P
- Reported as
- Piper PA-24
- 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.