WPR11CA142 · Piper PA-31P-350
EAL Leasing Piper PA-31P-350 · Accident: landing gear not configured
From Aurora State Airport (KUAO) to Southwest Oregon Regional Airport (KOTH)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR11CA142
- 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-31P-350
- Aircraft type
- Piper PA-31
- 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
- N9237Y
- Operator
- EAL Leasing
- Onboard fatalities
- Unknown
- Route
- From Aurora State Airport (KUAO), Aurora, ORTo Southwest Oregon Regional Airport (KOTH), North Bend, OR
- 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
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
According to the pilot, while in the process of executing a terminal instrument approach to his home airport, he transitioned from instrument meteorological conditions to visual meteorological conditions. He canceled his instrument flight rules clearance, and transitioned from the terminal instrument approach to a visual flight rules approach pattern. During this sequence of events he did not follow a written checklist, and inadvertently forgot to lower the landing gear. During the landing flare, he heard the noise caused by the wing flaps and both propellers contacting the surface of the runway, and he added power and immediately executed a go-around. He then entered a closed pattern, lowered the landing gear and repositioned the flaps, before making an uneventful landing. He said during the approach he heard the gear warning horn sounding, but he thought it was the altitude alerting system. An inspection of both the runway surface scarring and each propeller blade revealed that the tips of all six blades had been grounded down by repeated contact with the asphalt surface. He also said that the airplane did not have any system malfunctions.
Probable cause
The pilot's failure to lower the landing gear while on approach to landing. Contributing to the accident was the pilot's failure to follow a written checklist during the approach portion of the flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11CA142
- Event ID
- 20110223X00020
- Case number
- WPR11CA142
- 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. 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: c08e782aae72bf95dc60d56333368aa3e0b65ab76071355e48d51f1ad9e6f24e; retrieved 2026-09-15T15:50:10.044Z.