# NTSB CEN10CA191: Maule M-5-210C, N62040, Bismarck, ND, April 5, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: April 4, 2010, 19:41 local (Apr 5, 2010, 00:41 UTC) - Place: Bismarck, ND - Coordinates: 46.772777, -100.745834 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=46.7728&lon=-100.7458&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: 4 uninjured - Status: Completed, report August 12, 2010 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Federal Aviation Administration - Fargo FSDO - NTSB case key (mKey): 75654 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN10CA191 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/75654/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=75654 - Page: https://openairdocs.org/ntsb/CEN10CA191 ## Probable cause The pilot’s failure compensate for the crosswinds resulting in a loss of directional control while landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: crosswind correction](https://openairdocs.org/ntsb-findings/01062030): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Maule M-5-210C, 1 case](https://openairdocs.org/ntsb-findings/01062030/cases.md?model=5460134), [All aircraft, 184 cases](https://openairdocs.org/ntsb-findings/01062030/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: [Maule M-5-210C, 4 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=5460134), [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: [Maule M-5-210C, 4 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=5460134), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Response/compensation; cases with it: [Maule M-5-210C, 1 case](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=5460134), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/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: [Maule M-5-210C, 1 case](https://openairdocs.org/ntsb-events/092/sequence.md?model=5460134), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing-flare/touchdown: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Maule M-5-210C, 2 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=5460134), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Maule M-5-210C, 4 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=5460134), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Maule M-5-210C, 3 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=5460134), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Maule M-5-210C, 5 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=5460134), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot was attempting a crosswind landing on runway 31 in a tailwheel equipped airplane. He reported that the airplane began to sink during the landing flare, which resulted in a bounced landing. After the airplane touched down for the second time, the pilot pushed the control yoke forward, raising the tail, to ensure that the main landing gear stayed on the runway and to mitigate any potential for porpoising. He stated that his corrective actions were “not a very good move” with the crosswind condition, which resulted in reduced rudder effectiveness because the fuselage restricted airflow past the rudder control surface. The airplane veered off the left side of the runway, despite the pilot’s corrective inputs of right rudder and right brake. The airplane then ground-looped and struck a runway light. The right wing, right aileron and right elevator were substantially damaged. The pilot reported that there were no pre-impact mechanical malfunctions or failures that would have precluded normal operation of the airplane. He noted that the airplane was equipped with 26-inch diameter tires and single puck brakes. He suggested that with increased braking power, by the installation of dual puck brakes, his directional control would have been maintained. He also suggested that the use of another runway, better aligned with the wind, could have prevented the accident. A local weather station reported that the prevailing wind was out of the west-southwest between 10 and 15 knots. ## Factual narrative The pilot was attempting a crosswind landing on runway 31 in a tailwheel equipped airplane. He reported that the airplane began to sink during the landing flare, which resulted in a bounced landing. After the airplane touched down for the second time, the pilot pushed the control yoke forward, raising the tail, to ensure that the main landing gear stayed on the runway and to mitigate any potential for porpoising. He stated that his corrective actions were “not a very good move” with the crosswind condition, which resulted in reduced rudder effectiveness because the fuselage restricted airflow past the rudder control surface. The airplane veered off the left side of the runway, despite the pilot’s corrective inputs of right rudder and right brake. The airplane then ground-looped and struck a runway light. The right wing, right aileron and right elevator were substantially damaged. The pilot reported that there were no pre-impact mechanical malfunctions or failures that would have precluded normal operation of the airplane. He noted that the airplane was equipped with 26-inch diameter tires and single puck brakes. He suggested that with increased braking power, by the installation of dual puck brakes, his directional control would have been maintained. He also suggested that the use of another runway, better aligned with the wind, could have prevented the accident. A local weather station reported that the prevailing wind was out of the west-southwest between 10 and 15 knots. ## Aircraft - Registration: [N62040](https://openairdocs.org/aircraft/N62040), registered now, S/N 6073C, built 1975 (OpenAirDocs) - Reported make and model: MAULE M-5-210C - Registry model: [Maule M-5-210C](https://openairdocs.org/model/maule-m-5-210c) (registry code 5460134) (OpenAirDocs) - Registry engine: [Continental IO-360 series](https://openairdocs.org/engine/continental-io-360-series) (registry code 17025, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 6073C - Airframe hours: 1220 - Engines: Teledyne Continental Motors IO-360-D33B 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, February 18, 2010 - Departed: KFCM, Eden Prairie, MN - Destination: KBIS, Bismarck, ND - Flight plan: IFR - Airport: KBIS, Bismarck Municipal Airport, runway 31, 8,794 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 50; injuries: none; airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review February 25, 2010; seat: left; flight hours: 6,377 total, 300 in this make and model, 4,906 as pilot in command, 146 in the last 90 days, 54 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 240° at 10 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 48 °F, dew point 23 °F - Altimeter: 29.79 inHg - Observed at: KBIS ## 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 20100404031209A](https://openairdocs.org/incident/20100404031209A), Apr 4, 2010: Maule M-5-210C, Bismarck, ND, Substantial damage. The aircraft bounced on landing then came back down. The airman stated that he pushed forward on the yoke to stick the main gear on the runway and stop the… ## Docket (1 files) The files NTSB released with the investigation on May 25, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=75654. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40329514&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF 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.