FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09CA466 · Beech A23-19

26 Sept 2009 · Tehachapi, CA, United States

Fly'n Oma's Aviation Beech A23-19 · Accident: landing area overshoot

From Apple Valley Airport (KAPV) to Tehachapi Municipal Airport (KTSP)

Report a problem

Event

NTSB case
WPR09CA466
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
0 · 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-19

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
N7944L
Onboard fatalities
Unknown
Route
From Apple Valley Airport (KAPV), Apple Valley, CATo Tehachapi Municipal Airport (KTSP), Tehachapi, 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
Landing
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
Landing area overshoot
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
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot stated that he overshot his turn to final and had to bank hard left to align with the center of the runway; as a result he was off to the extreme left side of the runway. He banked hard right to correct, and landed hard on the left edge of the runway. The airplane bounced and landed on the right side of the runway. The pilot stated that he added power in an attempt to salvage the landing; however, the airplane departed the runway, impacted a chain link fence, and came to rest nose down. The pilot stated that the airplane and engine experienced no mechanical failures or malfunctions during the flight.

Probable cause

The pilot's failure to attain an established approach path while on final approach resulting in an improper flare and bounced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09CA466
Event ID
20090926X30555
Case number
WPR09CA466
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. 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: 02acae10802c0be8779dcb2cd321d53daf47b3cf74f7755424fdbccb59f5113c; retrieved 2026-09-15T13:21:00.411Z.