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

Quicksilver MX II accident near Brady, Texas, April 11, 2025

On April 11, 2025 at about 10:20 pm local time, a 2025 Quicksilver MX II, an amateur-built aircraft,, registered UNREG, was substantially damaged in an accident during maneuvering near Brady, Texas. It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The airplane’s encounter with a dust devil, which resulted in a loss of airplane control at a low altitude.

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

What the record shows

Date
April 11, 2025 · about 10:20 pm local time · cases in 2025
Place
Brady, Texas · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Quicksilver MX II Sprint, built 2025, amateur-built
Registration
UNREG · registered outside the United States · serial UKN
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported that while conducting a slow flight maneuver for flight testing purposes in an unregistered airplane, he felt a “heavy push up” on the airplane to about 75 ft above ground level. The right wing then lifted and the pilot lost control of the airplane which entered a left descending spiral. The airplane subsequently impacted terrain and came to rest inverted. A witness reported that he observed dust devil weather activity where the airplane was flying at the time of the accident. The airplane sustained substantial damage to the fuselage, both wings, and the empennage. The pilot reported there were no preimpact 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

  1. Loss of control in flight during maneuvering defining event
  2. Other weather encounter during maneuvering
  3. Attempted remediation/recovery during maneuvering
  4. Collision with terrain or object (not controlled flight into terrain) during maneuvering

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Attain/maintain not possible
  • Environmental issues › Conditions/weather/phenomena › Wind › Dust devil/whirlwind › Effect on equipment
  • Environmental issues › Conditions/weather/phenomena › Wind › Dust devil/whirlwind › Ability to respond/compensate
  • Environmental issues › Conditions/weather/phenomena › Wind › Dust devil/whirlwind › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 325 hours in all; 325 as pilot in command
  • Medical certificate: Sport Pilot
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 1 hours
  • Last inspection: inspection type not recorded, April 10, 2025
  • Maximum gross weight: 750 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 582EGB (piston); 1 hours total

The flight

  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 75°F (24°C), dew point 0°F (-18°C)
  • Observation at 5:20 pm

Injuries

FatalSeriousMinorNone
Flight crew1

Photographs from the investigation 1 picture from the NTSB's docket, as the NTSB released them

The 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

3 documents, released by the NTSB on August 21, 2025. 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.

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

2026-07-07CEN26LA246 · accident near Hooker, OK · substantial damage · minor injuries
2026-02-28CEN26LA131 · accident near Van Burensburg, IL · substantial damage · no injuries
2025-10-13ERA26LA017 · accident near Gaffney, SC · substantial damage · serious injuries
2025-09-27CEN25LA397 · accident near Harvard, IL · substantial damage · no injuries
2025-09-12CEN25LA385 · accident near Rossville, IN · substantial damage · serious injuries
2025-07-07CEN25LA242 · incident near Ingram, TX · minor damage · no injuries
2025-06-18DCA25WA305 · accident near N/A · serious injuries
2025-05-01OPS25LA034 · incident near Washington, DC
2025-01-30DCA25MA108 · accident near Washington, DC · destroyed · fatal
2024-12-21DCA25LA065 · accident near Orlando, FL · substantial damage · serious injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/CEN25LA155.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.