- Date
- March 26, 1972
- Place
- Clarksville, AR · CLARKSVILLE, AR
- Injuries
- 4 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N4568JPiper PA-28R
- Status
- Completed · report November 3, 1972
- Report
- Brief approved by the director
- Case key
- 165811
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-0596 72/3/26 CLARKSVILLE,ARK PIPER PA-28R CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 41, 183 TIME - 1635 N4568J PX- 3 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 176 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION CLARKSVILLE,ARK KANSAS CITY,MO TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: CONTROLLED IN FLIGHT: CLIMB TO CRUISE PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS FACTOR(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING WEATHER - LOW CEILING WEATHER - FOG TERRAIN - HIGH OBSTRUCTIONS WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE OBSCURATION 0 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE ZERO NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F FOG 36 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 135 7 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE REMARKS- FLEW INTO OBSCURED MTN SLOPE.
Aircraft
- Registration
- N4568J
- 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.