N7019N

HISTORY OF FLIGHTOn March 25, 2018, about 2137 central daylight time, a Beech V35A, N7019N, was destroyed when it impacted terrain near Hydro, Oklahoma. The commercial pilot and passenger were fatally injured. The airplane was owned by the pilot who was operating it as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. Night instrument meteorological conditions prevailed, and no flight plan was filed for the flight, which departed from Odessa Airport-Schlemeyer Field (ODO), Odessa, Texas, about 1947, and was destined for El Reno Regional Airport (RQO), El Reno, Oklahoma.

The pilot and passenger departed RQO earlier in the day and arrived at ODO about 1345. A line technician at the ODO fixed-base operator (FBO) reported that the passenger left the airport shortly after the airplane arrived and the pilot remained in the terminal. The FBO technician reported that the pilot asked that weather radar and satellite information be displayed on a large monitor throughout the afternoon, as the pilot stated to him that he was "concerned with the clouds."

Review of an audio recording from Leidos Flight Service in Austin, Texas, revealed that the pilot called for a weather briefing at 1806. The pilot informed the flight service specialist that he was planning a visual flight rules (VFR) flight from ODO to RQO in about 30 minutes and it would be about a 2.5-hour flight. During the 11-minute call, the flight service specialist provided the pilot with numerous weather and flight information details.

The flight service specialist informed the pilot that multiple AIRMETs affected his route of flight. The specialist stated that one AIRMET was for "IFR [instrument flight rules] right at your destination," developing between 1900-2200, "shortly after you depart Odessa." The pilot stated, "I don't see that being a problem right now, I can see things are changing out here. Things look good v-f-r at Odessa." The specialist responded, "yeah, this isn't a problem about Odessa, it's about your destination. Your first part of your route isn't the problem, it might be that last part. Can you go i-f-r if you need to?" The pilot responded, "yeah, I can if I need to." The specialist and pilot continued the briefing for another 7 minutes; an audio recording of the entire call is available in the public docket.

Review of air traffic control audio provided by the Federal Aviation Administration (FAA) revealed that the pilot requested VFR flight following services upon departure from ODO, and radio communications were uneventful for about the first 1 hour 40 minutes of the flight. About 2120, the pilot checked in with the Oklahoma City Terminal Radar Approach Control Facility (OKC approach) and was provided with the current altimeter setting.

About 2125, the OKC approach controller asked the pilot if he had RQO in sight. The pilot stated that he did not and informed the controller that he was trying to "get down underneath it [clouds]" and asked for the reported weather at Oklahoma City Airport (OKC). The controller informed him that OKC reported a ceiling of 1,100 ft agl, which the pilot acknowledged. About 2126, the controller informed the pilot that Hinton Municipal Airport (2O8), Hinton, Oklahoma, was to the west about 5 miles, and asked if he would like to try that airport. The pilot acknowledged the suggestion and began to navigate toward 2O8.

About 2128, the controller informed the pilot that Hinton was at his 12 o'clock and 3 miles. The pilot did not respond. The controller attempted to contact the pilot two additional times, and on the third attempt, instructed the pilot to 'ident' the transponder. At 2128:56, the pilot responded, "I'm hearing you, I'm still trying to get out of these clouds here uh I'm uh headed over towards Hinton right now but I'm going to go back out to the west and see if I can get underneath [the clouds]."

About 2129, the OKC controller instructed the pilot to contact the Fort Worth Air Route Traffic Control Center (ZFW center) controller and informed the pilot that he was actually in ZFW's airspace at that time. The pilot did not respond. For the next 1.5 minutes, the OKC controller attempted to contact the pilot three additional times and, on the fourth attempt, he instructed the pilot to click his microphone twice if he could hear the transmission. The pilot did not respond, and no microphone clicks were heard on the audio recording.

About 2131, the pilot transmitted, "…uh I'm still uh trudging out to the west here I'm still trying to get back out of it uh could you give me the el reno [weather]." The OKC controller asked the pilot how he heard the transmission. The pilot did not respond. The ZFW controller attempted to contact the pilot, but the pilot did not respond. The OKC controller attempted to contact the pilot again, and the pilot told the controller to go ahead. The OKC controller informed the pilot that he could not tell if he could hear him or not.

