- Date
- September 30, 1966
- Place
- Richmond, IN · RICHMOND, IN
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N3368XMooney M20E
- Status
- Completed · report January 10, 1967
- Report
- Brief approved by the director
- Case key
- 120849
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-3309 66/9/30 RICHMOND IND MOONEY M20E CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 39, 268 TIME - 1245 N3368X PX- 0 0 1 BUSINESS TOTAL HOURS, 39 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - RICHMOND MUNI TYPE OF ACCIDENT PHASE OF OPERATION HARD LANDING LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING FACTOR(S) WEATHER - RAIN WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY PHONE WEATHER FORECAST - UNKNOWN/NOT REPORTED EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING ON AIRPORT ADVERSE/UNFAVORABLE WEATHER SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED 800 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 2 MILES OR LESS RAIN OBSTRUCTIONS TO VISION AT ACCIDENT SITE RELATIVE BEARING OF WIND NONE HEAD WIND 338-022 DEGREES TEMPERATURE-F WIND DIRECTION-DEGREES 59 240 WIND VELOCITY-KNOTS TYPE OF WEATHER CONDITIONS 7 VFR TYPE OF FLIGHT PLAN NONE REMARKS- PROPELLER STRUCK RUNWAY.
Aircraft
- Registration
- N3368X
- Reported as
- Mooney M20E
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Richmond Muni
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.