- Date
- December 1, 1971
- Place
- Rutledge, MO · RUTLEDGE, MO
- Injuries
- 2 fatal, 3 uninjured
- Phase of flight
- Enroute
- Status
- Completed · report May 25, 1972
- Report
- Brief approved by the director
- Case key
- 164983
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-3871 71/12/1 NR.RUTLEDGE,MO MOONEY M20E CR- 2 0 0 NONCOMMERCIAL COMMERCIAL, FL.INSTR., TIME - 1123 N6038Q PX- 0 0 0 BUSINESS AGE 20, 1056 TOTAL HOURS, DAMAGE-DESTROYED OT- 0 0 3 55 IN TYPE, INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION CHILLICOTHE,MO BLOOMINGTON,ILL TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH AIRCRAFT: BOTH IN FLIGHT IN FLIGHT: NORMAL CRUISE PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO SEE AND AVOID OTHER AIRCRAFT PERSONNEL - MISCELLANEOUS-PERSONNEL: PILOT OF OTHER AIRCRAFT FACTOR(S) WEATHER - OBSTRUCTIONS TO VISION MISSING AIRCRAFT - LATER RECOVERED SKY CONDITION CEILING AT ACCIDENT SITE BROKEN 1200 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F HAZE 35 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE SPECIAL DATA SEGMENTS OF AVIATION INVOLVED - SMALL US GEN.AV.-SMALL US GEN.AV. CONTROLLING AGENCY - NO CONTROL RADAR CTL/SURVEILLANCE - UNKNOWN/NOT REPORTED TRAFFIC ADVISORY ISSUED - NONE CONTROL ZONE/AREA - UNKNOWN/NOT REPORTED EVASIVE ACTION TAKEN - NO ANTI-COLLISION LIGHTS - INSTALLED,OPERATION UNKNOWN REMARKS- COLLIDED ALMOST HEAD ON. M20E VERT STAB AND RUDDER SEPARATED. RECOVERY DATE 12/2/71.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-3871 71/12/1 NR.RUTLEDGE,MO PIPER PA-28 CR- 0 0 2 INSTRUCTIONAL COMMERCIAL, FL.INSTR., TIME - 1123 N3393R PX- 0 0 1 DUAL AGE 45, 7101 TOTAL HOURS, DAMAGE-SUBSTANTIAL OT- 2 0 0 20 IN TYPE, INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION MOLINE,ILL KIRKSVILLE,MO TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH AIRCRAFT: BOTH IN FLIGHT IN FLIGHT: NORMAL CRUISE PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO SEE AND AVOID OTHER AIRCRAFT PERSONNEL - MISCELLANEOUS-PERSONNEL: PILOT OF OTHER AIRCRAFT FACTOR(S) WEATHER - OBSTRUCTIONS TO VISION SKY CONDITION CEILING AT ACCIDENT SITE BROKEN 1200 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F HAZE 35 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE SPECIAL DATA SEGMENTS OF AVIATION INVOLVED - SMALL US GEN.AV.-SMALL US GEN.AV. CONTROLLING AGENCY - NO CONTROL RADAR CTL/SURVEILLANCE - UNKNOWN/NOT REPORTED TRAFFIC ADVISORY ISSUED - NONE CONTROL ZONE/AREA - UNKNOWN/NOT REPORTED EVASIVE ACTION TAKEN - NO ANTI-COLLISION LIGHTS - NOT OPERATING REMARKS- R GR OF PA-28 SEPARATED IN FLT. CONT TO DEST,FURTHER DMG ON LDG.
Aircraft · 2
- Registration
- N3393R
- Reported as
- Piper PA-28
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
N3393RRegistered now · Piper PA-28-180Airframe modelPiper PA-28-180Engine modelLycoming O&VO-360 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.
- Registration
- N6038Q
- Reported as
- Mooney M20E
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
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.