ERA25LA296 · Maule MX-7-180A
Maule MX-7-180A · Accident: landing area overshoot
From Nantucket Memorial Airport (ACK) to an unrecorded destination
Event
- NTSB case
- ERA25LA296
- 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
- Event fatalities
- Unknown
- 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 MX-7-180A
- Aircraft type
- Maule MX-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
- N1052T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Nantucket Memorial Airport (ACK), Nantucket, MATo not recorded
- Aircraft age
- About 27 years (built 1998)
- 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
- Landing area overshoot
- 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
The pilot of the tailwheel-equipped airplane reported that he was attempting to land on a 750-ft-long, rough turf airstrip. He added that he had not landed at that airstrip in about 3 years. The pilot rejected the first landing attempt as the airplane touched down too long. During the second approach, the airplane touched down slightly beyond the intended touchdown point. The pilot applied light braking at first, but two the airplane bounced twice after cresting two small humps in the runway. The pilot again attempted to reject the landing and added full power to clear 8-ft reeds at the end of the runway; however, the propeller contacted the reeds, and the airplane began to decelerate. As the airplane decelerated, it nosed over and came to rest inverted beyond the end of the runway, resulting in substantial damage to the left wing and rudder. The pilot stated that there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to obtain a proper touchdown point while attempting to land on a very short and rough turf runway, which resulted in a runway overrun and collision with vegetation and terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA25LA296
- Event ID
- 20250812200768
- Case number
- ERA25LA296
- 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: 4830dbbd1bf1dfa74e1af2968bcddc5271914750782238471ee7582db59a107d; retrieved 2026-09-16T20:12:36.609Z.