DFW06CA192 · Beech BE23
Beech BE23 · Accident: in flight collision with object on approach
From Bowie Municipal Airport (0F2) to Bowie Municipal Airport (0F2)
Event
- NTSB case
- DFW06CA192
- 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
Beech BE23
- Aircraft type
- Beechcraft 23
- 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
- N2326Z
- Operator
- Ray D. Watson · private individual
- Onboard fatalities
- Unknown
- Route
- From Bowie Municipal Airport (0F2), Bowie, TXTo Bowie Municipal Airport (0F2), Bowie, 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
- Approach · VFR go-around
- 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
- In flight collision with object
- 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
- Dual student › Clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane collided with trees when the pilot attempted a go-around during an instructional flight. The training flight had been in the closed traffic pattern for Runway 35 (3,603-foot long, by 60-foot wide). According to the flight instructor, the single-engine airplane touched down and began to veer off into grass on the left side of the runway. The flight instructor advised the student to "add some power and turn back onto the runway;" however, the student responded by applying full power while simultaneously pulling back on the yoke. The airplane lifted off the ground and impacted trees that were located on the left side of the runway. The flight instructor reported that at the time of the accident, the wind was from 050 degrees at 9 knots, gusting to 12 knots. The investigator-in-charge calculated the density altitude at 3,311 feet.
Probable cause
The student pilot's failure to maintain clearance from trees. Contributing factors were the prevailing crosswind and improper supervision of the flight by the flight instructor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06CA192
- Event ID
- 20060810X01148
- Case number
- DFW06CA192
- 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, 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: cd1d032ca743132b52b2e9016cf5452f499cefa686947bd46fc23192df581737; retrieved 2026-09-22T04:39:19.111Z.