N4267H

HISTORY OF FLIGHTOn June 25, 2022, about 1823 central daylight time, a Mooney M20J, N4267H, was destroyed when it was involved in an accident near Kerrville, Texas. The pilot and passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 flight.

The pilot and passenger arrived at Kerrville Municipal Airport/Louis Schreiner Field (ERV) about 1700 on the day of the accident, having been flown inbound by a friend from Dublin Municipal Airport (9F0).

The airplane had undergone an annual inspection that was completed in December 2021. The accident pilot, who was the airplane’s owner, was unable to pick up the airplane following the inspection, so it remained with the maintenance facility until the day of the accident. The accident flight was the first time the pilot had flown the airplane since the inspection.

Review of low-resolution airport security video showed the pilot arrive at the airplane about 1734 and perform what appeared to be a walk around and preflight inspection. Thirteen minutes later both the pilot and passenger had boarded, and an engine start was attempted. Over the next 10 minutes, the engine was seen to turn at least 12 times, but not start. The pilot then got out of the airplane and walked around the wings and reached over to both the left and right fuel caps. He then boarded the airplane again. Over the next two minutes multiple engine restarts were attempted, until 1802, the engine appeared to start, and the video ended.

There were no security cameras that recorded the airplane’s takeoff, and no witnesses came forward to report they had observed the initial takeoff sequence. Runway 12 was active at the time of the accident, and there were no other airplanes in the traffic pattern or on the runway about the time of the accident.

Automatic dependent surveillance-broadcast (ADS-B) data provided by the FAA did not capture the takeoff sequence but indicated that about 1819 the airplane was on an east-northeast track, about 2 miles east of the departure end of runway 12 at an altitude of about 1,775 ft mean sea level (msl), about 150 ft above ground level (agl). When combined with field wind conditions, the data revealed that the airplane was traveling at an airspeed of about 70 knots calibrated. Over the next two minutes, the airplane began a 180° left turn, while traveling about 80 knots. The airplane began to accelerate as it rolled out of the turn, reaching 96 knots as it approached runway 30. The last recorded target indicated the airplane was about 150 ft agl, 1,700 ft short of the runway 30 threshold, while tracking on the runway heading.

About this time, a witness, who was a retired professional pilot with an airline transport pilot rating was driving eastbound on a parallel highway, just south of the runway. He stated that he was passing about midfield when he saw a Mooney airplane approaching runway 30 with the landing gear extended at an altitude of about 150 ft agl. He knew the winds that day were favoring the southeast and wondered why the airplane was making what appeared to be a downwind landing on runway 30. He thought the pilot may have been practicing an instrument approach but noticed that the airplane appeared to be flying erratically in both the lateral and vertical axis. He stated that the propeller was turning and there was no fire, smoke, or other signs of distress. As the flight progressed, the airplane turned slightly right and became offset to the north of the runway centerline while maintaining altitude. He then lost sight of the airplane as he continued to travel along the highway.

Another witness traveling along the same highway observed a Mooney airplane flying over runway 30, but not climbing. He assumed it had just taken off and was concerned because the wind favored the opposite runway, and the weather was hot. He watched as the airplane continued traveling in a northwest direction, in a manner that he described as “mushing.” It was very close to the treetops when it appeared to make a turn to the left. The witness thought this was a left base turn for runway 12, but the bank angle became very steep, and the airplane disappeared behind trees (see Figure 1).

ADS-B data provided by a publicly available collection service (ADS-B Exchange) recorded position data during the return leg to the airport. The data appeared to match the witness observations and showed that the airplane flew directly over the takeoff runway at an altitude of about 100 ft agl before making a 10° turn to the right. The airplane continued at the same altitude for the next 1.25 miles before beginning a left turn almost 800 ft southeast of the accident site.

A southeast-facing security camera located on the wall of a school, about 3/4 mile northwest of the approach end of runway 12, captured the last 2 seconds of the flight. The video showed that the airplane was flying southwest just above the tree line while in a left bank of about 45°. The airplane continued to roll left until the underside was completely visible as it descended into the trees and a fireball ensued.

