FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR14CA057 · NEW Piper PA46 350P

23 Nov 2013 · Salt Lake City, UT, United States

NEW Piper PA46 350P · Accident: landing gear not configured

From Salt Lake City International Airport (SLC) to Salt Lake City International Airport (SLC)

Report a problem

Event

NTSB case
WPR14CA057
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

NEW Piper PA46 350P

Aircraft type
New Piper PA46
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
N3151G
Operator
Unknown
Onboard fatalities
Unknown
Route
From Salt Lake City International Airport (SLC), Salt Lake City, UTTo Salt Lake City International Airport (SLC), Salt Lake City, UT
Aircraft age
About 7 years (built 2006)
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
Landing · flare/touchdown
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
Landing gear not configured
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 systems
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that he was asked by air traffic control to enter a right base, crossing in front of a passenger jet on final approach to another runway. The pilot further stated that he accepted this option and did not feel rushed; however, in doing so, it interrupted him from his typical traffic pattern entry and checklist usage, which resulted in him not extending the landing gear. The airplane subsequently landed gear up which resulted in substantial damage to the fuselage. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot's failure to extend the landing gear before landing. Contributing to the accident was the pilot's improper use of the checklist.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR14CA057
Event ID
20131125X53917
Case number
WPR14CA057
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. 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: 2404dc8ae0d869ec29ef4e2e14785a2de7b442063cd2c2aa8cefc3d2b2e7ddc9; retrieved 2026-09-15T23:08:35.605Z.