FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12CA215 · Maule M-7-260

6 May 2012 · Brigham City, UT, United States

Maule M-7-260 · Accident: loss of control on ground during landing

From Brigham City Regional Airport (BMC) to Brigham City Regional Airport (BMC)

Report a problem

Event

NTSB case
WPR12CA215
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Maule M-7-260

Aircraft type
Maule M-7
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N7ZF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Brigham City Regional Airport (BMC), Brigham City, UTTo Brigham City Regional Airport (BMC), Brigham City, UT
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control on ground
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

According to the pilot, after a 1-hour local flight, he performed a flyover of the airport and noted that the windsocks at both ends of the runway indicated calm wind. The pilot stated that he flew a normal left pattern. As he turned the airplane onto the base leg, he checked to make sure the airplane was configured for landing. On final approach, he looked down the runway and determined that no crosswind correction was needed. The landing flare and touchdown were normal. However, on the landing roll, the tail veered to the right. The pilot increased power in an attempt to go around, but the airplane was already turning around, and the right wing was lifting. He reduced the power and attempted to maintain airplane control, but the right main landing gear collapsed, and the airplane veered off the runway and came to a stop. After exiting the airplane, the pilot noted over the next few minutes gusting wind conditions from the north, west, and northwest between 5 and 10 knots. The pilot further stated that he has experience landing in gusty wind conditions, but on the day of the accident the crosswind was variable and unpredictable. The airplane sustained damage to the landing gear, wing tip, and aileron.

Probable cause

The pilot’s failure to maintain directional control while landing with a gusting crosswind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12CA215
Event ID
20120517X05337
Case number
WPR12CA215
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: aa134f090b81cbd403c517fb2e509da2b74bfc89450cb4d51ab7edb638f01c37; retrieved 2026-09-15T18:08:47.649Z.