GAA16CA524 · VAN Hoomissen Gerald J MURPHY ELITE
VAN Hoomissen Gerald J MURPHY ELITE · Accident: nose over/nose down during landing
From Deer Park Airport (DEW) to Nordman, ID
Event
- NTSB case
- GAA16CA524
- 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
VAN Hoomissen Gerald J MURPHY ELITE
- Aircraft type
- Van Hoomissen Gerald MURPHY ELITE
- 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
- N567AK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Deer Park Airport (DEW), Deer Park, WATo Nordman, ID
- Aircraft age
- About 14 years (built 2002)
- 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
- Nose over/nose down
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the amphibious float-equipped airplane reported that during the touchdown to the north on choppy lake waters the airplane nosed over. The pilot further reported that when he and the passenger egressed from the cockpit and climbed onto the floats he noticed that the wind was 5-7 miles per hour (mph) from the south.
The airplane sustained substantial damage to the fuselage.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
The pilot reported as a safety recommendation that the pilot should get a "better read of the wind direction" prior to landing.
Probable cause
The floatplane pilot's improper landing flare during landing on choppy water with a tailwind, which resulted in a nose-over. Contributing to the accident was the pilot's failure to determine the wind direction before landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA524
- Event ID
- 20161006X15038
- Case number
- GAA16CA524
- 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: cc3a7415c75ef55ade7f8b4600455875f2edb78f23124a7f5cc98e43819f9b5f; retrieved 2026-09-16T04:21:37.724Z.