FTW85FA078 · Beech V35A
Beech V35A · Accident: airframe, component or system failure en route
From Dallas Executive Airport (RBD) to Corpus Christi International Airport (CRP)
Narrative check · The NTSB narrative appears to contradict this record's flight rules. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- FTW85FA078
- 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
Beech V35A
- Aircraft type
- Beechcraft 35
- 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
- N7460N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dallas Executive Airport (RBD), Dallas, TXTo Corpus Christi International Airport (CRP), Corpus Christi, 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 Possible conflict
- 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 · 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
- Airframe, component or system failure
- 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 › Spatial disorientation
- Pilot in command › Visual lookout, not possible
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
N7460N, OPERATING AS MID-AMERICA FLT 401, CRASHED WHILE ON AN IFR FLT PLAN ENROUTE TO CORPUS CHRISTI, TX. AFTER HAVING BEEN VECTORED AROUND A HEAVY THUNDERSTORM & CLEARED DIRECT TO WACO, TX. THE PLT CONTACTED FORT WORTH CENTER & STATED THAT HE HAD 'LOST MY ARTIFICIAL HORIZON & MY DIRCTIONAL GYRO.' AFTER ASKING THE PLT IF THE ACFT HAD A COMPASS & RECEIVING AN AFFIRMATIVE REPLY THE ACFT WAS INSTRUCTED TO TURN TO A 010 HEADING. SHORTLY AFTER, THE RADAR TARGET WAS LOST. INVESTIGATION REVEALED THAT THE PLT HAD BEEN EMPLOYED BY MID-AMERICA FOR APROX 3 WKS AS A NIGHT REFUELER. ON THE DATE OF THE ACC THE PLT WAS REPORTEDLY GIVEN A 1.2 HR PART 135 CHECK RIDE BY THE COMPANY ASST CHIEF PLT. THE VACUUM PUMP DRIVE WAS FOUND SHEARED WITH THE SHEARED ENDS POLISHED, INDICATING THAT THE DRAYING END WAS STILL ROTATING AFTER SHAFT SEPARATION. ONE VACUUM DRIVEN GYRO WAS FOUND SHOWING NO EVIDENCE OF ROTATION AT IMPACT. THE GYRO FROM THE ELECTRICALLY POWERED TURN & BANK SHOWED NO SIGNS OF ROTATION AT IMPACT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW85FA078
- Event ID
- 20001214X41774
- Case number
- FTW85FA078
- 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 1984-12-18.
- API snapshot SHA-256: 3af9699c7677ecb3b4c1d9981f7a4b8ac879e85343117194590a003c8e684dad; retrieved 2026-09-21T05:12:29.436Z.