FTW91LA034 · Cessna 152
Bourland Field Cessna 152 · Accident: loss of control in flight during landing
From Ennis Municipal Airport (F41) to an unrecorded destination
Event
- NTSB case
- FTW91LA034
- 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 152
- Aircraft type
- Cessna 152
- 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
- N67650
- Operator
- Bourland Field
- Onboard fatalities
- Unknown
- Route
- From Ennis Municipal Airport (F41), Ennis, TXTo 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
- Landing · flare/touchdown
- 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
- 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
- Pilot in command › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT FLARED THE AIRPLANE OVER THE CENTER LINE OF RUNWAY 17 AND PRIOR TO TOUCHDOWN A GUST OF WIND LIFTED THE RIGHT WING. THE AIRPLANE VEERED LEFT OFF THE RUNWAY AND A GO AROUND WAS INITIATED. THE PILOT STATED THAT THE AIRPLANE WOULD NOT CLIMB DURING THE ATTEMPTED ABORTED LANDING, AND THAT HE WAS UNABLE TO REGAIN CONTROL. THE AIRPLANE THEN STRUCK THE TOP TWO STRANDS OF A BARBED WIRE FENCE. IT SUBSEQUENTLY TOUCHDOWN IN AN OPEN FIELD ADJACENT TO THE AIRPORT AND STRUCK A TREE AND A SECOND FENCE PRIOR TO COMING TO A STOP. THE LANDING WAS ATTEMPTED IN A RIGHT CROSS WIND. WINDS AT THE CLOSEST WEATHER OBSERVATION FACILITY WERE REPORTED TO BE FROM 260 DEGREES AT 12, GUSTING TO 20 KNOTS.
Probable cause
THE PILOT'S FAILURE TO MAINTAIN DIRECTIONAL CONTROL DURING LANDING. CONTRIBUTING TO THE ACCIDENT WAS THE CROSSWIND CONDITION THAT EXISTED AT THE TIME OF THE ACCIDENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW91LA034
- Event ID
- 20001212X16320
- Case number
- FTW91LA034
- 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: 4cacb0b81d7dcfd5779309d892b0c9b0bc163bf8d523177ed7eec4fc0413a30b; retrieved 2026-09-23T04:51:05.287Z.