FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12LA097 · Beech 58P

7 Jan 2012 · Santa Ana, CA, United States

Beech 58P · Accident: landing gear not configured

From Santa Barbara Municipal Airport (KSBA) to John Wayne Orange County International Airport (SNA)

Report a problem

Event

NTSB case
WPR12LA097
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 58P

Aircraft type
Beechcraft 58
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
N580TC
Operator
Unknown
Onboard fatalities
Unknown
Route
From Santa Barbara Municipal Airport (KSBA), Santa Barbara, CATo John Wayne Orange County International Airport (SNA), Santa Ana, CA
Aircraft age
About 35 years (built 1977)
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
Landing gear not configured
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

  • Personnel issues › Task performance

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

NTSB narrative

The pilot of the twin-engine airplane was on a sightseeing diversion while en route to an airport when two "ALT" annunciator lights on the instrument panel illuminated, and the load meters indicated that the alternators were not providing electrical power to the airplane. The pilot powered off some electrical equipment and recycled both alternator switches. The "ALT" annunciator lights extinguished, and all other indications returned to normal. Since nightfall was approaching and the pilot was concerned about the continued availability of electrical power, he then headed for his destination. When the airplane was on short final, the pilot noticed that none of the three green landing gear position annunciator lights were illuminated despite the fact that he had selected the landing gear down. He reported this information to the air traffic control tower controller, conducted a go-around, and asked for the controller's observations regarding the landing gear position. The pilot misunderstood the air traffic controller's communication that the landing gear was not extended. Subsequently, the pilot did not recycle the gear and did not review or execute any abnormal checklist procedures for the landing gear. Although the landing gear warning horn sounded during the second landing approach, the pilot incorrectly believed that the landing gear was extended and landed the airplane with the landing gear fully retracted. Although the landing was accomplished 31 minutes before local sunset and 58 minutes before the end of local civil twilight, the pilot did not go around again due to his concern about approaching nightfall.

While the airplane was in temporary storage awaiting postaccident examination, the owner of the repair facility, who had previously repaired the landing gear system and had conducted the most recent annual inspection on the airplane, gained unapproved access to the airplane, operated the landing gear, and inadvertently damaged the airplane. Subsequent examination of the airplane by investigators revealed that the landing gear system operated normally, and no irregularities were revealed with the electrical system.

According to the airplane manufacturer, without alternator augmentation, the airplane battery would have lasted about the same amount of time that it took for the flight to depart and reach the location where the pilot first noticed the electrical anomaly. Based on this information and the fact that the airplane had been tampered with, no detailed component testing was accomplished, and the root causes of the initial electrical anomaly and failure of the landing gear to extend could not be determined.

Probable cause

The pilot’s failure to review or execute any applicable checklist procedures or troubleshoot or take corrective action before landing despite indications that the landing gear was not extended. Contributing to the accident were the pilot’s misunderstanding of the air traffic controller’s communication that the landing gear was not extended, his desire to land quickly, and an undetermined electrical system anomaly.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12LA097
Event ID
20120206X15258
Case number
WPR12LA097
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 2012-01-08.
  • API snapshot SHA-256: 297bbb1cea9d14fc801d0cd3d153d7ba95847f5d7845ca2b0d54763907ea2ed8; retrieved 2026-09-15T17:10:57.730Z.