FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10LA365 · Texas Air Ventures Inc COMP AIR 8

19 Jul 2010 · Mount Pleasant, SC, United States

BOGCO Aviation Texas Air Ventures Inc COMP AIR 8 · Accident: loss of control in flight on approach

From Merritt Island Airport (COI) to Mount Pleasant Regional Airport Faison Field (LRO)

Report a problem

Event

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

Texas Air Ventures Inc COMP AIR 8

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
N882X
Onboard fatalities
Unknown
Route
From Merritt Island Airport (COI), Merritt Island, FLTo Mount Pleasant Regional Airport Faison Field (LRO), Mount Pleasant, SC
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 go-around
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
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

The pilot was conducting the first leg of a positioning flight in an experimental, amateur built, tail-wheel turboprop airplane. During landing, the airplane touched down to the right of the runway centerline and departed the right side of the runway. The pilot then added engine power to attempt an aborted landing. The airplane lifted off the runway, pitched up at a steep angle, stalled, and impacted the ground. Examination of the wreckage did not reveal any mechanical malfunctions; however, a postcrash fire consumed the majority of the wreckage. The airplane's pitch trim actuator was observed in the landing position, which was the full nose-up position and would have resulted in a steep nose-up attitude during climb-out, if not corrected by the pilot. The pilot had accumulated about 1,930 hours of total flight experience; however, he only had 5 total hours in the same make and model as the accident airplane.

Probable cause

The pilot's failure to retrim the airplane and maintain aircraft control during an aborted landing, which resulted in an inadvertent stall. Contributing to the accident was the pilot's lack of experience in the accident airplane make and model.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10LA365
Event ID
20100719X92628
Case number
ERA10LA365
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. 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: fd055bf4bf375b286c123d7dce26d29c7ddeebd2bfbde28acd6fa32a09687b4a; retrieved 2026-09-13T20:57:24.486Z.