- Date
- June 9, 1971
- Place
- Murfreesboro, TN · MURFREESBORO, TN
- Injuries
- 2 fatal
- Damage
- Destroyed
- Phase of flight
- Uncontrolled descent
- Aircraft
- N5115LPiper PA-28
- Status
- Completed · report December 7, 1971
- Report
- Brief approved by the director
- Case key
- 161699
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-0927 71/6/9 MURFREESBORO,TENN PIPER PA-28 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 54, 540 TIME - 1800 N5115L PX- 1 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, UNK/NR IN DAMAGE-DESTROYED OT- 0 0 0 TYPE, NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION METROPOLIS,ILL MURFREESBORO,TENN TYPE OF ACCIDENT PHASE OF OPERATION 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 - SPATIAL DISORIENTATION FACTOR(S) WEATHER - THUNDERSTORM ACTIVITY WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE BROKEN 10000 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F NONE 73 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE FIRE AFTER IMPACT REMARKS- OBSRVD COMING OUT OF CLOUD.TSHWR AT SITE 10-15MIN BEFORE CRASH.
Aircraft
- Registration
- N5115L
- Reported as
- Piper PA-28
- 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.