- Date
- July 7, 1965
- Place
- Fenton, MI · FENTON, MI
- Injuries
- 3 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N2011XCessna 182
- Status
- Completed · report September 20, 1965
- Report
- Brief approved by the director
- Case key
- 176497
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-2211 65/7/7 FENTON MICH CESSNA 182 CR- 0 0 1 COMMERCIAL COMMERCIAL, FL.INSTR., TIME - 1200 N2011X PX- 0 0 2 AIR TAXI-PASSG AGE 27, 1181 TOTAL HOURS, DAMAGE-SUBSTANTIAL OT- 0 0 0 58 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - AERO ACRES TYPE OF ACCIDENT PHASE OF OPERATION OVERSHOOT LANDING: ROLL COLLIDED WITH: DITCHES LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - SELECTED WRONG RUNWAY RELATIVE TO EXISTING WIND PILOT IN COMMAND - FAILED TO INITIATE GO-AROUND FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND WEATHER - LOW CEILING WEATHER - RAIN WEATHER BRIEFING - SELF-HELP,PILOT CHECKED WEATHER DATA WEATHER FORECAST - UNKNOWN/NOT REPORTED EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING ON AIRPORT SKY CONDITION CEILING AT ACCIDENT SITE OVERCAST 600 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 2 MILES OR LESS RAIN RELATIVE BEARING OF WIND TEMPERATURE-F TAIL WIND 158-202 DEGREES 65 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 180 15 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR NONE
Aircraft
- Registration
- N2011X
- Reported as
- Cessna 182
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Aero Acres
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.