CEN10CA228 · Piper PA-32R-300
Piper PA-32R-300 · Accident: landing gear not configured
From Jamestown Regional Airport (JMS) to Jamestown Regional Airport (JMS)
Event
- NTSB case
- CEN10CA228
- 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-32R-300
- Aircraft type
- Piper PA-32
- 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
- N5868V
- Operator
- Silas Liechty
- Onboard fatalities
- Unknown
- Route
- From Jamestown Regional Airport (JMS), Jamestown, NDTo Jamestown Regional Airport (JMS), Jamestown, ND
- 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
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was approaching the airport with the intention of performing three touch and go landings. He went over the landing checklist as he was nearing the field, but he did not put the landing gear down because he was not on the downwind leg, where he would normally complete the checklist. He reported, “As I turned final, I thought I had the gear down but didn’t.” He reported that the gear up warning horn never sounded. The airplane touched down in a wings level attitude on the runway, which resulted in a bent propeller and substantial damage to the “hat” assemblies, which are U-shaped structural channels on the belly of the airplane. The landing gear handle was found in the UP position. The inspection of the airplane revealed that the landing gear extended and retracted when the airplane was put on jacks. The “Warning Gear Unsafe” light illuminated when the throttle was pulled to the idle position with the landing gear in the retracted position. The “Warning Gear Unsafe” light is about a 1-inch square red light located directly in front of the pilot on the instrument panel. However, the “Gear Warning Horn” did not sound.
Probable cause
The pilot's failure to lower the landing gear, resulting in a gear-up landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA228
- Event ID
- 20100428X13942
- Case number
- CEN10CA228
- 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: 6493b2be74bfa51fc337c25af7884cc1f674854cae8d4339a10916e66d865d8f; retrieved 2026-09-15T13:56:08.581Z.