FTW87FA032 · Cessna 340A
Cessna 340A · Accident: in flight encounter with weather en route
From David Wayne Hooks Memorial Airport (DWH) to Tulsa Riverside Airport (RVS)
Event
- NTSB case
- FTW87FA032
- 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
- 1 · 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
- Instrument Meteorological Cond
Cessna 340A
- Aircraft type
- Cessna 340
- 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
- N8CD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From David Wayne Hooks Memorial Airport (DWH), Tomball, TXTo Tulsa Riverside Airport (RVS), Tulsa, OK
- 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
- En route · climb to cruise
- 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 encounter with weather
- 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 (marked); 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
- Destroyed
Cause areas
- Pilot in command › Directional control, not maintained
- Pilot in command › Proper altitude, not maintained
- Pilot in command › Spatial disorientation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT TOOK OFF IN FOG AND LIGHT RAIN AND CLIMBED INTO CLOUDS AT ABOUT 300-400 FEET ABOVE THE GROUND WHILE BOTH LANDING LIGHTS WERE EXTENDED AND ILLUMINATED. ALSO THE AIRPORT'S ROTATING BEACON (LOCATED AOBUT A MILE FROM THE ACCIDENT SITE) WAS FLASHING ON THE CLOUDS ACCORDING TO A GROUND WITNESS. JUST AFTER ENTERING THE CLOUDS THE PILOT WAS ISSUED A LEFT TURN FROM HIS PRESENT HEADING OF 350 DEGREES TO A HEADING OF 270 DEGREES AND TOLD TO CONTACT DEPARTURE CONTROL. HE DID NOT MAKE THIS CONTACT AND HE CONTINUED THE LEFT TURN (NOW DESCENDING) TO A HEADING OF 210 DEGREES AT WHICH TIME THE AIRCRAFT COLLIDED WITH TREES AND A LARGE ELECTRICAL TRANSMISSION LINE AND THEN THE GROUND. THE ENGINES WERE OPERATING AT A HIGH POWER SETTING AT THE TIME OF IMPACT. ALL BROKEN FLIGHT CONTROL CABLES REVEALED EVIDENCE OF OVERSTRESS SEPARATION. NO EVIDENCE OF PREIMPACT MECHANICAL FAILURE OR MALFUNCTION WAS FOUND.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW87FA032
- Event ID
- 20001213X35356
- Case number
- FTW87FA032
- 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: 5046a3d1f90f9f03d3b5fdc786d06559a3f7657bccb7ad78e0e0a71c7cd6fc8d; retrieved 2026-09-21T04:17:42.840Z.