ANC23FA001 · Cessna A185F
Cessna A185F · Accident: nose over/nose down while taxiing
Event
- NTSB case
- ANC23FA001
- 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
Cessna A185F
- Aircraft type
- Cessna 185
- 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
- N217C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 44 years (built 1978)
- 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
- Taxi · into takeoff position
- 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
- None
Cause areas
- Aircraft › Aircraft systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot of the float-equipped airplane was departing from a pond. He aborted the first attempt and was taxiing back to attempt a second takeoff. Witnesses saw the floats almost fully submerged under the water as the airplane taxied and stated that the pitch attitude of the airplane was unusually nose-low. The pilot reduced engine power and the airplane nosed over. The airplane was not damaged; however, several hundred pounds of unsecured cargo inside the airplane shifted during the nose-over and likely resulted in the pilot’s inability to egress and his subsequent drowning. During a postaccident examination, two unsealed holes were found under the float bumpers that would have allowed water to enter the front compartment of each float. It is likely that the front compartments in both floats filled with water and resulted in the nose-over during taxi.
Probable cause
The improperly maintained floats, which allowed water to fill the front compartments and resulted in the airplane nosing over during taxi. Contributing to the fatal injury of the pilot was the improperly secured cargo, which prevented the pilot from egressing the airplane following the nose-over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC23FA001
- Event ID
- 20221006106074
- Case number
- ANC23FA001
- 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: local date, investigation status, coordinates, cause areas, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2022-10-06.
- API snapshot SHA-256: 46df309328102c51a189867607c456d3e3c0a19e3b724947a170d20643f05e86; retrieved 2026-09-15T07:52:26.261Z.