- Date
- March 4, 1967
- Place
- Bethlehem, IN · BETHLEHEM, IN
- Injuries
- 4 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N5688PPiper PA-24
- Status
- Completed · report August 10, 1967
- Report
- Brief approved by the director
- Case key
- 118485
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-0671 67/3/4 BETHLEHEM, IND PIPER PA-24 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 52, 230 TIME - 1330 N5688P PX- 0 0 3 BUSINESS TOTAL HOURS, 26 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: FENCE,FENCEPOSTS LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS FACTOR(S) WEATHER - LOW CEILING WEATHER - RAIN WEATHER - FOG WEATHER BRIEFING - BRIEFING RECEIVED-METHOD UNKNOWN WEATHER FORECAST - UNKNOWN/NOT REPORTED EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING OFF AIRPORT ADVERSE/UNFAVORABLE WEATHER SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED 400 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 1 MILE OR LESS RAIN OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS FOG IFR TYPE OF FLIGHT PLAN NONE REMARKS- PLT FLEW INTO FOG BANK.
Aircraft
- Registration
- N5688P
- Reported as
- Piper PA-24
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
N5688PRegistration cancelled Jan 30, 2021 · Piper PA-24-250Airframe modelPiper PA-24-250Engine modelLycoming 0-540 series
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.