LAX08FA092 · Beech 95-B55
Beech 95-B55 · Accident: loss of control in flight on approach
From Safford Regional Airport (SAD) to Benson Municipal Airport/Paul Kerchum Field (E95)
Event
- NTSB case
- LAX08FA092
- 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 95-B55
- Aircraft type
- Beechcraft 55
- 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
- N20480
- Operator
- James Robertson
- Onboard fatalities
- Unknown
- Route
- From Safford Regional Airport (SAD), Safford, AZTo Benson Municipal Airport/Paul Kerchum Field (E95), Benson, 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
- Approach · VFR go-around
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A witness at the airport reported that the airplane's first approach for landing in dark night conditions appeared high and fast. Prior to touchdown, the pilot announced over the common traffic frequency that he was going around. During the second approach, which the witness reported as not as high and fast as the first approach, the airplane was about 10 feet above ground level when it passed the midfield point on the 4,000-foot runway. The witness lost sight of the airplane behind a hangar, but heard what sounded like a hard landing, followed by the sound of increasing engine sounds. The witness looked over the hangars and saw a green light (right wing tip) arc to the left as if the airplane were rolling inverted. The airplane collided with the ground in a near-inverted, slightly nose-down attitude and came to rest between the runway and the taxiway. Postcrash examination of the airframe and flight control systems found no anomalies. The left engine was examined and subsequently placed in a test cell. The engine started easily and ran smoothly at various rated power settings. The right engine was subject to a teardown inspection. The disassembly of the engine did not reveal any preexisting anomalies that would have precluded normal operation of the engine. Both propellers had impact marks on the spinner from contact with a counterweight while the blade/counterweight was at a low pitch position. There were no impact marks or other indications to suggest that either propeller was feathered. Both propellers were turning and were driven toward a lower blade angle at impact as evidenced by the damage to the low pitch stop. A review of the private pilot's flight logbook indicated the pilot had accumulated approximately 274 hours total flight time in all aircraft, with only 29 hours in the aircraft type and 5 hours of night flying experience logged.
Probable cause
The pilot's misjudged speed and altitude during approach that led to a long landing and his subsequent failure to maintain control during an attempted go-around. Contributing to the accident were the dark night, the pilot's low total night flight experience, and low total time in the make and model airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08FA092
- Event ID
- 20080410X00449
- Case number
- LAX08FA092
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2008-04-03.
- API snapshot SHA-256: 56acd94d224c6ab814b78f97ec3c2108c0c91476c3afacd9bc92fa9ca4b11f6c; retrieved 2026-09-13T19:01:59.272Z.