FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25FA185 · MX Aircraft Tech PTY Ltd MXS

24 Apr 2025 · Hampton, VA, United States

MX Aircraft Tech PTY Ltd MXS · Accident: flight control system malfunction/failure during landing

From Smyrna Airport (MQY) to an unrecorded destination

Report a problem

Event

NTSB case
ERA25FA185
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
1 · all aircraft and ground
Ground fatalities
0
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

MX Aircraft Tech PTY Ltd MXS

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
N530RH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Smyrna Airport (MQY), Smyrna, TNTo not recorded
Aircraft age
About 6 years (built 2019)
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
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
Flight control system malfunction/failure
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 systems
  • Aircraft › Fluids/miscellaneous hardware

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

NTSB narrative

The pilot of the aerobatic airplane was on approach to a runway at the destination airport at the conclusion of a cross-country flight. According to a witness, and electronic data recovered from avionics onboard the airplane, the airplane leveled off about 50 ft above the runway and flew straight down the runway for several hundred feet. The airplane then pitched up and then down before it pitched up to a nose high pitch attitude and climbed several hundred feet. The airplane then rolled 90° to the left, pulled over the top of a loop, and descended before impacting the ground.

Postaccident examination of the airplane at the accident site revealed that that a counterweight plug that normally would have been installed in the left elevator was not present and was found on the ground about 10 ft behind the wreckage. The counterweight plug for the right elevator was found installed and tight. The left elevator counterweight plug threads were intact, about half of the circumference of the counterweight plug displayed gouging, and an area showed evidence of paint transfer. The horizontal stabilizer structure adjacent to the left elevator position where the counterweight plug would have been installed displayed dents and paint scrapes consistent with contact with the counterweight plug. A washer beneath a screw secured to the horizonal stabilizer structure (near where the paint scrapes were observed) was also dented. Metallurgical examination revealed that both the washer and screw had thickness profiles that matched the marks in the outer diameter edge on the counterweight plug and that the marks were consistent with the washer having made repeated contact with plug.

The elevator counterweight plugs were part of a custom feature that the pilot requested the airframe manufacturer incorporate into the elevator during its construction. The airframe manufacturer described the plugs as a short-term solution and they did not provide any instructions for continuing airworthiness, to include torque values to be used when installing the plugs. The manufacturer also stated the plug design incorporated an o-ring that would serve as a secondary locking mechanism. No o-ring was found on the recovered plug at the accident site, nor was one found on the still-installed right elevator’s counterweight plug. Additionally, the plugs found installed on the accident airplane differed dimensionally from those specified in a design document provided by the airframe manufacturer.

Based on the available information, it is likely that the left elevator counterweight plug loosened during the flight until it made contact with the washer and screw in the horizontal stabilizer, sufficient to jam the elevator. This ultimately resulted in the pilot being unable control the airplane during the landing, and the subsequent impact with terrain.

Probable cause

A counterweight plug that loosened during the accident flight, jammed the elevator, and resulted in loss of control during landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA25FA185
Event ID
20250424200061
Case number
ERA25FA185
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, cause areas. 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: 8a58bd007b512d2d220b26e2bac6679edcadf874063a26cfa14db39ae76b4183; retrieved 2026-09-15T09:04:14.247Z.