DFW08LA144 · Stinson 108-3
Stinson 108-3 and Us Aviation Group Piper PA-28-161 · Accident: runway incursion (vehicle, aircraft or person) during takeoff
Event
- NTSB case
- DFW08LA144
- 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
Aircraft 1 · Stinson 108-3
- Aircraft type
- Stinson 108
- 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
- N6805M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Aero Valley Airport (52F), Roanoke, TXTo Roanoke, 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
- Takeoff
- 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
- Runway incursion (vehicle, aircraft or person)
- 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
Aircraft 2 · Piper PA-28-161
- Aircraft type
- Piper PA-28
- 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
- N8295X
- Operator
- US Aviation Group
- Onboard fatalities
- Unknown
- Route
- From Denton Enterprise Airport (DTO), Denton, TXTo Aero Valley Airport (52F), Roanoke, 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
- Landing · flare/touchdown
- 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
- Runway incursion (vehicle, aircraft or person)
- 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
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While landing, a low-wing airplane collided with a departing high-wing airplane. The high-wing airplane was on the takeoff roll and the low-wing airplane was in the landing flare when the collision occurred. Both airplanes came to rest upright on the runway with the low-wing airplane on top of the high-wing airplane. All three pilots were able to exit unassisted. The high-wing airplane was departing for a local flight and the low-wing airplane was on an instructional flight. The pilot of each airplane reported that they had transmitted their position/intentions on the common traffic control frequency (CTAF). In addition, the pilots reported not seeing the other airplane before the collision occurred. The runway's threshold was displaced 320-feet due to trees, which were approximately 50-feet tall, located just south and along the approach path. The pilot of each airplane reported that the trees contributing to the accident. According to 14 CFR 91.113, Right-of-way rules: Except water operations, "Aircraft, while on final approach to land or while landing, have the right-of-way over other aircraft in flight or operating on the surface, except that they shall not take advantage of this rule to force an aircraft off the runway surface which has already landed and is attempting to make way for an aircraft on final approach."
Probable cause
The departing pilot's inadequate visual lookout resulting in his airplane colliding with the landing airplane. Contributing to the accident was the trees/visual obstructions along the runway's approach path.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW08LA144
- Event ID
- 20080618X00877
- Case number
- DFW08LA144
- 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: 18a1ec3d8979a23b90ee69ee5a97207cb699da63275cc6d056dd4f1b8e32d39f; retrieved 2026-09-13T18:13:27.232Z.