FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA00LA119 · Bair Helicopters, Inc. SEAREY

26 Mar 2000 · Kill Devil Hills, NC, United States

Bair Helicopters, Inc. SEAREY · Accident: in flight encounter with weather on approach

From No airport to an unrecorded destination

Report a problem

Event

NTSB case
MIA00LA119
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

Bair Helicopters, Inc. SEAREY

Aircraft type
Bair 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
N246DB
Operator
Carl F. Newton, JR · private individual
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
Approach · VFR pattern final
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 encounter with weather
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/mush
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 › Stall/mush, inadvertent

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot stated that after takeoff he performed one touch-and-go landing on the water where the airplane is based then flew north of there then returned and performed one touch-and-go landing on the water. While turning left base to final for the planned 3rd touch-and-go landing, with 10 degrees of flaps extended, in a 15-20 degree angle of bank, and with the power reduced, the passenger called out that the indicated airspeed was 55 miles per hour. The pilot later reported that he did not monitor the airspeed during the turn. He applied partial power; the engine responded, then lowered the nose. He then applied aft elevator input with no response. The airplane contacted the water while in a left wing low attitude. He further reported that there was no engine or flight control preimpact failure or malfunction and just before impact with the water the flight encountered a wind gust. Postaccident examination of the airplane by one of the co-owners revealed aileron, rudder, and elevator flight control continuity from the cockpit to each control surface.

Probable cause

The inadvertent stall by the pilot-in-command while on final approach resulting in the uncontrolled descent and in-flight collision with water.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA00LA119
Event ID
20001212X20702
Case number
MIA00LA119
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: 6928e9e8d69ca7a4a8365c0fc4e8d78e5a0258aff03c576bcb490a2fa55be1ad; retrieved 2026-09-21T20:16:53.799Z.