Piper Aircraft INC PA-34-220T accident near New Harmony, Utah, January 4, 2023
On January 4, 2023 at about 9:56 pm local time, a 2014 Piper Aircraft INC PA-34-220T, registered N814WT, was destroyed in an accident during enroute (climb to cruise) near New Harmony, Utah. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The pilot’s decision to continue visual flight rules flight into instrument meteorological conditions, which resulted in a loss of airplane control due to spatial disorientation.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 4, 2023 · about 9:56 pm local time
- Place
- New Harmony, Utah · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Piper Aircraft INC PA-34-220T, built 2014
- Registration
- N814WT · registry record · serial 3449495
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot departed on a cross-country visual flight rules (VFR) flight on a route with which he was familiar. On the day of the accident, visual meteorological conditions (VMC) prevailed along most of the route; however, the mountain pass just north of the departure airport was obscured by low clouds and light rain. The pilot had obtained weather information before departure that would have reflected the instrument meteorological conditions (IMC), and he would have been able to see the mountain obscuration from the departure airport. Recorded data from onboard avionics revealed that, during previous flights on the accident route, the pilot typically departed and flew direct toward the destination through the mountain pass north of the departure airport, engaging the autopilot shortly after takeoff. The accident takeoff and departure were uneventful, but rather than taking the northern route through the pass as usual, the pilot chose an initial heading to the northeast, toward rising terrain. It is likely that the airplane entered IMC at this point and continued in IMC for the remainder of the flight. The airplane descended as it approached the terrain, and the pilot appeared to make corrective control inputs via the autopilot using the heading mode (HDG) function to turn left back toward the pass. The airplane responded appropriately, and once the airplane had reached the entrance of the pass, the pilot provided a series of small heading corrections toward the north. The airplane then continued on a track similar to previous flights, but veered to the left of the pass, then continued the left turn toward rising terrain. Recorded data indicated that, around this time, power was applied to both engines and the airplane started to climb, likely as a result of the terrain awareness system alerting the pilot to the rising terrain ahead. The airplane then began a series of extreme pitch and bank excursions while climbing and descending in a left turn. The airplane ultimately impacted the ground in a steep left wing- and nose-low attitude. Based on the recorded basic autopilot mode parameters, which included commanded (but not selected) altitude and bank values, the directional commands the pilot issued the autopilot could not be definitively determined; however, it is likely that, based on his use of HDG mode, he was guiding the airplane incrementally through the pass in an effort to avoid terrain and/or inclement weather. The pilot was likely attempting to negotiate the surrounding terrain by reference to the terrain awareness features of the airplane’s integrated flight display (IFD). This feature was not designed to be used as the sole source of navigation. Review of the data during the final stages of the flight indicated that the pilot was most likely disoriented and fighting against the autopilot. The autopilot was equipped with a return-to-level (LVL) safety feature, which can be activated by the pilot at any time. The LVL system works to return the airplane to a straight-and-level flight attitude. About 40 seconds before ground impact, the autopilot was turned off, and LVL mode was activated, likely by the pilot. The autopilot immediately issued commands to regain control, and although it appeared to respond, the descent and roll continued, possibly due to the pilot physically overpowering the autopilot’s control inputs via the control column. Examination of the flight control system did not reveal any anomalies that would have precluded normal operation. The recorded data indicated that both engine power levels mirrored each other during the entire flight, and damage signatures to the engine and propellers were consistent with them both producing power at the time of impact. Damage to the airplane prevented a complete assessment of the operational status of the IFD system; however, the recorded data confirmed that the autopilot was being used throughout the accident flight. The airplane was also equipped with a set of independent backup flight instruments; therefore, the pilot had the capability to disengage the autopilot and fly the airplane by reference to those instruments if needed; however, it could not be determined if he had practiced such procedures before or was current and capable of hand-flying the airplane in IMC. The weather conditions at the accident site were conducive to the accretion of airframe icing, and although the airplane was equipped with deicing equipment, whether it was in use during the flight could not be determined. The system’s operation was not automatic and would have required manual activation by the pilot at regular intervals, which would have represented additional workload and a diversion of his attention as he attempted to maneuver through the terrain. The pilot had no urgent personal activities that would have required him to return that day, but he was aware of the incoming weather system (which persisted for a few days after the accident), and he had a vacation planned for the following week. Returning by car would have resulted in a relatively long drive of over 300 miles. Although the pilot held an instrument rating, no pilot logbooks were available to review, and his recency of instrument flight experience could not be determined. Given his familiarity with the accident route of flight and the isolated nature of the IMC along the route, it is likely that the pilot became overconfident in the airplane’s automation to navigate through the relatively small area of mountain obscuration. The airplane’s erratic pitch and bank excursions just before the accident are consistent with the known effects of pilot spatial disorientation, and the pilot’s susceptibility to the development of spatial disorientation would have increased with a lack of recent IFR flight experience. Based on the available information, it is likely that the pilot’s decision to continue the visual flight rules flight into IMC resulted in his spatial disorientation, a subsequent loss of airplane control, and impact with terrain.
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
- Loss of visual reference during enroute (climb to cruise)
- VFR encounter with IMC during enroute (climb to cruise) defining event
- Loss of control in flight during enroute
- Collision with terrain or object (not controlled flight into terrain) during enroute
The NTSB's findings
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below VFR minima › Effect on personnel
- Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Pilot
- Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
Pilot
- Certificate: private
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 2,625 hours in all; 2,000 in this make and model
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 483.2 hours
- Last inspection: annual inspection, April 29, 2022; 30 hours since
- Maximum gross weight: 4,750 lb
- Seats: 6
- Landing gear: retractable
- Engine 1: Cont Motor TSIO-360-RB5B (piston); 513 hours total
- Engine 2: Cont Motor LTSIO-360-RB5 (piston); 513 hours total
The flight
- Departed from: SGU St George UT at 9:39 pm
- Destination: SLC Salt Lake City UT
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 220° at 11 knots
- Visibility: 10 statute miles
- Sky: a few clouds at 12,000 ft
- Temperature: 36°F (2°C), dew point 32°F (0°C)
- Altimeter: 30.17 inHg
- Observation at 2:53 pm from KCDC, 14 miles away
Weather report (METAR): METAR KCDC 042153Z AUTO 22011KT 10SM FEW120 02/00 A3017 RMK AO2 SLP234 T00170000=
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
16 documents, released by the NTSB on March 19, 2025. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Meteorology Specialist's Factual Report | PDF, 19 pages · our copy | View Download |
| 2 | Onsite Exam Report | PDF, 7 pages · our copy | View Download |
| 3 | Examination Report | PDF, 22 pages · our copy | View Download |
| 4 | Memorandum for Record A�� Witnesses | PDF, 4 pages · our copy | View Download |
| 5 | Data Extracted from G1000 for Accident Flight on January 4, 2023 | data file · our copy | Download |
| 6 | Data Extracted from G1000 for Flight on July 20, 2022 | data file · our copy | Download |
| 7 | Data Extracted from G1000 for Flight on September 6, 2022 | data file · our copy | Download |
| 8 | Data Extracted from G1000 for Flight on November 11, 2022 | data file · our copy | Download |
| 9 | Data Extracted from G1000 for Flight on November 25, 2022 | data file · our copy | Download |
| 10 | ADS-B Data for Accident Flight | data file · our copy | Download |
| 11 | Maintenance Logbook Excerpts | PDF, 8 pages · our copy | View Download |
| 12 | Fuel Logs | PDF, 2 pages · our copy | View Download |
| 13 | Toxicological Report | PDF, 1 page · our copy | View Download |
| 14 | Cockpit Display Recorded Flight Data - Specialist's Factual Report | PDF, 13 pages · our copy | View Download |
| 15 | Cockpit Display Recorded Flight Data - Specialist's Factual Report Attachment 1 - Tabular Data | data file · our copy | Download |
| 16 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page · our copy | View Download |
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.
