LAX08CA147 · Beech B-23
Beech B-23 · Accident: loss of control in flight during landing
From Twentynine Palms Airport (TNP) to Bagdad Airport (E51)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- LAX08CA147
- 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 B-23
- Aircraft type
- Beechcraft B-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
- N4026T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Twentynine Palms Airport (TNP), Twenty Nine Pal, CATo Bagdad Airport (E51), Bagdad, AZ
- 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 · flare/touchdown
- 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 control in flight
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot said he had just purchased the airplane in California and was returning to his home in Texas. He was in the landing flare when a gust of wind blew the airplane off the side of the runway. He attempted to go around, but the landing gear impacted some rocks on the left side of the runway. The outboard 10 feet of the right wing was wrinkled and compressed aft, and the bottom of the empennage was badly wrinkled and compromised. The airplane came to rest approximately 185 feet from the runway. The reported winds at Prescott, Arizona, located 37 nautical miles east of the accident airport, were from 350 degrees at 11 knots gusting to 17 knots.
Probable cause
The pilot's inadequate compensation for the wind conditions and failure to maintain runway alignment. Contributing factors were the gusty crosswind weather conditions and the rocky terrain adjacent to the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08CA147
- Event ID
- 20080527X00732
- Case number
- LAX08CA147
- 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. 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: be154952e18542f46bc2c5a9a9fa13b3915bdecfed72f5acc75727201af8eab0; retrieved 2026-09-15T09:41:20.294Z.