- Date
- January 24, 1971
- Place
- Asheboro, NC · ASHEBORO, NC
- Injuries
- 2 fatal
- Damage
- Destroyed
- Phase of flight
- Approach
- Aircraft
- N9327JPiper PA-28
- Status
- Completed · report October 20, 1971
- Report
- Brief approved by the director
- Case key
- 159438
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-0176 71/1/24 ASHEBORO,NC PIPER PA-28 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 32, 133 TIME - 1542 N9327J PX- 1 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 61 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - ASHEBORO DEPARTURE POINT INTENDED DESTINATION MYRTLE BEACH,SC UNKNOWN/NOT REPORTED TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: TREES LANDING: FINAL APPROACH PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS FACTOR(S) WEATHER - LOW CEILING WEATHER - FOG WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - WEATHER SLIGHTLY WORSE THAN FORECAST MISSING AIRCRAFT - LATER RECOVERED SKY CONDITION CEILING AT ACCIDENT SITE OBSCURATION 0 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE ZERO NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS FOG VFR TYPE OF FLIGHT PLAN NONE REMARKS- RECOVERY DATE 1/26/71. ACFT IN AND OUT OF LOW CLOUDS. NEARBY RIDGES OBSCURED. HIT TREES ON RIDGE.
Aircraft
- Registration
- N9327J
- Reported as
- Piper PA-28
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Asheboro
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.