FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR20CA243 · Quest KODIAC 100

28 Jul 2020 · Hunts Point, WA, United States

Cly Aviation Quest KODIAC 100 · Accident: landing gear not configured

From King County International Airport - Boeing Field (KBFI) to an unrecorded destination

Report a problem

Event

NTSB case
WPR20CA243
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
Event fatalities
Unknown
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

Quest KODIAC 100

Aircraft type
Quest KODIAC 100
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
N856TC
Operator
Cly Aviation
Onboard fatalities
Unknown
Route
From King County International Airport - Boeing Field (KBFI), Seattle, WATo not recorded
Aircraft age
About 10 years (built 2010)
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

  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot of the amphibious float plane departed from a lake to a local airfield to refuel. After refueling, he departed the airport but neglected to retract the landing gear and he flew back to the same lake. During the touchdown, the float plane nosed over, and the engine truss was substantially damaged. The pilot added that he would modify his takeoff and prelanding checklist procedure to better verify the configuration of the landing gear. The pilot reported that there were no preimpact mechanical failures or malfunctions with the airframe and engine that would have precluded normal operation.

Probable cause

The pilot’s failure to retract the landing gear during a water landing, which resulted in a nose over. Contributing to the accident was the pilot’s failure to properly use a prelanding checklist.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR20CA243
Event ID
20200728X14620
Case number
WPR20CA243
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, cause areas. 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: 1e6135e42ecacad587e58959d107552a441f2f5bd7be3e73640681b6aec51410; retrieved 2026-09-16T12:17:56.657Z.