# NTSB LAX08CA285: Mason Falconar F-11, N65017, Creswell, OR, August 28, 2008 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 28, 2008, 09:55 local (16:55 UTC) - Place: Creswell, OR - Coordinates: 43.930831, -123.007225 - Nearby events: https://openairdocs.org/map.md?lat=43.9308&lon=-123.0072&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report January 22, 2009 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 68826 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX08CA285 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/68826/pdf - Page: https://openairdocs.org/ntsb/LAX08CA285 ## Probable cause The pilot's failure to maintain a stabilized approach, inadequate recovery from a bounced landing, and failure to maintain directional control. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Mason FALCONAR F-11, 1 case](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=0566118), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Mason FALCONAR F-11, 1 case](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=0566118), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/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: [Mason FALCONAR F-11, 1 case](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=0566118), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/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: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Mason FALCONAR F-11, 1 case](https://openairdocs.org/ntsb-events/092/sequence.md?model=0566118), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Mason FALCONAR F-11, 1 case](https://openairdocs.org/ntsb-events/230/sequence.md?model=0566118), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) ## Analysis The pilot entered the traffic pattern and planned to land on runway 33. Initially, no traffic was observed in the pattern; however, just before announcing the base turn another airplane pilot announced that he was turning base for runway 33. The pilot observed the other airplane, which was ahead of his airplane, and he extended his downwind leg for spacing. The pilot indicated that he needed to perform a series of "S" turns to "delay landing" for spacing with the preceding airplane while heading back to the runway's center line. The pilot stated that he arrived over the threshold with above normal sink rate and below normal forward speed. The airplane bounced on the runway, the pilot lost directional control, and the airplane ground looped. The airplane came to rest in the grass with a collapsed left main landing gear. Upon the pilot's subsequent examination of the airframe, he observed that the left wing spar was cracked. The pilot said that the airplane's final approach flight path was not stabilized and that he should have performed a go-around. ## Factual narrative According to the accident pilot, he took off for the local area personal flight at 0925. After performing a few maneuvers and sightseeing, he returned to the airport, entered the traffic pattern, and planned to land on runway 33. Initially, no traffic was observed in the pattern. However, just before announcing "turning base" another airplane pilot announced that he was turning base for runway 33. The accident pilot observed the other airplane, which was ahead of his airplane, and he extended his downwind leg for spacing. Thereafter, the accident pilot indicated that he needed to perform a series of "S" turns to "delay landing" while heading back to the runway's center line. The pilot stated that he arrived over the threshold with above normal sink rate and below normal forward speed. The airplane bounced on the runway, the pilot lost directional control, and the airplane ground looped. The airplane came to rest in the grass with a collapsed left main landing gear. Upon the pilot's subsequent examination of the airframe, he observed that the left wing spar was cracked. The pilot acknowledged in his completed "Pilot/Operator Aircraft Accident Report" that the airplane's final approach flight path was not stabilized, and he should have performed a go-around. ## Aircraft - Registration: [N65017](https://openairdocs.org/deregistered/N65017-2012-11-26), registration cancelled 2012-11-26, S/N 6249, built 1982 (OpenAirDocs) - Reported make and model: Mason Falconar F-11 - Registry model: [Mason FALCONAR F-11](https://openairdocs.org/model/mason-falconar-f-11) (registry code 0566118) (OpenAirDocs) - Registry engine: [Lycoming 0-290 series](https://openairdocs.org/engine/lycoming-0-290-series) (registry code 41506, 4 cycle) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 6249 - Engines: Lycoming O-290 reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Annual, July 1, 2008 - Departed: 77S, Creswell, OR - Destination: 77S, Creswell, OR - Airport: 77S, Hobby Field, runway 33, 3,101 × 60 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 69; injuries: none; private; airplane ratings: single-engine land; medical: class 3; seat: left; flight hours: 245 total, 1 in this make and model, 12 in the last 90 days, 6 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none ## 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 20080828844759A](https://openairdocs.org/incident/20080828844759A), Aug 28, 2008: Amtr FALCONARF11, Creswell, OR, Substantial damage. (-23) [privacy data omitted] stated he ground looped the aircraft after a one half hour local flight at the Hobby Field Airport at Creswell, Oregon. He stated… 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.