- Date
- April 4, 2010, 19:41 local (Apr 5, 2010, 00:41 UTC)
- Place
- Bismarck, ND
- Injuries
- 4 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N62040Maule M-5-210C
- Defining event
- Landing-flare/touchdown: Hard landing
- Weather
- Visual (VMC) · Day
- Status
- Completed · report August 12, 2010
- Report
- Approved by Office Director
- NTSB office
- Central Region
- Parties
- Federal Aviation Administration - Fargo FSDO
- FAA report
- 20100404031209A
- Case key
- 75654
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The pilot’s failure compensate for the crosswinds resulting in a loss of directional control while landing.
Findings · 4
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
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
- Reported as
- Maule M-5-210C
- Category
- Airplane
- Serial number
- 6073C
- Airframe hours
- 1,220
- Engine
- 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
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 50
- Injuries
- None
- Certificate
- 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
Docket · 1
The files NTSB released with the investigation on May 25, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.