LAX01FA049 · Beech BE-55-D55
Beech BE-55-D55 · Accident: in flight collision with object on approach
From Show Low Regional Airport (SOW) to Greenlee County Airport (CFT)
Event
- NTSB case
- LAX01FA049
- 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
- 1 · all aircraft and ground
- Ground fatalities
- 0
- 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 BE-55-D55
- Aircraft type
- Beechcraft BE-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
- N7901R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Show Low Regional Airport (SOW), Show Low, AZTo Greenlee County Airport (CFT)
- 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 pattern final
- First occurrenceThe 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Pole
- 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
- Pilot in command › Altitude/clearance, not maintained
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Proper glidepath, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The twin-engine airplane impacted a utility pole about 1,250 feet short of the runway while conducting an approach during dark night light conditions. A witness located at the airport observed the airplane make three attempts to land, and on the fourth, the airplane veered to the left and burst into flames. He added he had turned his vehicle lights on at the approach end of the runway so the pilot would be able to land. The same witness indicated he observed the runway lights prior to the accident when another aircraft landed earlier in the evening. The airport utilized a pilot control lighting system, which requires the pilot to key the communication radio mike seven times over the common traffic advisory frequency within 5 seconds to illuminate the runway edge lights on their highest intensity. The runway edge lights would then remain illuminated for a period of 15 minutes from the most recent time of activation. Another pilot, who utilized the airport on the day of the accident, reported no discrepancies with the lighting system 30 minutes prior to and following the accident. A postaccident examination of the communication radios could not determine which frequency the pilot had selected. The aircraft's altimeter face was located in the wreckage and was set so that it was reading approximately 150 feet higher than the aircraft's actual altitude. Another airport, located 22 miles from the accident site, utilized continuous runway lighting between sunset and sunrise.
Probable cause
the pilot's improper in-flight decision to attempt a landing on an unlit runway at night, and his failure to maintain the proper glide path and clearance from obstacles while on final approach, which resulted in the collision with a utility pole. A contributing factor was his failure to divert to an airport with constant runway lighting.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01FA049
- Event ID
- 20001212X22298
- Case number
- LAX01FA049
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2000-12-01.
- API snapshot SHA-256: ed10b3e64588760e8178c825fa957ddc481d5bb560b4741afddc07e585018856; retrieved 2026-09-20T20:44:34.532Z.