FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR25FA007 · Beech 95-B55

8 Oct 2024 · Avalon, CA, United States

Beech 95-B55 · Accident during initial climb

From an unrecorded airport to Santa Monica Municipal Airport (SMO)

Report a problem

Event

NTSB case
WPR25FA007
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
Ongoing
API-reported fatalities
5 · 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
Unknown

Beech 95-B55

Aircraft type
Beechcraft 55
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
N73WA
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Santa Monica Municipal Airport (SMO), Santa Monica, CA
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
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
Initial climb
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
Unknown or undetermined
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

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. 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. 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. Catalina Airport is a non-towered airport located on a flat plateau with descending terrain on either end of the runway. The reported airport elevation is 1,601 ft mean sea level (msl). Airport operating hours are 0800-1700 and the single concrete runway, runway 4/22, was not equipped with runway lighting and night operations are not permitted. 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 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. The airplane subsequently landed at AVX at 1820. The pilots shut down both engines, loaded the stranded pilots, and attempted to restart the engines. 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 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 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, heard what sounded like a normal departure. 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. 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. Preliminary ADS-B 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 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. 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 wreckage was recovered and transported to a secure location for examination later. 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.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record WPR25FA007
Event ID
20241009195282
Case number
WPR25FA007
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
  • 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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2024-10-09.
  • API snapshot SHA-256: 2c58e24a07db943318efd942ebf25714d9f624dc0d50a0f25d9dc4f159a08876; retrieved 2026-09-15T08:59:13.396Z.
  • Corrected after a review of the NTSB narrative, which states these values explicitly: damage. The narrative states the airplane "was destroyed when it was involved in an accident".