Figure 1 – Composite flight track. Green: FAA ADS-B. Red: ADS-B Exchange. PERSONNEL INFORMATIONThe pilot’s most recent FAA medical took place almost 21 years before the accident on November 19, 2001. There were no records indicating he was operating under the provisions of BasicMed.

Multiple flight instructors from the pilot’s base in the Dublin and Stephensville area of Texas were contacted. None stated that they had provided the pilot any recent flight training. One instructor recounted that he had given the pilot initial training in 2001 through to his first solo flight. He reported that the pilot was stubborn and often refused to use his checklist. The instructor was made aware that shortly after receiving his solo endorsement the pilot was flying passengers while still a student. When he approached the pilot to discuss, the pilot stated that he no longer wanted to use him as an instructor. The pilot reportedly found another instructor to complete his training.

Burnt remnants of the pilot’s logbooks were found in the wreckage. Thermal damage prevented an accurate assessment of total flight time; however, the endorsement pages were largely intact. The last endorsement was dated August 11, 2004, and was for a 14 CFR 61.56 flight review.

A friend, who was also a pilot and had flown with him, stated that he was generally procedure-oriented, and on occasion was overcome by operational tasks and could sometimes “get behind” the airplane.

The passenger was a recent acquaintance of the pilot and did not hold a pilot certificate. AIRCRAFT INFORMATIONBecause the airplane sat unused for so long since inspection, in advance of the arrival of the pilot the maintenance facility flew a test flight on June 23. During that flight, it was found that the directional gyro was inoperative. The gyro was replaced the following day and another test flight was flown. The test pilot stated that beyond the problems with the directional gyro, the test flights were uneventful and the engine started without issue.

According to the owner of the maintenance facility, during the period when the airplane was not flown it sat on the ramp outside and was brought into the hangar during heavy storms.

When the pilot originally brought the airplane in for the annual inspection, he stated that the engine could be hard to start. However, according to the maintenance facility owner, no anomalies were found, and the engine started normally if the engine start checklist was followed.

The pilot also reported to him that on one occasion the landing gear circuit breaker popped after takeoff while the landing gear was being retracted, causing it to remain partially extended. The pilot cycled the circuit breaker and the landing gear retraction cycle completed normally. The maintenance facility owner tried to duplicate the discrepancy during the annual inspection by cycling the landing gear multiple times but he was not able to get the circuit breaker to pop and the gear cycled normally. He examined the landing gear system but was not able to find any anomalies.

An employee at a local fixed base operator on the airport recalled that about the time of the accident he heard a radio transmission from a pilot stating that he was having landing gear trouble and was coming back to the airport.

Fuel

The day before the accident the airplane was serviced by the maintenance facility with 25.1 gallons of 100 low-lead aviation fuel to the fuel level indicators, or “tabs,” which would have indicated that each tank contained 25 gallons of fuel (32 gallons capacity).

The fueling facility tested the fuel batch immediately following the accident and the results were nominal. Three other airplanes were serviced from the same fuel truck on the day of the accident. None of those pilots reported problems and a review of commercially available flight tracking software confirmed that those aircraft had reached their destinations. METEOROLOGICAL INFORMATIONAt the time of the accident wind speed was 10 knots from 190° and the density altitude was about 4,480 ft. AIRPORT INFORMATIONBecause the airplane sat unused for so long since inspection, in advance of the arrival of the pilot the maintenance facility flew a test flight on June 23. During that flight, it was found that the directional gyro was inoperative. The gyro was replaced the following day and another test flight was flown. The test pilot stated that beyond the problems with the directional gyro, the test flights were uneventful and the engine started without issue.

According to the owner of the maintenance facility, during the period when the airplane was not flown it sat on the ramp outside and was brought into the hangar during heavy storms.

When the pilot originally brought the airplane in for the annual inspection, he stated that the engine could be hard to s...