CEN24FA057 · Beech A23-24
Beech A23-24 · Accident: loss of engine power (total) during initial climb
From Wiley Post Airport (PWA) to Shawnee Regional Airport (SNL)
Event
- NTSB case
- CEN24FA057
- 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
- 2 · 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 A23-24
- Aircraft type
- Beechcraft 23
- 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
- N6945Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wiley Post Airport (PWA), Oklahoma City, OKTo Shawnee Regional Airport (SNL), Shawnee, OK
- Aircraft age
- About 55 years (built 1968)
- 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
- Loss of engine power (total)
- 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
- Aircraft › Aircraft power plant
- Aircraft › Fluids/miscellaneous hardware
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and his passenger were conducting a personal flight when, about 1.5 minutes after takeoff, the airplane entered a left turn back toward the airport. The pilot told the tower controller that he was returning to land because the engine was losing power and subsequently declared an emergency. During the pilot’s transmissions, the engine was heard in the background running roughly. The tower controller cleared the pilot to land on any runway and issued the current surface wind condition. Witnesses reported that the engine was running roughly and there was smoke trailing from the airplane. The airplane impacted a concrete rubble pile at a concrete recycling facility about 0.4 nautical mile (nm) from the runway threshold. An extensive postimpact fire thermally damaged most of the airplane.
Postaccident examination of the pilot’s hangar revealed evidence of non-recent minor oil leaks often seen on hangar floors, and there was no evidence of an oil leak between the hangar and the asphalt taxiway. However, evidence of a significant oil leak and puddling was observed on the taxiway where the pilot likely started the airplane engine. The oil leak was consistent with the airplane being stationary for an extended period with the engine running. The nose landing gear subsequently deposited an easily discernible, dark black, oily tire track as the airplane began its taxi toward the runup pad and the runway.
Additional evidence of a significant oil leak and puddling was observed on the runup pad where the pilot likely completed his before takeoff engine runup checks. Finally, evidence of an oil leak was observed where the airplane came to stop before the hold short lines for the departure runway. Based on the available evidence, the engine oil system likely began leaking shortly after the engine was started and continued during the taxi, before engine runup, takeoff, and climb portions of the flight. The pilot was likely unaware of the significant engine oil system leak before takeoff.
Postaccident examination of the engine revealed evidence of multiple connecting rod separations due to a lack of oil lubrication. However, the extensive thermal damage to the engine and its oil system components precluded determination of the source of the oil leak.
FAA toxicological testing of postmortem samples taken during the pilot’s autopsy detected multiple impairing substances. However, these impairing substances likely were administered during the pilot’s postaccident medical care and therefore did not cause any impairment at the time of the accident. Additionally, toxicological testing conducted on a hospital blood draw obtained from the pilot about 37 minutes after the accident did not detect any tested-for substances, which included ethanol, opiates, fentanyl, and benzodiazepines.
Probable cause
A total loss of engine power due to multiple connecting rod failures from oil starvation associated with an extensive before takeoff oil system leak, the source of which could not be identified due to postaccident fire damage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24FA057
- Event ID
- 20231210193501
- Case number
- CEN24FA057
- 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, 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: 1abb219656d00fc85fbb347e74a09c3f67b08875a70fb500de9dbb92ce711ce8; retrieved 2026-09-15T08:09:10.057Z.