WPR10LA207 · Piper PA-22-160
Ventana Air Piper PA-22-160 · Accident: hard landing
From U42 · West Jordan, UT to Thunder Ridge Airpark (UT83)
Event
- NTSB case
- WPR10LA207
- 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-22-160
- Aircraft type
- Piper PA-22
- 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
- N9019D
- Operator
- Ventana Air
- Onboard fatalities
- Unknown
- Route
- From U42 · West Jordan, UTTo Thunder Ridge Airpark (UT83), Fruitland, 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
- 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
- Hard landing
- 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 reported that the windsock indicated light winds straight down the runway and he encountered some light headwind gusts on short final. During the flare, the airplane ballooned and he applied power to smooth the descent. The pilot stated that the landing was a full stall hard landing, which was the only type of landing he ever performed. The left main landing gear subsequently collapsed, the left wing dropped, and the airplane veered to the right. Despite the pilot's control inputs, the airplane exited the right side of the runway surface and impacted a drainage berm. Federal Aviation Administration inspectors examined the airplane and observed that the landing gear shock cord’s retainer lug fractured and separated. The cords released, which caused them to lose all of the tension required to perform their intended function. The structure had no indication of previous cracking or fatigue, and there were 45-degree shear lips around the entire circumference of the fracture surface indicative of an overload condition.
Probable cause
The pilot’s improper landing flare.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10LA207
- Event ID
- 20100416X63833
- Case number
- WPR10LA207
- 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: 83580a74bc01a88b3143532964daaf8652341dd4240edeecb8eb52c5ed4b4d24; retrieved 2026-09-15T13:52:19.611Z.