Brooks Seaplane Service Cessna U206G accident
Cessna U206G · Accident: in flight collision with object on approach
From Brooks Seaplane Base (S76) to Rose Lake, ID
Event
- NTSB case
- SEA04CA164
- 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
- Charter & commuter
- 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 U206G
- Aircraft type
- Cessna 206
- 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
- N9752Z
- Operator
- Brooks Seaplane Service
- Onboard fatalities
- Unknown
- Route
- From Brooks Seaplane Base (S76), Coeur d'Lane, IDTo Rose Lake, ID
- 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
- Part 135: Air Taxi & Commuter
- 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 pattern final
- First occurrenceThe 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, transmission
- 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
- Pilot in command › Clearance, not maintained
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 was approximately 50 feet above the water approaching the lake preparing to land when he saw the wires. In an effort to clear the wires, the pilot immediately added full power and back pressure on the yoke. The wires subsequently went over the top of the floats and caught onto both float struts, eventually breaking free from the right side but remaining entangled on the left float strut and pulling the airplane down. The pilot then pulled the nose up just prior to impacting the water, resulting in substantial damage to the airplane.
Probable cause
The pilot's failure to maintain clearance with the powerlines on final approach which resulted in a hard landing. A factor contributing the to accident were the powerlines.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA04CA164
- Event ID
- 20040827X01301
- Case number
- SEA04CA164
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 48b71907d95b2b41995de6abb9782bc692a659ff799750eaad1340101eeb07e1; retrieved 2026-09-18T15:18:53.633Z.