WPR09LA417 · Piper PA28R 200
Piper PA28R 200 · Accident: landing gear not configured during initial climb
From Wendover Airport (ENV) to Salt Lake City International Airport (SLC)
Event
- NTSB case
- WPR09LA417
- 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 PA28R 200
- Aircraft type
- Piper PA28
- 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
- N4837T
- Operator
- Levon Koshkaryan
- Onboard fatalities
- Unknown
- Route
- From Wendover Airport (ENV), Wendover, UTTo Salt Lake City International Airport (SLC), Salt Lake City, UT
- Aircraft age
- Not recorded
- 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
- Initial climb
- 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 oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said that after takeoff he was unable to retract the landing gear, and at about the same time perceived a loss of engine power output. The pilot then set the mixture control to full rich and leveled the airplane. When attempts to retract the landing gear were unsuccessful, the pilot elected to make an emergency landing on an interstate highway. During the landing the airplane’s left wing impacted the left side of a tractor-trailer truck, which resulted in substantial damage to the airplane. The engine was test run 3 separate times during a post accident examination and no anomalies were noted that would have precluded normal operation. The airplane was equipped with a landing gear back-up actuator override mechanism, which prevents landing gear retraction at airspeeds below approximately 85 miles per hour (mph); this airspeed increases with power reduction and/or altitude increase. Density altitude at the time of the accident was calculated to be 6,946 feet, which according to Piper Aircraft, would have required an additional 6 miles per hour to be added to the 85 mph to affect a normal gear retraction. The system incorporates a manual override emergency gear lever that in the raised position allows the landing gear position to be controlled by the landing gear selector switch regardless of airspeed and power combinations. A post accident examination of the override system revealed no anomalies that would have precluded normal operation. When asked if he had used the system prior to the emergency landing, the pilot said he had not. The pilot’s failure to attain and maintain an airspeed sufficient to affect a normal landing gear retraction, as well as his failure to utilize the airplane’s emergency landing gear override system, collectively contributed to his decision to make an emergency landing. The pilot’s perceived loss of engine power was most probably due to the degraded engine performance as a direct result of positioning the mixture control from an optimal lean position to the full rich position in a high density altitude environment. The pilot could have mitigated the event had he elected to initially use the manual override system, which would have resulted in a normal gear retraction regardless of airspeed and altitude.
Probable cause
The failure of the pilot to attain and maintain an airspeed sufficient for normal landing gear retraction during initial climb. Contributing to the accident was the pilot's failure to use the airplane's manual override landing gear system, misidentifying that a total loss of engine power was imminent, positioning the mixture control to the full rich position, and the density altitude condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09LA417
- Event ID
- 20090826X33516
- Case number
- WPR09LA417
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2009-08-27.
- API snapshot SHA-256: 147dddb694b4e00ea917befd01585fc994b75b5ab01de8aeb28caa7f6e2b284f; retrieved 2026-09-15T12:50:56.110Z.