- Date
- August 23, 1979
- Place
- Bluffton, OH · BLUFFTON, OH
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Approach
- Aircraft
- N27715Piper PA-31
- Status
- Completed · report April 29, 1980
- Report
- Brief approved by the director
- FAA report
- 19790823040699A
- Case key
- 133762
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-3529 79/8/23 BLUFFTON,OH PIPER PA-31 CR- 1 0 0 COMMERCIAL ATP,FLIGHT INSTR., AGE TIME - 0038 N27715 PX- 0 0 0 AIR TAXI-CARGO 36, 3555 TOTAL HOURS, 500 DAMAGE-DESTROYED OT- 0 0 0 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - BLUFFTON DEPARTURE POINT INTENDED DESTINATION YPSILANTI,MI BLUFFTON,OH TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: UNCONTROLLED LANDING: FINAL APPROACH PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - SPATIAL DISORIENTATION FACTOR(S) WEATHER - LOW CEILING WEATHER - FOG WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY RADIO 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 RELATIVE BEARING OF WIND FOG LIGHT AND VARIABLE TEMPERATURE-F TYPE OF WEATHER CONDITIONS 67 BELOW MINIMUMS TYPE OF FLIGHT PLAN NONE FIRE AFTER IMPACT
Aircraft
- Registration
- N27715
- Reported as
- Piper PA-31
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Bluffton
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.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.