Maule M-7-260C accident near Kanab, Utah, May 21, 2026
On May 21, 2026 at about 10:26 pm local time, a 2000 Maule M-7-260C, registered N261MM, was substantially damaged in an accident during landing (landing roll) near Kanab, Utah (Kanab Municipal Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s failure to maintain directional control during the landing roll with gusting crosswind conditions.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 21, 2026 · about 10:26 pm local time · cases in 2026
- Place
- Kanab, Utah · Kanab Municipal Airport · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Maule M-7-260C, built 2000 · all M-7-260Cs on the register
- Registration
- N261MM · registry record · serial 30015C
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot of the tailwheel equipped airplane reported that, during the landing roll, and prior to the tailwheel contacting the runway surface, a gust of wind moved the tail of the airplane to the right. The pilot attempted to correct with right rudder input, followed by alternating right and left rudder inputs. However, the airplane ground looped to the left, and the right main landing gear collapsed. During the ground loop, the right wing struck the ground, which resulted in substantial damage to the right wing and aileron. The pilot reported that, at the time of the accident, he was landing the airplane on runway 1 with a west-northwest wind at 10 knots, gusting to 19 knots. According to the pilot, there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
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
- Loss of control on ground during landing (landing roll) defining event
- Attempted remediation/recovery during landing (landing roll)
- Landing gear collapse during landing (landing roll)
The NTSB's findings
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- Environmental issues › Conditions/weather/phenomena › Wind › Crosswind › Effect on operation
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 469 hours in all; 13.5 in this make and model; 13.5 in the last 90 days; 13.5 in the last 30 days; 410 as pilot in command
- Last flight review: May 21, 2026
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 1,421.6 hours
- Last inspection: type not recorded, May 9, 2026; 13 hours since
- Maximum gross weight: 2,500 lb
- Seats: 5
- Landing gear: fixed
- Engine: Lycoming IO-540 (piston); 0 hours total
The flight
- Departed from: CNO Chino CA at 7:45 pm
- Flight plan: none
- Runway 1, 6,200 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 320° at 10 knots, gusting 17
- Visibility: 10 statute miles
- Temperature: 82°F (28°C), dew point 16°F (-9°C)
- Altimeter: 29.95 inHg
- Observation at 4:15 pm from KKNB
Weather report (METAR): METAR KKNB 212215Z AUTO 32010G17KT 10SM MM 28/M09 A2995 RMK A01=
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 3 pictures from the NTSB's docket, as the NTSB released them
Photograph 1 – View of accident airplane
Photograph 2 – View of right wing damage
Photograph 3 – View of right aileron damageThe NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
2 documents, released by the NTSB on July 9, 2026. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
| 2 | Investigation Photographs | PDF, 4 pages · our copy | View Download |
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
- N261MM on the register today · the tail number may have moved to another aircraft since
- Maule M-7 275 registered today · the model family and its accident history
- Maule 1,346 aircraft on the register
- Engine: Lycoming IO-540 4,222 aircraft carry this series today · as the NTSB recorded it
- Kanab Municipal · nearest airport
- Chino Airport · departed from
- Accidents and incidents in Utah 1,440 since 1982 · 263 in the last ten years
- Utah 8,357 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR26LA200.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.