# NTSB WPR14CA139: Bayer Oscar Starduster SA300, N490B, San Luis Obispo, CA, March 19, 2014 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: March 19, 2014, 14:20 local (21:20 UTC) - Place: San Luis Obispo, CA - Coordinates: 35.242778, -120.651107 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=35.2428&lon=-120.6511&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report May 21, 2014 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 88935 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR14CA139 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/88935/pdf - Page: https://openairdocs.org/ntsb/WPR14CA139 ## Probable cause The pilot's inadequate flare, which resulted in a bounced landing and subsequent loss of aircraft control during landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Bayer Oscar STARDUSTER SA300, 1 case](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=86603AG), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Bayer Oscar STARDUSTER SA300, 1 case](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=86603AG), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Bayer Oscar STARDUSTER SA300, 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=86603AG), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Bayer Oscar STARDUSTER SA300, 1 case](https://openairdocs.org/ntsb-events/090/sequence.md?model=86603AG), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Bayer Oscar STARDUSTER SA300, 1 case](https://openairdocs.org/ntsb-events/230/sequence.md?model=86603AG), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) ## Analysis The pilot reported that during touchdown in the tailwheel equipped airplane, it bounced once, and as the airplane main landing gear made contact with the runway, the right landing gear strut collapsed. The pilot lost directional control and the airplane ground looped. The fuselage and right wing sustained substantial damaged. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Factual narrative The pilot reported that during touchdown in the tailwheel equipped airplane, it bounced once, and as the airplane main landing gear made contact with the runway, the right landing gear strut collapsed. The pilot lost directional control and the airplane ground looped. The fuselage and right wing sustained substantial damaged. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Aircraft - Registration: [N490B](https://openairdocs.org/aircraft/N490B), registered now, S/N 1994 (OpenAirDocs) - Reported make and model: BAYER OSCAR STARDUSTER SA300 (NO SERIES) - Registry model: [Bayer Oscar STARDUSTER SA300](https://openairdocs.org/model/bayer-oscar-starduster-sa300) (registry code 86603AG) (OpenAirDocs) - Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 1994 - Airframe hours: 2213 - Engines: LYCOMING IO360 SER 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Condition, March 18, 2014, 0 hours before - Departed: SBP, San Luis Obispo, CA - Destination: SBP, San Luis Obispo, CA - Airport: SBP, San Luis County Rgnl, runway 29, 6,100 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 88; injuries: none; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review November 14, 2012; seat: rear; restraint: 3-point; flight hours: 15,575 total, 2,172 in this make and model, 9,705 as pilot in command ## Weather - Conditions: Visual (VMC), Day - Wind: 220° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 73 °F, dew point 36 °F - Altimeter: 30.03 inHg - Observed at: KSBP ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20140319003459A](https://openairdocs.org/incident/20140319003459A), Mar 19, 2014: Bayer Oscar STARDUSTER SA300, San Luis Obispo, CA, Substantial damage. The aircraft was landing on runway 29 at sbp (San Luis Obispo regional airport). The wind was 240 at approximately 10 knots. The aircraft landed hard causing… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.