- Date
- September 26, 1972
- Place
- Artemus, KY · ARTEMUS, KY
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N3308FCessna 182J
- Status
- Completed · report February 28, 1973
- Report
- Brief approved by the director
- Case key
- 168599
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-2505 72/9/26 ARTEMUS,KY CESSNA 182J CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 61, 674 TIME - 1620 N3308F PX- 0 0 1 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 102 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION ROANOKE,VA LEXINGTON,KY TYPE OF ACCIDENT PHASE OF OPERATION OVERSHOOT LANDING: LEVEL OFF/TOUCHDOWN COLLIDED WITH: DITCHES LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN FACTOR(S) WEATHER - TURBULENCE, ASSOCIATED W/CLOUDS AND/OR THUNDERSTORMS TERRAIN - OTHER WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, IN PERSON WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING OFF AIRPORT ADVERSE/UNFAVORABLE WEATHER SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED 1200 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 1 MILE OR LESS NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TYPE OF WEATHER CONDITIONS HAZE IFR TYPE OF FLIGHT PLAN VFR
Aircraft
- Registration
- N3308F
- Reported as
- Cessna 182J
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
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.