The National Transportation Safety Board last week released the preliminary report on the October plane crash that claimed five lives on Catalina Island. Another year or two may pass before the NTSB issues a final report.
According to the NTSB preliminary report, the manager of the Airport in the Sky advised the pilot against taking off after sunset. The pilot insisted he had to go.
The NTSB classified the investigation as “Class 3,” which “seek to identify safety issues that reveal underlying cause(s) of the accident,” according to ntsb.gov.
“The investigation is led by an investigator-in-charge, who may be assisted by other NTSB subject matter experts if the investigation requires an in-depth focus on a specific area. The investigative team may travel to the scene of the accident or to other follow-up activities, or the entirety of the investigation may be conducted remotely,” according to ntsb.gov.
“Following a final technical review of the gathered facts and analysis of those facts, a final report will be made available to the public following Board approval that identifies the probable cause(s) of the accident and factors that contributed to the outcome of the accident, if any,” according to ntsb.gov.
“A probable cause of the crash, along with any contributing factors, will be detailed in the final report, which is expected in 12-24 months,” according to the NTSB.
Report
The following text is from the report. Items in brackets [] were inserted for clarity.
“On October 8, 2024, at 2005 Pacific daylight time, a Beech 95-B55, N73WA, was destroyed when it was involved in an accident near Avalon, California. The pilot, two pilot rated passengers, and two student pilot passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight,” according to the unsigned report.
“On the afternoon of October 8, a flight instructor and two student pilots were preparing to depart Catalina Airport (AVX), Avalon, in a rented, single engine airplane WPR25FA007
“The rental airplane experienced a magneto malfunction during preflight, which prevented them from departing. The stranded pilots contacted the flight school they had rented the airplane from and were informed another airplane would fly to AVX from Santa Monica Municipal Airport (SMO), Santa Monica, California, to pick them up and fly them back to SMO,” the report said.
The report described the Catalina airport as being on a flat plateau without a control tower.
“Airport operating hours are 0800-1700 [8 a.m. to 5 p.m.] and the single concrete runway, runway 4/22, was not equipped with runway lighting and night operations are not permitted,” the report said.
“Information provided by the flight school indicated that the responding airplane was not operated by the flight school and belonged to an acquaintance of the owner of the flight school,” the report said.
“The airport manager at AVX stated that he gave the pilots permission to land at AVX after closing hours, and relayed to them they had to depart before sundown at 1831 [6:31 p.m.]. The airplane subsequently landed at AVX at 1820. The pilots shut down both engines, loaded the stranded pilots, and attempted to restart the engines,” the report said.
“During restart the right engine would not start due to insufficient battery power. The occupants exited the airplane, and an extension cord was then attached to an on-board battery charger,” the report said.
“The pilots were informed by the airport manager that since the time required to charge the battery would extend beyond sunset that a post-sunset departure would not be approved,” the report said.
“The pilot / airplane owner informed the airport manager that he had to go and intended to depart anyway. The airport manager advised him that, while he could not stop him, his departure would be unapproved and at his own risk. The airport manager then went to his residence, and about 2000 [8 p.m.], heard what sounded like a normal departure,” the report said.
“Airport security video captured the airplane taking off on runway 22. The video showed dark night conditions were present as the airplane came into view during the takeoff roll about 2004 [8:04 p.m.]. It was not possible to discern in the video if the airplane was airborne or not prior to reaching the end of the runway. As the airplane reached the departure end of the runway it descended out of view of the camera,” the report said.
“Preliminary ADS-B [Automatic Dependent Surveillance–Broadcast] data showed that the airplane may have become airborne around midpoint of the runway and maintained a low altitude until reaching the departure end of the runway. The ADS-B data showed the airplane continued a slight descent after takeoff followed by a right turn until the data ended about 0.6 miles west of the departure end of runway 22,” the report said.
“The airplane impacted the east face of a ridgeline about 0.7 miles west of the last recorded ADS-B target and about .96 miles west-southwest of the departure end of runway 22 at an elevation of about 1,230 ft msl [mean sea level],” the report said.
“Ground scars were consistent with the airplane striking the ground on a 280° heading in a wings level attitude with the landing gear extended. The main wreckage came to rest in a ravine about 450 ft west of the initial impact point,” the report said.
“According to the airport manager, the sky at the time of the accident was clear from the airport surface and above, and there was a light breeze from the North Northwest, approximately perpendicular to the runway. An hour post-accident he observed cloud tops approximately 200 feet below airport elevation off the departure end of the runway. The wreckage was located below the cloud tops,” the report said.
As previously reported, the remains of the five individuals on board the plan were recovered on Oct. 9.
The accident number for the case is WPR25FA007.
