The U.S. aircraft register, updated daily
Accidents · NTSB CEN14FA042 · Final report

Piper PA-32R-301 accident near Kirksville, Missouri, November 6, 2013

On November 6, 2013 at about 1:12 am local time, a 1981 Piper PA-32R-301, registered N408DM, was destroyed in an accident during approach (IFR final approach) near Kirksville, Missouri (Kirksville Regional Airport). It was an instructional flight under general aviation rules (Part 91). 2 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

A loss of control due to spatial disorientation. Contributing to the accident were the private pilot's impairment due to a sedating antihistamine and both pilots' fatigue.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 6, 2013 · about 1:12 am local time
Place
Kirksville, Missouri · Kirksville Regional Airport · map
Type
Accident
Injuries
2 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Piper PA-32R-301, built 1981 · all PA-32R-301s on the register
Registration
N408DM · registry record · serial 32R-8113012
Damage
Destroyed
Flight
Instructional flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The flight instructor accompanied the private pilot on a business flight to provide instrument flight instruction. Dark night instrument meteorological conditions prevailed with a 15-knot headwind that was gusting to 20 knots. The pilots were cleared for an instrument approach and instructed to change to the local advisory frequency. Recorded radar data indicated that the airplane was tracking the inbound course to the airport. One of the pilots contacted the airport on the local advisory frequency and gave two position reports; the last one reported the airplane was 5 miles from the airport. There was no other communication with the pilots. It could not be determined which pilot was flying the airplane when the accident occurred. The wreckage was located about 3.5 miles north of the airport, and the initial tree impact was about 0.4 mile east of the last radar contact. The location of the accident site was consistent with the airplane turning left away from the inbound course and descending rapidly after the last radar contact. Given the dark night instrument meteorological conditions, the most likely explanation for the turn and rapid descent is that the flying pilot experienced spatial disorientation and lost control of the airplane. Examination of the accident site indicated that the airplane was in a nose-up attitude when it contacted the trees on the up sloping terrain, and it continued to climb, clearing the crest of the hill and continuing down the other side, before it came to rest. The wreckage path was consistent with a possible attempt to recover from the descent just before impacting the trees, but by then there was insufficient altitude to avoid the accident. Examination of the airplane and engine found no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. A commuter airline pilot who landed at the airport 15 minutes before the accident stated that the weather conditions were such that the lights from the radio antenna towers along the approach course illuminated the clouds around him with a white flashing light similar to airplane anti-collision lights or runway end identifier lights. If similar conditions were present during the accident airplane's approach, this phenomenon could have distracted the pilots. However, there is insufficient information to determine either the presence of this phenomenon during the accident airplane's approach or its role in this accident. The pilots began their first flight of the day about 0804, and the accident occurred on their third flight of the day at 1912. Assuming the pilots woke up about 2 hours before they began the first flight, they had been awake about 13 hours when the accident occurred. The combined flights totaled about 5 hours 46 minutes of flight time. The cumulative flight time in conjunction with the extended time since awakening most likely resulted in the pilots experiencing some level of fatigue at the time of the accident. Although the instructor's autopsy revealed that he had severe coronary artery disease, it could not be determined whether this contributed to the accident. The private pilot's toxicology results were positive for diphenhydramine, a sedating antihistamine, and impairment from this over-the-counter medication likely contributed to the accident whether he was actively flying or observing the instructor fly the approach at the time of the loss of control.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control in flight during approach (IFR final approach) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Effect on personnel
  • cause Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Instructor/check pilot
  • cause Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Student/instructed pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Personnel issues › Physical › Impairment/incapacitation › OTC medication › Student/instructed pilot

Pilot

  • Certificate: commercial pilot, flight engineer
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 10,368 hours in all; 19.1 in this make and model; 174.3 in the last 90 days; 53 in the last 30 days; 8,087.8 on instruments
  • Last flight review: October 24, 2013
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: rgt
  • Injury: fatal

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 365 hours in all
  • Last flight review: October 7, 2013
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 3,157 hours
  • Last inspection: 100-hour inspection, October 30, 2013; 12 hours since
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Lycoming IO-540-K1G5D (piston); 3,659 hours total
  • Operator: Rfg LLC

The flight

  • Departed from: APA Denver CO at 9:43 pm
  • Destination: IRK Kirksville MO
  • Flight plan: IFR
  • Runway 18, 6,005 ft by 100 ft
  • A second pilot was aboard

Weather at the time

  • Light: night, dark
  • Wind: from 170° at 15 knots, gusting 20
  • Visibility: 9 statute miles
  • Sky: overcast at 800 ft
  • Temperature: 57°F (14°C), dew point 55°F (13°C)
  • Altimeter: 29.92 inHg

Injuries

FatalSeriousMinorNone
Flight crew2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.