- Date
- July 25, 1973
- Place
- Mcclellanville, SC · MCCLELLANVILLE, SC
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N6177ZPiper PA-25
- Status
- Completed · report January 29, 1974
- Report
- Brief approved by the director
- FAA report
- 19730725022489A
- Case key
- 188794
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-3586 73/7/25 MCCLELLANVILLE,SC PIPER PA-25 CR- 0 0 1 MISCELLANEOUS COMMERCIAL, AGE 35, 3235 TIME - 1630 N6177Z PX- 0 0 0 FERRY TOTAL HOURS, 650 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION MCCLELLANVILLE,SC GEORGETOWN,SC TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: EN ROUTE TO TREAT CROP COLLIDED WITH: TREES LANDING: FINAL APPROACH PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING PERSONNEL - MAINTENANCE,SERVICING,INSPECTION: INADEQUATE MAINTENANCE AND INSPECTION MISCELLANEOUS ACTS,CONDITIONS - WATER IN FUEL TERRAIN - HIGH OBSTRUCTIONS COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND REMARKS- CONTAMINATED FUEL ENGINE STOPPED.AIRCRAFT STRUCK TREES DURING FORCED LANDING ON HIGHWAY
Aircraft
- Registration
- N6177Z
- Reported as
- Piper PA-25
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
N6177ZRegistration cancelled Feb 11, 2013 · Piper PA-25Airframe modelPiper PA-25Engine modelLycoming 0-320 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.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.