NYC99FA096 · Sellors SEAREY
Sellors SEAREY · Accident: loss of control in flight during landing
From No airport to an unrecorded destination
Event
- NTSB case
- NYC99FA096
- 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
- 1 · 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
Sellors SEAREY
- Aircraft type
- Sellors SEAREY
- 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
- N6115P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From No airportTo 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
- 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
- Loss of control in flight
- 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 › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While returning from a local flight, the pilot established the airplane on a straight-in-approach for a water landing. Approximately 300 feet msl and 75 mph, the pilot configured the airplane with 20 degrees of flaps, and reset the elevator trim. After the airplane cleared a tree-covered hill to the northeast, the pilot retarded the throttle to idle. The airplane contacted the water, dragged its tail, and became airborne. The airplane then contacted the water for a second time in a nose-low attitude, and nosed over. After the accident, flight control continuity was verified, and the engine was run on the airframe, at takeoff power, for 5 minutes. The pilot did not have a single engine sea rating. Federal Aviation Regulations exempt pilots of experimental aircraft from needing a rating in the category of aircraft they are operating.
Probable cause
The pilot's failure to maintain aircraft control during the landing sequence, which resulted in the airplane contacting the water in a nose low attitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC99FA096
- Event ID
- 20001205X00547
- Case number
- NYC99FA096
- 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: 91fac15c355256cab69e3498258bf3612bcd67bb46cbd869a38daf8d2b960cc6; retrieved 2026-09-20T22:09:16.248Z.