- Date
- April 5, 1970
- Place
- Lafayette, IN · LAFAYETTE, IN
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N25347Luscombe 8C
- Status
- Completed · report January 7, 1971
- Report
- Brief approved by the director
- Case key
- 128399
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-1602 70/4/5 LAFAYETTE,IND LUSCOMBE 8C CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 45, 155 TIME - 1020 N25347 PX- 0 0 1 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 58 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - ARETZ DEPARTURE POINT INTENDED DESTINATION BROWNSBURG,IND LAFAYETTE,IND TYPE OF ACCIDENT PHASE OF OPERATION HARD LANDING LANDING: LEVEL OFF/TOUCHDOWN NOSE OVER/DOWN LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - IMPROPER LEVEL OFF PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING FACTOR(S) WEATHER - UNFAVORABLE WIND CONDITIONS WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - UNKNOWN/NOT REPORTED 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 RELATIVE BEARING OF WIND NONE RIGHT CROSS WIND 068-112 DEGREES TEMPERATURE-F WIND DIRECTION-DEGREES 42 160 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 10 VFR TYPE OF FLIGHT PLAN NONE
Aircraft
- Registration
- N25347
- Reported as
- Luscombe 8C
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Aretz
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.