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

Mooney M20C accident near Santa Fe, New Mexico, November 27, 2018

On November 27, 2018 at about 2:50 am local time, a 1966 Mooney M20C, registered N113TA, was destroyed in an accident near Santa Fe, New Mexico (Santa Fe Municipal airport). It was a positioning flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

Collision with terrain for reasons that could not be determined based on the available information. Contributing to the accident was the pilot's poor preflight planning and poor decision to depart on the accident flight.

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

What the record shows

Date
November 27, 2018 · about 2:50 am local time · cases in 2018
Place
Santa Fe, New Mexico · Santa Fe Municipal · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Mooney M20C No Series, built 1966 · all M20Cs on the register
Registration
N113TA · no longer on the register · serial 3402
Damage
Destroyed
Flight
Positioning flight · general aviation rules (Part 91)

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

The private pilot departed on a cross-country flight which continued into night visual meteorological conditions across sparsely-populated terrain. The destination airport was located about 600 nautical miles (nm) northeast of the departure airport; however, the airplane impacted terrain almost 5 hours after takeoff near an airport about 330 nm east-northeast of the departure airport and about 120 nm east-southeast of a direct course between the departure and destination airports. The airplane's route of flight could not be determined; however, the location of the accident site suggests that the pilot had become lost at some point during the flight. Investigators were not able to determine what, if any route of flight planning was conducted by the pilot prior to the flight. A witness near the accident site saw the airplane flying over the airport with "no lights whatsoever." His perception was that the pilot was not trying to land, but may have been trying to attract the attention of the tower controller. The landing gear and wing flaps appeared to be retracted, and the engine was running smoothly. The airplane impacted a ravine about 1/3-mile south of the airport and was destroyed by impact forces and a postimpact fire. Postaccident airframe and engine examinations did not reveal any anomalies consistent with a preimpact failure or malfunction; however, portions of the airplane were damaged by the postimpact fire to the extent that a complete examination of some airplane systems, such as the electrical system, were not possible. The airplane did not have a current annual inspection, nor had the pilot requested a ferry permit for the flight. Based on the available information, the reason the pilot was circling the airport and the airplane's subsequent impact with terrain could not be determined. It is likely the pilot became lost at some point during the flight and the airplane was likely near its fuel endurance limit at the time of the accident. The pilot may have been trying to orient himself by circling the airport or was attempting to alert the tower controller before setting up for a landing. However, the investigation was unable to determine whether a loss of control preceded the impact with terrain or whether the pilot became low on a landing approach.

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. Unknown or undetermined during unknown defining event
  2. Collision with terrain or object (not controlled flight into terrain) during unknown

The NTSB's findings

  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • factor Personnel issues › Task performance › Planning/preparation › Flight planning/navigation › Pilot
  • factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,200 hours in all
  • Medical certificate: None
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 2,189 hours
  • Last inspection: annual inspection, July 7, 2013
  • Maximum gross weight: 2,575 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Lycoming O-360-A1D (piston); 2,189 hours total
  • Fire on the ground

The flight

  • Departed from: GYR Goodyear AZ at 10:00 pm
  • Destination: AKO Akron CO
  • Flight plan: none
  • Runway 2, 8,366 ft by 150 ft

Weather at the time

  • Light: night
  • Wind: from 360° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 30°F (-1°C), dew point 7°F (-14°C)
  • Altimeter: 30.22 inHg
  • Observation at 2:53 am from SAF, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Photographs from the investigation 10 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

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

13 documents, released by the NTSB on April 20, 2020. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Witness Statements PDF, 3 pages · our copy View Download
2 Conversation Record -- Friend of Pilot PDF, 1 page · our copy View Download
3 Exemplar Flight Route PDF, 1 page · our copy View Download
4 Summary of Airplane Examination PDF, 3 pages · our copy View Download
5 Report Photos PDF, 10 pages · our copy View Download
6 Maintenance Records -- Airframe/engine PDF, 11 pages · our copy View Download
7 Maintenance Records -- Propeller PDF, 6 pages · our copy View Download
8 FAA Chart Supplement -- Santa Fe Municipal Arpt PDF, 2 pages · our copy View Download
9 Weather Documentation -- Santa Fe Municipal Arpt PDF, 2 pages · our copy View Download
10 Sun and Moon Data -- Santa Fe PDF, 1 page · our copy View Download
11 Toxicological Report PDF, 1 page · our copy View Download
12 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page · our copy View Download
13 Personal Electronic Device - Specialist's Factual Report PDF, 4 pages · our copy View Download

The same docket at the NTSB.

Other NTSB records under N113TA the same tail number, which may have belonged to a different aircraft at the time

2010-05-13ERA10CA264 · accident near Ormond Beach, FL · substantial damage · no injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/CEN19FA032.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.