ERA13CA416 · Cessna U206F F
Airborne Flyer Cessna U206F F · Accident: nose over/nose down during landing
From Plymouth Municipal Airport (1P1) to Rumney, NH
Event
- NTSB case
- ERA13CA416
- 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 U206F F
- 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
- N208LH
- Operator
- Airborne Flyer
- Onboard fatalities
- Unknown
- Route
- From Plymouth Municipal Airport (1P1), Plymouth, NHTo Rumney, NH
- Aircraft age
- About 39 years (built 1974)
- 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
- 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
- Nose over/nose down
- 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 power plant
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The purpose of the flight was for the pilot to relocate the amphibious airplane from an airport with a small grass runway, to another nearby land airport. Enroute, the pilot planned to make two intermediate stops at local lakes, before proceeding to the destination. After takeoff from the departure airport, the pilot did not retract the landing gear, and climbed the airplane in preparation to land at the first intermediate destination lake, which was located about 6 miles and about 1,500 feet in elevation above the departure airport. During the climb, the pilot leaned the engine's fuel mixture, and observed four green lights illuminated on the instrument panel, after which he stated, "Gear is up for water landing." He again repeated the landing gear check with the lake of intended landing in sight; however, illumination of four blue lights on the instrument panel was the correct indication that the landing gear was retracted and configured for a water landing.
While on final approach to the lake, while at an altitude of 40 feet and an airspeed of 75 mph, the landing gear warning indicator announced "gear is down for runway landing." The pilot responded by immediately initiating a go-around. The pilot pushed the throttle and propeller vernier controls forward simultaneously, but only brushed his fingers against the mixture control. The airplane continued to descend and struck the water about 10 seconds later with the engine under partial power. The airplane immediately nosed over upon touchdown, resulting in substantial damage.
The pilot later was advised by witnesses who observed the accident that during the go-around attempt, that as the engine power increased, it began "sputtering." The pilot then realized that he was likely unable to hear this due to the background noise of the music he had playing and noise-cancelling headset he was wearing. Upon examining the wreckage following the accident, the pilot found that the mixture control had not been fully advanced as he had applied power during the go-around attempt. In evaluating his fitness for flight following the accident, the pilot stated, "The flight was after a stressful day of work. Mentally I was C+ material at best. Concentration and focus was not as high as I like for flying."
Probable cause
The pilot's failure to ensure that the amphibious airplane's landing gear was properly configured for a landing on water and his failure to properly configure the airplane during the attempted go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13CA416
- Event ID
- 20130916X02738
- Case number
- ERA13CA416
- 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, 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: 6ca5209ca534a55779b701081c56b355e78005c6a8f5cf19246fb940f2500487; retrieved 2026-09-15T22:51:22.415Z.