LAX99LA271 · Cessna TU 206G
Cessna TU 206G · Accident: airframe, component or system failure during landing
From San Carlos Airport (SQL) to an unrecorded destination
Event
- NTSB case
- LAX99LA271
- 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
- 0
- 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 TU 206G
- Aircraft type
- Cessna TU-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
- N206RR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From San Carlos Airport (SQL), San Carlos, CATo 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 · landing roll
- 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
- Airframe, component or system failure
- 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
- Fuselage, attachment › Corroded
- Fuselage, attachment › Fractured
Approximate · Estimated position: the centre of Clearlake, CA, the place the record names. Not the accident site.
NTSB narrative
According to the pilot, during a water landing with the float equipped airplane, the touchdown was smooth. Shortly after water contact, the airplane suddenly veered to the left and overturned. The winds were light and variable and there were no white caps. An inspection of the airplane revealed a fracture and separation of the spreader bar at the front left pontoon attach point. The fracture was corroded. This area could only be observed because the pontoon was split open, and a mechanic could not inspect this area unless the floats were removed. A visual inspection had been completed on the floats by a mechanic the day before, and there were no mechanical problems with the airplane.
Probable cause
The fracture and separation of the front left pontoon attach point due to corrosion. The inability of the area to be inspected was a factor in the accident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX99LA271
- Event ID
- 20001212X19558
- Case number
- LAX99LA271
- 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. 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: 665375cef41255d3c71d35a422355cd44b98ef43032f446c40e57c13e2ae3f96; retrieved 2026-09-22T14:17:19.790Z.