WPR16FA154 · Sperling Richard G LANCAIR 360
Sperling Richard G LANCAIR 360 · Accident: loss of control in flight on approach
From Columbia Gorge Regional Airport (DLS) to Columbia Gorge Regional Airport (DLS)
Event
- NTSB case
- WPR16FA154
- 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
- 1 · 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
Sperling Richard G LANCAIR 360
- Aircraft type
- Sperling Richard LANCAIR 360
- 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
- N528HZ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Columbia Gorge Regional Airport (DLS), The Dalles, ORTo Columbia Gorge Regional Airport (DLS), The Dalles, OR
- Aircraft age
- About 2 years (built 2014)
- 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
- Approach · VFR go-around
- 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
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot was landing the airplane on runway 31 in visual meteorological conditions when witnesses observed the airplane in a nose-low, steep-left-bank attitude west of the runway over grassy terrain. A second later, the airplane impacted the terrain. An examination of the accident site revealed propeller slash marks about 1,800 ft from the approach end of runway 31. The initial point of a 200-foot-long debris path was located 385 ft from the slash marks on a 235° magnetic heading, and the airplane came to rest upright at the end of the debris path with its nose oriented northeast.
During the wreckage recovery, both main and the nose landing gear were found in a retracted position. During the postaccident examination, the throttle, mixture and propeller control levers were observed positioned full forward. The left and right main landing gear doors and the fuselage bottom skin exhibited numerous scratches and paint transfer consistent with the airplane's lower surface contacting the runway with the landing gear retracted. Both propeller blade tips were bent and curled aft, and the blades displayed numerous span-wise scratches from about mid span to the blade tips consistent with the propeller blades contacting the runway. The examination revealed no evidence of any preimpact mechanical failures or anomalies that would have precluded normal operation.
It is likely that, during the landing sequence, the pilot realized that the landing gear was retracted and aborted the landing by adding full power. During the aborted landing, the pilot did not maintain control of the airplane, which rolled to the left and impacted terrain.
Probable cause
The pilot's loss of control during an aborted landing. Contributing to the accident was the pilot's failure to extend the landing gear before touchdown.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16FA154
- Event ID
- 20160801X93405
- Case number
- WPR16FA154
- 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: 1bf2e3c3bbd9241ae5fd2264fd900186681bbc1e91799d2f904304ac23a648cd; retrieved 2026-09-14T21:57:46.087Z.