FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN26LA110 · Glasair GlaStar

6 Feb 2026 · Beaumont, TX, United States

Glasair GlaStar · Accident: powerplant system/component malfunction/failure during initial climb

From Thibodaux Municipal Airport (L83) to Jack Brooks Regional Airport (BPT)

Report a problem

Event

NTSB case
CEN26LA110
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
Ongoing
Event fatalities
Unknown
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

Glasair GlaStar

Aircraft type
Glasair GLASTAR
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
N789BM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Thibodaux Municipal Airport (L83), Thibodaux, LATo Jack Brooks Regional Airport (BPT), Beaumont, TX
Aircraft age
About 24 years (built 2002)
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
Initial climb
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
Powerplant system/component malfunction/failure
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On February 6, 2026, about 1810 central standard time, an experimental Glasair GlaStar airplane, N789BM, was substantially damaged when it was involved in an accident near Beaumont, Texas. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported a loss of engine oil pressure about six miles from the intended destination airport. The engine started running rough and losing power. He executed a landing to a taxiway at the destination airport. However, the airplane began to porpoise on landing. It subsequently overran the taxiway and impacted a fence. The airframe sustained substantial damage to both wings and the empennage. The airplane was recovered to a secure hangar at the airport. A postaccident engine examination is planned.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record CEN26LA110
Event ID
20260209202406
Case number
CEN26LA110
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2026-02-07.
  • API snapshot SHA-256: 52b3443165e87fa56d5468408bed3152bad4abf2cc90bfa878bfd5e178617537; retrieved 2026-09-16T20:43:40.863Z.