ANC12GA114 · Quest Aircraft Company LLC KODIAK 100
U.S. Fish and Wildlife Service Quest Aircraft Company LLC KODIAK 100 · Accident: loss of control on ground during landing
From Kenai Municipal Airport (PAEN) to Lake Hood Seaplane Base (PALH)
Event
- NTSB case
- ANC12GA114
- 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
- Government
- 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 Aircraft Company LLC KODIAK 100
- Aircraft type
- Quest KODIAK 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
- N745
- Operator
- U.S. Fish and Wildlife Service
- Onboard fatalities
- Unknown
- Route
- From Kenai Municipal Airport (PAEN), Kenai, AKTo Lake Hood Seaplane Base (PALH), Anchorage, AK
- 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
- Public Aircraft
- 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 · landing roll
- 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 on ground
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was landing an amphibious float-equipped airplane in a lake on the final leg of a 4 day, public-use wildlife survey. The pilot stated she had not conducted a water landing recently, so she elected to land on the water to maintain proficiency. Before landing, the pilot completed the before landing checklist, set approximately 50 percent right rudder trim, and confirmed the wheels were in the up position. She noted that her airspeed on approach was slightly faster than normal. During touchdown, the airplane veered to the left and then to the right. The airplane then veered violently to the right, as though it "caught a float," and the right wing struck the water. The airplane then pivoted abruptly to the right, cartwheeled, and the wreckage began to sink.
An NTSB postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.
Because the airplane was operated as a public aircraft operation, the Department of Interior's (DOI) training program was not subject to the civil aircraft requirements. An NTSB review of the flight training program revealed a general outline with hour requirements. The flight training program did not include curriculums, events, or testing and checking procedures. No written maneuvers and procedures guide, with acceptable performance standards was developed, therefore no standardization existed within the pilot group, and tribal knowledge and experimentation were accepted as part of the organizations culture. Multiple checklists existed for the airplane, and pilots were allowed to use whichever checklist they preferred. DOI did not/nor were they required to incorporate best practices and industry standards into their training program and airplane operations, and no FAA oversight was required or provided. Vendor pilot requirements were substantially higher with stricter standards, and required FAA oversight, compared to those of agency pilots flying similar missions.
The pilot stated that, during her interagency pilot evaluation/qualification check, step turns were not completed. The pilot said that the check pilot was not comfortable performing the maneuver, so they agreed to sign off the maneuver on the check ride form but did not accomplish the task. Although the pilot had logged 232 hours and 68 water landings, only 2 water landings were logged without an instructor onboard.
Probable cause
The pilot's failure to maintain directional control while landing, which resulted in a collision with the water. Contributing to the accident were the pilot's lack of experience conducting waterborne operations in the accident make and model airplane and the public aircraft operator’s lack of training standardization.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC12GA114
- Event ID
- 20121001X34716
- Case number
- ANC12GA114
- 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: f274e3754beb0687cf8282cd23d32cf05ab4574811bb6c0afe08f8319b4eea35; retrieved 2026-09-15T20:03:49.412Z.