- Date
- April 17, 1967
- Place
- Troy, MI · TROY, MI
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N3865WPiper PA-32
- Status
- Completed · report September 5, 1967
- Report
- Brief approved by the director
- Case key
- 117632
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-1230 67/4/17 TROY,MICH PIPER PA-32 CR- 0 0 2 INSTRUCTIONAL COMMERCIAL, FL.INSTR., TIME - 1445 N3865W PX- 0 0 0 DUAL AGE 31, 7670 TOTAL HOURS, DAMAGE-SUBSTANTIAL OT- 0 0 0 101 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - BERZ T TYPE OF ACCIDENT PHASE OF OPERATION UNDERSHOOT LANDING: FINAL APPROACH GEAR COLLAPSED LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - EXERCISED POOR JUDGMENT WEATHER - UNFAVORABLE WIND CONDITIONS FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE SKY CONDITION CEILING AT ACCIDENT SITE CLEAR UNLIMITED VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F NONE 65 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 270 45 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE REMARKS- INSTRUCTOR CONTINUED LOCAL FLIGHT UNTIL WIND CONDITIONS EXCEEDED ACFT PERFORMANCE CAPABILITY.
Aircraft
- Registration
- N3865W
- Reported as
- Piper PA-32
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Berz T
N3865WRegistered now · Piper PA-32-260Airframe modelPiper PA-32-260Engine 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.