FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24LA254 · Piper PA-34-220T

24 Jul 2024 · Roy, UT, United States

CSA Aircraft Leasing Piper PA-34-220T · Accident: collision with terrain/object (non-CFIT) on approach

From Ogden, UT to an unrecorded destination

Report a problem

Event

NTSB case
WPR24LA254
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-34-220T

Aircraft type
Piper PA-34
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N134MG
Onboard fatalities
Unknown
Route
From Ogden, UTTo not recorded
Aircraft age
About 43 years (built 1981)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Collision with terrain/object (non-CFIT)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft power plant
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On July 24, 2024, about 1555 mountain daylight time, a Piper PA-34-220T, N134MG, was substantially damaged when it was involved in an accident near Roy, Utah. The flight instructor was seriously injured and the pilot receiving instruction sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. According to the flight instructor they had departed from Ogden-Hinckley Airport (OGD), Ogden, Utah, for a local practice area to practice single engine maneuvers without incident. They returned to the airport, performed a practice instrument approach to runway 03, followed by a missed approach. The flight instructor and pilot receiving instruction then executed a and then executed a second practice instrument approach with a simulated left engine failure. At the final approach fix, they lowered the landing gear; however, the right main landing gear indicator did not show a that the landing gear was down and locked. They attempted to trouble shoot the right landing gear, which included swapping the light bulbs, cycling the gear, and using the emergency extension with no success. They performed a low approach over runway 03, where the air traffic control tower controller reported that the landing gear appeared to be down. The flight instructor stated that the tower offered to call fire and rescue equipment to be in position near the runway in case the landing gear collapsed on landing. The flight instructor agreed and then circled to the east of the airport while they awaited the arrival of fire personnel. After maneuvering over runway 03, the upwind was extended by an additional two miles before a left crosswind turn was made. During the crosswind turn, the student advanced the power to the left engine and the flight instructor secured the right engine to avoid damage to the propeller and engine if the right main landing gear collapsed upon landing. The flight instructor reported that initially the airplane was able to maintain altitude and 92 knots indicated airspeed (KIAS), which was best rate of climb for single engine operation (Vyse) with maximum power on the left engine. Once established on downwind, the “over-boost” light illuminated on the annunciator panel, consistent with the operating engine exceeding the manifold pressure limit of 40.5 inches of Hg. The pilot receiving instruction was instructed by the flight instructor to retard the throttle and then make incremental movements of the throttle in an effort to not over-boost the left engine. As the airplane passed mid-field for runway 03, the instructor began the steps to restart the right engine; however, due to the altitude and airspeed, they told the controller that that they were going to land immediately south of the runway. The flight instructor took control of the airplane and maneuvered to land on a road. During the landing process, the airplane struck multiple trees and impacted a road before it came to rest upright abut a tree in the front yard of a residence. The airplane was recovered to a secure facility for further investigation.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record WPR24LA254
Event ID
20240725194765
Case number
WPR24LA254
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 40cecceea78126120616beaaec941db04b94887b32e8c0ac52643927ad8bddfb; retrieved 2026-09-16T19:05:08.243Z.