ASN Wikibase Occurrence # 141786
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Saturday 7 January 2012 |
| Time: | 16:28 |
| Type: |  Beechcraft 58P Baron |
| Owner/operator: | Private |
| Registration: | N580TC |
| MSN: | TJ-126 |
| Total airframe hrs: | 5740 hours |
| Fatalities: | Fatalities: 0 / Occupants: 5 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | John Wayne-Orange County Airport - KSNA, Santa Ana, CA -
 United States of America
|
| Phase: | Landing |
| Nature: | Private |
| Departure airport: | Santa Barbara, CA (KSBA) |
| Santa Ana, CA (SNA) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Sources:
NTSB
FAA register: https://www.ocregister.com/2012/01/08/airport-runway-reopens-after-planes-hard-landing/
https://www.faa.gov/data_research/accident_incident/preliminary_data/events01/media/06_580TC.txt
http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=580TC
https://www.ntsb.gov/aviationquery/brief.aspx?ev_id=20120206X15258&key=1
https://flightaware.com/live/flight/N580TC
https://www.ocregister.com/2012/01/08/airport-runway-reopens-after-planes-hard-landing/
https://www.faa.gov/data_research/accident_incident/preliminary_data/events01/media/06_580TC.txt
http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=580TC
https://www.ntsb.gov/aviationquery/brief.aspx?ev_id=20120206X15258&key=1
https://flightaware.com/live/flight/N580TC
Accident investigation:
 |
|
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 09-Jan-2012 16:48 | Geno | Added |
| 09-Jan-2012 17:35 | RobertMB | Updated [Aircraft type, Narrative] |
| 09-Jan-2012 19:40 | RobertMB | Updated [Date] |
| 15-Feb-2012 15:34 | Geno | Updated [Time, Source, Damage, Narrative] |
| 21-Dec-2016 19:26 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 27-Nov-2017 17:53 | ASN Update Bot | Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
| 20-Nov-2022 22:11 | Ron Averes | Updated [Location, Departure airport, Destination airport, Source] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2023 Flight Safety Foundation