Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

April 5, 2010 · Maule M-5-210C · N62040

Bismarck, ND

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
April 5, 2010
Injury Outcomes
No injuries (4 uninjured)
Location
Bismarck, ND
Aircraft
Maule M-5-210C
Tail Number
N62040
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CEN10CA191

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.

NTSB Probable Cause

Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Crosswind correction-Not attained/maintained - C

Full 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.

Flight

Event TypeAccident
Event Time19:41 CDT
Nearest AirportBismarck Municipal Airport (0nm)
Runway31
Runway Length8794 ft
Runway Width150 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftMaule M-5-210C
Tail NumberN62040
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsTeledyne Continental Motors · IO-360-D33B · Reciprocating · 300
Seats4

People & Injuries

Injury SummaryNo injuries (4 uninjured)
Fatal0
Serious0
Minor0
Uninjured4
Total4
Crew 1Age 50 · Second Class · None

Conditions

ConditionsVMC
LightDaylight
Wind240° @ 10 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point48 / 23 C
Altimeter29.79 inHg
Observation Time00:52
Weather SourceWFAC

Appendix: Source Data