FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL89LA138 · Cessna 150

26 Apr 1989 · New Bern, NC, United States

Air East Cessna 150 · Accident: on ground/water collision with terrain/water during landing

From Coastal Carolina Regional Airport (EWN) to Coastal Carolina Regional Airport (EWN)

Report a problem

Event

NTSB case
ATL89LA138
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 150

Aircraft type
Cessna 150
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
N1595Q
Operator
Air East
Onboard fatalities
Unknown
Route
From Coastal Carolina Regional Airport (EWN), New Bern, NCTo Coastal Carolina Regional Airport (EWN)
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
On ground/water collision with terrain/water
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 › Go-around, delayed
  • Pilot in command › In-flight planning/decision, improper

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

NTSB narrative

THE PILOT WAS PRACTICING A FORCED LANDING WITH AN INTENDED POWER RECOVERY AT 100 FT AGL. HE STATED THAT AS POWER WAS APPLIED TO GO AROUND, THE AIRPLANE ENCOUNTERED TURBULENCE AT TREETOP LEVEL & THE RIGHT WING DROPPED. HE APPLIED CORRECTIVE ACTION, BUT THE AIRPLANE SETTLED TO A FEW FEET ABOVE THE GROUND. HE ELECTED TO LAND, BUT DURING THE LANDING ROLL-OUT ON WET TERRAIN, THE AIRPLANE COLLIDED WITH A DITCH & WAS DAMAGED.

Probable cause

THE PILOT'S IMPROPER IN-FLIGHT PLANNING/DECISION AND A DELAYED GO-AROUND. TURBULENCE, WET TERRAIN, AND A DITCH WERE CONTRIBUTING FACTORS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL89LA138
Event ID
20001213X28040
Case number
ATL89LA138
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: 6ff05e4f8708ce05c20d9d740273d024408b8180393dc1205840d82cbf18c061; retrieved 2026-09-23T07:39:57.217Z.