FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24FA184 · Beech A45

7 Jun 2024 · Deer Harbor, WA, United States

Beech A45 · Accident: low altitude operation/event while maneuvering

From Skagit Regional Airport (BVS) to an unrecorded destination

Report a problem

Event

NTSB case
WPR24FA184
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
1 · 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
Visual Meteorological Cond

Beech A45

Aircraft type
Beechcraft 45
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
N268AF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Skagit Regional Airport (BVS), Burlington, WATo not recorded
Aircraft age
About 63 years (built 1961)
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
Maneuvering · aerobatics
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
Low altitude operation/event
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot was performing a flight around an island archipelago where he used to live, with the intention of also performing a flyby of a friend’s home. He was familiar with the route of flight and had performed the same flyby multiple times before. The friend stated that, in the past, the pilot often rocked the airplane’s wings during his flybys, but had never performed aerobatics. She stated that, during the accident flight, the airplane was flying at a higher altitude than on previous occasions. The left wing then dropped, and she thought this was part of the pilot’s usual routine; however, the wing continued to drop as the airplane began to rapidly descend toward the water. The airplane began to pull out of the dive, but by the time it had recovered to an almost wings-level, upright attitude, the belly impacted the water.

Video of the accident recorded by another witness in the vicinity showed the airplane inverted and diving, in what appeared to be the early stages of an aerobatic maneuver consistent with a splitS. Video analysis indicated that the airplane began the maneuver about 1,800 ft above the water. Its flight path followed a constantradius arc which, at its lowest point, extended 30 feet below the water’s surface.

Examination of the airframe and engine showed no evidence of preaccident malfunction. Video footage indicated that the engine was operating during the descent and appeared to be producing power at impact. Damage to the airplane’s altimeter precluded a determination of its operating status at the time of the accident; however, its Kollsman window was set correctly for local atmospheric conditions.

The pilot had an extensive and distinguished career in human spaceflight and aviation, and according to family members exhibited a lifelong pattern of maintaining high standards and conservative flying habits. Evidence suggests, however, that as he aged the pilot became less rigid in maintaining those standards. As an example, he was not wearing a personal floatation device during the accident flight despite his self-imposed rule of doing so when flying over water. Additionally, although it was reported that he never performed aerobatics without wearing a parachute, the pilot did perform a barrel roll the week before the accident without wearing one. According to the pilot’s son, performing a split-S maneuver at such a low altitude and with such little margin for error would have been out of character for the pilot. The pilot’s decision to perform the flyby at a higher altitude than usual suggests that he likely intended to perform the maneuver, but misjudged the entry altitude.

The pilot’s medical profile included conditions typical for a 90-year-old, and evidence suggested that behaviorally he demonstrated impatience with other aircraft in the traffic pattern and was struggling with the communications equipment in another similar airplane. About 10 years before the accident, he voluntarily stopped flying aerobatics at airshows and flying higherperformance airplanes because he was concerned about damaging them. He shifted instead to simpler, seasonal flying in the accident airplane type—the airplane in which he originally learned to fly—and had recently stopped flying solo in congested airspace. Nevertheless, the pilot’s son stated that his flying skills were still excellent.

Although regulations permit any authorized flight instructor to conduct a flight review, the pilot’s son served as the pilot’s exclusive reviewer and recurrent instructor. This resulted in a lack of independent oversight, and due to family dynamics and the power disparity associated with the pilot’s experience, this arrangement may have limited the candid identification of riskincreasing behaviors or degrading skills.

The pilot’s autopsy report indicated his cause of death was a result of multiple blunt force injuries. The examination identified moderate coronary artery disease, but did not identify other significant natural diseases. As a result of his heart disease, the pilot was at some increased risk of a sudden impairing or incapacitating cardiac event, such as chest pain, arrhythmia, or heart attack. However, such an event does not leave reliable autopsy evidence if it occurs immediately before death. The pilot also would have been experiencing the effects of elevated G-forces during the maneuver. Pilot tolerance to G-forces is affected by multiple factors, including magnitude and duration of the acceleration, the individual’s training and level of fitness, and other health factors. However, the coordinated manner in which the maneuver was performed indicated that the pilot was actively controlling the airplane throughout. Thus, it is unlikely that the effects of the pilot’s coronary artery disease or encounter with elevated G-forces contributed to the accident.

Probable cause

The pilot’s decision to perform an aerobatic maneuver at low level, and his misjudged entry altitude for the maneuver, which resulted in impact with water.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24FA184
Event ID
20240607194417
Case number
WPR24FA184
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: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: df29842b04061b37571d33b3e00e6e7d0318ff21ba8c946e648101bc630bfb45; retrieved 2026-09-15T08:16:35.259Z.