FTW94FA203 · Cessna 175B
Cessna 175B · Accident: in flight collision with object while maneuvering
From TX to TX
Event
- NTSB case
- FTW94FA203
- 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 175B
- Aircraft type
- Cessna 175
- 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
- N8103T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From TXTo 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
- Maneuvering
- 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
- Wire, transmission; 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 › Clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE DEPARTED THE AIRPORT AND FLEW TO A GAS PLANT 6 NAUTICAL MILES TO THE SOUTH. A WITNESS AT THE GAS PLANT OBSERVED THE AIRPLANE STRIKE POWER LINES, AND ALMOST COLLIDE WITH GASOLINE TANKS AND A SMALL HILL. THE AIRPLANE WAS FLOWN BACK TO THE AIRPORT. THE PILOT STATED WHILE LANDING, AFTER TOUCH DOWN, HE OBSERVED DEER RUN ONTO THE RUNWAY AND INTO THE PATH OF THE AIRPLANE. HE STATED THAT HE ADDED POWER TO EXECUTE A GO-AROUND, AND THE AIRPLANE DID NOT RESPOND PROPERLY. A WITNESS OBSERVED THE AIRPLANE CIRCLING THE AIRPORT AND GOLF COURSE AT A 'VERY' LOW ALTITUDE SEVERAL TIMES. THE AIRPLANE WAS THEN OBSERVED FLYING SLOW AT A LOW ALTITUDE HEADING SOUTH ALONG THE NUMBER ONE FAIRWAY OF THE GOLF COURSE. THE AIRPLANE THEN MADE A STEEP LEFT TURN, THE LEFT WING STRUCK A TREE, NOSED DOWN, AND IMPACTED ON THE EDGE OF THE 7TH FAIRWAY OF THE GOLF COURSE.
Probable cause
THE PILOT'S FAILURE TO MAINTAIN OBSTACLE CLEARANCE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW94FA203
- Event ID
- 20001206X01517
- Case number
- FTW94FA203
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1994-06-21.
- API snapshot SHA-256: f08be612f86378337dba77e5a58ecc8286c2aac6a5fe32ec7602e5d629188449; retrieved 2026-09-21T13:50:42.915Z.