ASN Wikibase Occurrence # 212267
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: | Friday 15 June 2018 |
| Time: | 17:00 |
| Type: |  Beechcraft A35 Bonanza |
| Owner/operator: | Private |
| Registration: | N580B |
| MSN: | D-1599 |
| Year of manufacture: | 1948 |
| Total airframe hrs: | 2481 hours |
| Engine model: | Continental O-360 SERIES |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | South of Hesperia Airport (L26), Hesperia, CA -
 United States of America
|
| Phase: | Landing |
| Nature: | Private |
| Departure airport: | Hesperia, CA (L26) |
| Torrance Airport, CA (TOA/KTOA) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The pilot was conducting a personal flight; witnesses reported that the takeoff and initial climb appeared
normal, however something came off the airplane near the end of the runway. The airplane climbed to about 800 ft before the nose dropped and it made a "radical left turn." After the turn, the wings appeared vertical and the airplane lost about 400 ft. The airplane leveled out and appeared to be going back toward the airport, however the nose remained low. The airplane turned right and appeared to align with a road. The airplane then struck powerlines that were parallel to the road, impacted the ground, caught on fire, and came to rest inverted.
The mechanic who worked on the airplane the day before the accident, reported that the airplane had quite a few maintenance issues; he completed a few maintenance items that the pilot wanted fixed. However, the mechanic indicated to the pilot that he shouldn't fly the airplane until the remaining work could be completed.
The pilot purchased the airplane less than a year before the accident. The airplane's most recent maintenance logbook entries were inconsistent and contained date corrections. In addition, there was a 6-7 year gap between the most recent logbook entries with about 27 hours recorded on the tachometer during that time.
Wreckage documentation revealed that several pieces of the spinner and spinner bulkhead had separated shortly after takeoff and were found on the departure end of the runway. Some of the screws remained attached to the spinner and were undamaged, however, a majority of the screw holes were ripped. Metallurgical examination revealed that the fractures across the rivets and rivet holes were consistent with progressive fatigue crack growth. However, post-accident examination of the airframe and engine revealed no other anomalies that would
have precluded normal operation. Damage signatures to the propeller blades were consistent with the engine producing power at the time of impact and it appears that the pilot should have been able to maintain sufficient altitude and airplane control to return to the airport.
Further, the pilot was likely attempting to return to the airport when he abruptly reversed course and lost excessive altitude that resulted in the collision with the powerline. Because the maintenance on the airplane had not been completed yet by the mechanic, the pilot's decision to fly an unairworthy airplane was improper.
Whether the pilot's underlying medical conditions or effects from his use of tramadol, an opioid, and
meprobamate, a tranquilizer, both impairing substances, contributed to his unsafe decision-making, could not be determined.
Probable Cause
The pilot's failure to maintain airplane control during an attempted return to the airport following the separation of the spinner bulkhead during takeoff as a result of fatigue cracking. Contributing to the accident was the pilot's improper decision to fly an unairworthy airplane.
Accident investigation:
 |
|
Sources:
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/97484/pdf
http://abc7.com/small-plane-crashes-near-hesperia-airport-sparking-brush-fire/3607606/
http://ktla.com/2018/06/15/officials-responding-to-plane-crash-that-sparked-brush-fire-near-hesperia-airport/
http://www.vvng.com/2-dead-following-small-plane-crash-in-hesperia/
http://losangeles.cbslocal.com/2018/06/15/2-reportedly-dead-in-small-plane-crash-in-hesperia/
http://www.vvdailypress.com/news/20180615/authorities-two-killed-in-plane-crash-near-hesperia-airport-friday-afternoon
http://triblive.com/usworld/world/13766966-74/authorities-2-dead-in-small-plane-crash-on-california-road
http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=580B
https://www.flickr.com/photos/92009354@N00/36945346536/
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 16-Jun-2018 01:26 | Geno | Added |
| 16-Jun-2018 01:58 | Geno | Updated [Departure airport, Source, Narrative] |
| 16-Jun-2018 05:38 | Geno | Updated [Aircraft type, Source, Narrative] |
| 18-Jun-2018 18:47 | Geno | Updated [Aircraft type, Registration, Cn, Operator, Source] |
| 12-Jan-2019 21:58 | BEAVERSPOTTER | Updated [Aircraft type, Cn] |
| 26-Aug-2020 09:11 | ASN Update Bot | Updated [Time, Operator, Nature, Departure airport, Destination airport, Source, Narrative] |
| 26-Aug-2020 09:14 | harro | Updated [Destination airport, Source, Narrative] |
| 18-Apr-2022 13:49 | aaronwk | Updated [Source, Narrative] |
| 18-Apr-2022 13:50 | harro | Updated [Accident report] |
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:
©2024 Flight Safety Foundation