- Date
- November 25, 1972
- Place
- Jacksonville, FL · JACKSONVILLE, FL
- Injuries
- 4 fatal
- Damage
- Destroyed
- Phase of flight
- Approach
- Aircraft
- N5908YPiper PA-23
- Status
- Completed · report March 23, 1973
- Report
- Brief approved by the director
- Case key
- 169374
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-3715 72/11/25 JACKSONVILLE,FLA PIPER PA-23 CR- 2 0 0 NONCOMMERCIAL PRIVATE, AGE 49, 750 TIME - 1758 N5908Y PX- 2 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 400 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - JACKSONVILLE INTL DEPARTURE POINT INTENDED DESTINATION TRI-CITIES,TENN JACKSONVILLE,FLA TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: TREES LANDING: FINAL APPROACH PROBABLE CAUSE(S) PILOT IN COMMAND - IMPROPER IFR OPERATION FACTOR(S) WEATHER - LOW CEILING WEATHER - RAIN TERRAIN - HIGH OBSTRUCTIONS WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, IN PERSON WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE BROKEN 500 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 1/2 MILE OR LESS RAIN OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F SMOKE 63 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 160 9 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR IFR FIRE AFTER IMPACT REMARKS- HIT TREES APRX 2.5MI FRM END OF RWY DRG ILS APCH.
Aircraft
- Registration
- N5908Y
- Reported as
- Piper PA-23
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Jacksonville Intl
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.