About 2132, the pilot responded to the OKC controller, "okay I'm I'm uh I'm trying to uh I'm still trying to get out of this I I see it's clear above I'm just going to climb back up here." Seventeen seconds later, the OKC controller informed the pilot that the weather at RQO included 7 miles of visibility with an 800-ft overcast ceiling. The pilot responded, "…okay that explains it alright very good." The OKC controller told the pilot to contact ZFW center and advised him that ZFW center had radar contact on the airplane and that they would work with him. The pilot acknowledged.

About 2133, the pilot transmitted on the OKC approach frequency, "…Fort Worth center … we're uh back v f r on top again." The OKC controller advised the pilot that he was still transmitting on OKC approach control frequency. The pilot acknowledged and switched to the ZFW center frequency. At 2133:19, the pilot contacted the ZFW controller and reported that he was at 3,500 ft. The ZFW controller asked the pilot his intentions, to which the pilot responded, "okay my intentions are now that I've got myself out of the clouds, I'm back up on top here I'm going to try to go out to the west and get and slide in underneath it." The controller asked where he was flying to the west and where the pilot wanted to get back to. The pilot responded, "okay I'll try and go out towards Hinton Oklahoma and uh I'll try and get on the outskirts of this overcast and try to go underneath it to go to uh el reno." The controller acknowledged the transmission.

About 2138, the ZFW controller informed the pilot that radar contact was lost and asked the pilot to say his altitude. The pilot did not respond. The controller attempted to contact the pilot three additional times, but there were no further communications received from the pilot.

Review of radar data provided by the FAA revealed that the airplane was established on a northeasterly course toward RQO when, about 2125 and 8 miles from the airport, the airplane turned north, then west toward the town of Hinton, Oklahoma. The airplane continued flying west, passing Hinton Airport (2O8) about 1 mile south at 2,700 ft mean sea level (msl), and then flew southwest. At 2134, the airplane was about 7 miles south of Hydro, Oklahoma, flying southwest at 3,850 ft msl. Figure 1 shows the airplane's flight path and change of course.

Figure 1: Overview of Radar Flight Path

The radar track showed the airplane subsequently enter two left, descending, 360° spiral turns, leveling off about 2,200 ft msl. The airplane then flew north for about 20 seconds; the last radar target, at 2137, showed the airplane flying at 2,125 ft msl on a heading of 033° at 157 knots groundspeed. The final radar target was about 1/4 mile southwest of the accident site. Figure 2 depicts the spiral flight path.

Figure 2: Closer View of Final Few Minutes of Radar Flight Path

A witness, who was traveling southbound in his car on a road about 1/2 mile west of the accident site about the time of the accident, saw a "steady red light" and a "steady white light" travel over his car. He continued watching the lights out of his driver's side window for about 10 to 15 seconds, looking eastward, as the lights continued to get lower in his field of view; suddenly, he observed a bright "yellow glow" ignite. He attempted to drive to where he observed the bright yellow glow, but the light extinguished before he could reach the area.PERSONNEL INFORMATION

According to FAA airman records, the pilot held a commercial pilot certificate with ratings for airplane single- and multi-engine land and instrument airplane. The pilot was issued an FAA second-class medical certificate on January 18, 2018. At that time, the pilot reported civil flight experience that included 4,500 total hours and 2 hours in the previous 6 months.

A review of the pilot's logbook contained a record of flights between August 30, 1994 and March 23, 2011. The total recorded flight time accumulated in this logbook was 2,580.5 hours. The logbook showed that his most recent flight review endorsement was dated September 2, 2016.

The most recent instrument proficiency check was dated December 27, 2001.

Another logbook located in the wreckage contained flight entries starting in December 2, 2010 and ending on March 9, 2018. The entries were for flights specific to the accident airplane and contained numerous entries by the accident pilot, as well as entries from other pilots who had flown the airplane. The last logbook entry recorded by the accident pilot was on March 5, 2018. Reviewing the accident pilot's entries from February 27, 2016, through the last entry, he recorded a total time of 55.8 hours in the accident airplane. Within the previous 12 months, he recorded 8.3 hours. The accident pilot noted one-night landing on September 3, 2016, and two additional night landings on February 27, 2016. Additionally, within the remarks section, the accident pilot noted two instrument approaches for two separ...