FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN08LA102 · Cessna 150G

10 Jun 2008 · Brenham, TX, United States

American Views Cessna 150G · Accident: loss of control in flight during initial climb

From Brenham Municipal Airport (11R) to Conroe-North Houston Regional Airport (CXO)

Report a problem

Event

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

Cessna 150G

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
N4691R
Onboard fatalities
Unknown
Route
From Brenham Municipal Airport (11R), Brenham, TXTo Conroe-North Houston Regional Airport (CXO), Conroe, TX
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
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
Loss of control in flight
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
Tree(s)
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
  • Environmental issues › Conditions/weather/phenomena

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

NTSB narrative

The pilot said he checked the weather and radar and noted "a few small showers in the area, nothing close." He said the airport was surrounded by 15-20 foot trees that jut out from the perimeter of the airport towards the runway. There was a 10-knot crosswind, so the pilot selected runway 16 "since it has a down slope." He used a crosswind takeoff procedure. When he rotated, "a tremendous gust of wind hit the aircraft from the rear-left quarter and forced the aircraft sideways off the runway and towards some trees" near the runway. The pilot aborted the takeoff but was unable to stop the airplane and it collided with the trees. According to the airport's AWOS, the wind was from 100 degrees at 5 knots, with "lightning distant east and southeast."

Probable cause

The sudden windshift (crosswind gust), rendering directional control impossible. Contributing factors in this accident were the high speed during the aborted takeoff and trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN08LA102
Event ID
20080624X00895
Case number
DEN08LA102
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, coordinates. 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: faeebc783c535e617a9fe13d75113dacfb43528a505e801acac7ce64b13b749d; retrieved 2026-09-15T09:47:46.862Z.