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

Maule MX7 accident near Floydada, Texas, April 30, 2017

On April 30, 2017 at about 6:30 pm local time, a 1993 Maule MX7, registered N3035M, was substantially damaged in an accident during standing near Floydada, Texas (Floydada Muni airport). It was a positioning 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 decision to fly into and land at an area of known widespread high gusting wind, which resulted in a nose-over.

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

What the record shows

Date
April 30, 2017 · about 6:30 pm local time
Place
Floydada, Texas · Floydada Muni · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Maule MX7 180A, built 1993 · all MX7s on the register
Registration
N3035M · no longer on the register · serial 20004C
Damage
Substantial damage
Flight
Positioning 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 he was moving the airplane across the country for a friend and had multiple refueling stops along his route. He added that, on his first attempt to land on the asphalt runway, he conducted a go-around due to the strong crosswind, and during the subsequent approach, he landed in the grass next to the asphalt runway to touch down with a gusting headwind. Once stopped in the grass with the engine running, he radioed over the common traffic advisory frequency to ask for assistance to tie down the airplane, but after 5 to 10 minutes, no one had responded. He added, "suddenly" a wind gust lifted the left wing, and the airplane corkscrewed clockwise and nosed over. The right and left wing lift struts sustained substantial damage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The pilot reported that the wind was from 330° at 30 knots, gusting to 40 knots at the time of the accident. An automated weather observation station (AWOS), 22 nautical miles (nm) northwest from the accident site, recorded that, about the time of the accident, the wind was from 320° at 29 knots, gusting to 42 knots. Another AWOS, 32 nm southwest from the accident site, recorded that, about the time of the accident, the wind was from 320° at 29 knots, gusting to 43 knots. A review of the recorded hourly weather observations from the two AWOSs revealed that, from about 30 minutes before the pilot departed to 1 hour after the accident time, the wind remained consistent from the northwest about 30 knots, gusting to 38 to 46 knots. The pilot reported that he had on-board weather capability.

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. Preflight or dispatch event during prior to flight
  2. Other weather encounter during enroute (cruise)
  3. Loss of control on ground during standing defining event

The NTSB's findings

  • cause Personnel issues › Task performance › Planning/preparation › Weather planning › Pilot
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Pitch control › Attain/maintain not possible
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Environmental issues › Conditions/weather/phenomena › Wind › High wind › Decision related to condition
  • Environmental issues › Conditions/weather/phenomena › Wind › High wind › Ability to respond/compensate

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane; rotorcraft: helicopter
  • Flight time: 5,760 hours in all; 90 in the last 90 days; 30 in the last 30 days; 5,740 as pilot in command
  • Last flight review: October 24, 2016
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 1,919.9 hours
  • Last inspection: annual inspection, January 17, 2017
  • Maximum gross weight: 2,500 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360-C4F (piston); 1,940 hours total

The flight

  • Departed from: GYI Sherman/Denison TX at 2:00 pm
  • Destination: 41F Floydada TX
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 320° at 29 knots, gusting 42
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 52°F (11°C), dew point 27°F (-3°C)
  • Altimeter: 29.88 inHg
  • Observation at 6:35 pm from KPVW, 22 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Other NTSB records under N3035M the same tail number, which may have belonged to a different aircraft at the time

1982-11-11LAX83FA033 · accident near Coaling, CA · destroyed · no injuries

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.