WPR15LA132 · Beech B23
Beech B23 · Accident: loss of control on ground during landing
From Flagstaff Pulliam Airport (FLG) to Flagstaff Pulliam Airport (FLG)
Event
- NTSB case
- WPR15LA132
- 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 B23
- 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
- N7628R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Flagstaff Pulliam Airport (FLG), Flagstaff, AZTo Flagstaff Pulliam Airport (FLG), Flagstaff, AZ
- Aircraft age
- About 46 years (built 1969)
- 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 · landing roll
- 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 on ground
- 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 › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot reported that, during the takeoff roll for the local personal flight, the nosewheel seemed to turn slightly to the left. Rudder input maintained a straight path on the runway centerline, but the nosewheel side-skidded for a few seconds before the airplane lifted off. When the airplane returned for landing, the pilot stated that touchdown was smooth and uneventful. During the landing roll, the nosewheel turned slightly left, and he attempted to correct with full right rudder. The airplane continued to veer to the left, exited the runway, and impacted a precision approach path indicator (PAPI) light. The pilot stated that he felt that the right rudder bungee did not have enough pull to stop the nosewheel from continuing to turn more sharply to the left. However, a postaccident examination of the airplane and nosewheel steering mechanism did not reveal any mechanical anomalies that would have precluded normal operation. Thus, it is likely that the pilot failed to maintain directional control of the airplane during landing.
Probable cause
The pilot's failure to maintain directional control during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR15LA132
- Event ID
- 20150323X10548
- Case number
- WPR15LA132
- 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: 5a8b5d92931475f83f87f364dfdfc954960ce3e8116da40e4a10b56edaa1db8c; retrieved 2026-09-16T02:10:22.597Z.