CHI05CA275 · Cessna T206H
Cessna T206H · Accident: in flight collision with terrain/water during landing
From Austin Straubel International Airport (GRB) to an unrecorded destination
Event
- NTSB case
- CHI05CA275
- 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
Cessna T206H
- 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
- N206WK
- Operator
- Brian F. Michaud · private individual
- Onboard fatalities
- Unknown
- Route
- From Austin Straubel International Airport (GRB), Green Bay, WITo not recorded
- 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 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 · flare/touchdown
- 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 terrain/water
- 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
- Terrain condition › Water, rough
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The amphibian airplane contacted an unexpected wave and sank during the water landing. The pilot stated he flew over the intended landing area which he was very familiar with. He stated the water looked clear so he approached the channel on a downwind leg. He stated he turned base leg over the shoreline and turned onto final approach into the wind. He stated that when he entered the landing flare he looked out his side window to judge his height and he "saw a very large wave" that was in his path. He stated that there was no way to avoid the wave so he added power to try and "catch the top of the wave." However, the floats caught the wave and the airplane was "catapulted" forward into the water. The tip of the right float broke off and the airplane sank nose down in 10 to 12 foot deep water. The pilot reported there was approximately a 6-inch chop of the surface of the water at the time of the landing. He stated he was landing to the southwest and the winds were from the southwest at approximately 12 knots.
Probable cause
The unexpected wave that the airplane encountered during the landing flare.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05CA275
- Event ID
- 20051025X01723
- Case number
- CHI05CA275
- 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: 1be76d801efc5a5c2e8fe3a7c5ccdfbe261639cba463076111851d7fc62e50f5; retrieved 2026-09-22T05:20:13.651Z.