The U.S. aircraft register, updated daily
Accidents · NTSB CEN10CA191 · Final report

Maule M-5-210C accident near Bismarck, North Dakota, April 5, 2010

On April 5, 2010, a Maule M-5-210C, registered N62040, was substantially damaged in an accident during landing (flare/touchdown) near Bismarck, North Dakota (Bismarck Municipal Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s failure compensate for the crosswinds resulting in a loss of directional control while landing.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
April 5, 2010 · cases in 2010
Place
Bismarck, North Dakota · Bismarck Municipal Airport · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 4 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Maule M-5-210C · all M-5-210Cs on the register
Registration
N62040 · registry record · serial 6073C
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Hard landing during landing (flare/touchdown) defining event
  2. Attempted remediation/recovery during landing (flare/touchdown)
  3. Loss of control on ground during landing (landing roll)
  4. Runway excursion during landing (landing roll)
  5. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Crosswind correction › Not attained/maintained
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Environmental issues › Conditions/weather/phenomena › Wind › Crosswind › Response/compensation

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 6,377 hours in all; 300 in this make and model; 146 in the last 90 days; 54 in the last 30 days; 4,906 as pilot in command; 0 on instruments
  • Last flight review: February 25, 2010
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 1,220 hours
  • Last inspection: annual inspection, February 18, 2010
  • Maximum gross weight: 2,500 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Teledyne Continental Motors IO-360-D33B (piston); 0 hours total

The flight

  • Departed from: KFCM Eden Prairie MN at 9:08 pm
  • Destination: KBIS Bismarck ND
  • Flight plan: IFR
  • Runway 31, 8,794 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 240° at 10 knots
  • Visibility: 10 statute miles
  • Temperature: 48°F (9°C), dew point 23°F (-5°C)
  • Altimeter: 29.79 inHg

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers3

Documents from the investigation the NTSB's docket: the evidence folder behind the report

1 document, released by the NTSB on May 25, 2010. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN10CA191.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.