GAA19CA092 · Maule MX7 180A
Ave Av Maule MX7 180A · Accident: loss of control on ground during landing
From Immokalee Regional Airport (IMM) to Immokalee Regional Airport (IMM)
Event
- NTSB case
- GAA19CA092
- 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
- 0 · all aircraft and ground
- 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 MX7 180A
- Aircraft type
- Maule MX7
- 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
- N9225G
- Operator
- Ave Av
- Onboard fatalities
- Unknown
- Route
- From Immokalee Regional Airport (IMM), Immokalee, FLTo Immokalee Regional Airport (IMM), Immokalee, FL
- Aircraft age
- Not recorded
- 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
- Loss of control on ground
- 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
- Environmental issues › Physical environment
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that, while administering a flight review, he took the flight controls to demonstrate a full-stall landing. During the landing roll, the airplane exited the right side of the runway. He increased power to abort the landing, and the left horizontal stabilizer struck a runway sign. He continued the climb the airplane and flew one pattern and landed. The airplane sustained substantial damage to the left horizontal stabilizer and the rudder. The instructor reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The flight instructor's failure to maintain directional control during the landing roll, which resulted in a runway excursion and a collision with runway signage during the subsequent attempted aborted landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA092
- Event ID
- 20181106X02059
- Case number
- GAA19CA092
- 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. 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: 0be68712482e459c80e8aab6f4080c0f393247558ba8370044aa076472d77213; retrieved 2026-09-16T08:24:59.723Z.