FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA18FA114 · Beech V35 A

25 Mar 2018 · Hydro, OK, United States

Beech V35 A · Accident: VFR encounter with IMC en route

From Odessa Schlemeyer Field (ODO) to El Reno Regional Airport (RQO)

Report a problem

Event

NTSB case
ERA18FA114
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
2 · 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
Instrument Meteorological Cond

Beech V35 A

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
N7019N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Odessa Schlemeyer Field (ODO), Odessa, TXTo El Reno Regional Airport (RQO), El Reno, OK
Aircraft age
About 51 years (built 1967)
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 · cruise
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
VFR encounter with IMC
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The commercial pilot and passenger completed a cross-country flight earlier the day of the accident. Before departing on the night visual flight rules (VFR) return flight, the pilot called flight service for a weather briefing. The flight service specialist provided the pilot with information pertinent to the flight, which included a forecast for instrument flight rules (IFR) conditions for the destination airport area. The pilot stated to the specialist that he could fly IFR if he needed to; however, review of the pilot's logbooks found no entries to indicate that he met currency requirements for instrument flight or that he met night currency requirements for passenger carriage. The pilot expressed concern for cloud conditions to personnel at the airport before departing but chose to conduct the flight.

As the flight neared the destination airport, the pilot, who was receiving VFR flight-following services, stated to the controller that he was unable to visually identify the destination airport. The controller subsequently suggested another airport located west of the destination. This airport was not equipped with a weather observation system, although a nearby airport was reporting VFR conditions. The pilot diverted toward the suggested airport and passed about 1 mile south of the runway but was not able to visually identify the airport, likely due to a low cloud layer. Several radio transmissions between the pilot and controller indicated that the airplane was flying in and out of instrument meteorological conditions (IMC) during this time.

Shortly thereafter, the pilot was informed that his original destination was reporting IFR conditions. The pilot stated to the controller that he would attempt to fly to the destination airport by flying west to get under the clouds, then maneuvering east under the clouds toward the destination.

Radar track data showed that, during the final 2 minutes of the flight, the airplane conducted two left, descending, 360° turns, starting about 2,100 ft above ground level (agl) and leveling off about 500 ft agl. The airplane continued straight and level for about 20 seconds until radar contact was lost. The wreckage was located about 0.25 mile from the last radar return. The debris path was scattered over several hundred feet of flat, open farm field, consistent with a high-speed impact in a shallow descent; the airplane's landing gear and flaps were not configured for landing. A postaccident examination of the airplane did not reveal any anomalies consistent with a preimpact failure or malfunction.

Two other airports about 35 miles southwest of the accident site, which were located within the airplane's fuel endurance capability, reported VFR conditions throughout the evening. However, the pilot did not request further assistance from air traffic control in maintaining VFR or navigating to an airport with more favorable weather conditions rather than attempting to fly under the low cloud ceilings.

The airplane's radar track is consistent with the pilot's stated intention to fly underneath the cloud layer and navigate to his destination airport under the clouds. While maneuvering, it is likely that the pilot experienced spatial disorientation due to the dark night instrument meteorological conditions and the lack of visual references provided by the farm fields over which he was flying. The changes in the airplane's altitude and heading depicted on radar and the distribution of the wreckage consistent with a high-speed impact are also consistent with the known effects of spatial disorientation.

Probable cause

The pilot's decision to continue the night visual flight rules flight into instrument meteorological conditions, which resulted in a loss of control due to spatial disorientation. Contributing was the pilot's lack of instrument/night currency, and his failure to request additional assistance from air traffic control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA18FA114
Event ID
20180326X01910
Case number
ERA18FA114
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2018-03-26.
  • API snapshot SHA-256: 5ca6ad19b9542cb10d4066d3a80b372a689ef376aeac9a5e531fecba3a1a5e31; retrieved 2026-09-15T06:37:01.519Z.