ERA14CA209 · Cessna T206H
Cessna T206H · Accident: abnormal runway contact during landing
From Fitchburg Municipal Airport (FIT) to Gilford, NH
Event
- NTSB case
- ERA14CA209
- 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
- N262ME
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fitchburg Municipal Airport (FIT), Fitchburg, MATo Gilford, NH
- Aircraft age
- About 14 years (built 2000)
- 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
- 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
- Abnormal runway contact
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the float equipped airplane reported that he intended to practice water landings and operations after about 7 months of seaplane inactivity due to winter. He was flying above a lake with glassy water conditions surveying the surface for ice or other hazards when the airplane's floats inadvertently contacted the water "a bit harder" then normal. The pilot elected to reduce engine power and attempted to land; however, the airplane nosed over into the water, and subsequently sank. Postaccident examination of the airplane did not reveal any abnormalities that would have precluded normal operation. The right float displayed evidence of contact with the propeller and the aft portion of the fuselage, near the empennage was substantially damaged. The pilot reported about 1,400 hours of total flight experience; which included about 50 hours in the same make and model as the accident airplane. In addition, he reported 21 landings on water during the 12 months that preceded the accident, with the most recent water landing about 7 months prior.
Probable cause
The pilot misjudged the float equipped airplane's altitude while maneuvering above the surface of a lake, which resulted in a float inadvertently contacting the water. Contributing to the accident were the glassy water conditions and pilot's lack of recent experience in amphibious airplanes.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14CA209
- Event ID
- 20140428X84638
- Case number
- ERA14CA209
- 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: 2280ee5c1c778b521e770edfbb6cb2739c320e316e78141e7d9b3a6bd35f02ad; retrieved 2026-09-15T23:33:00.223Z.