GAA17CA168 · Maule MX7 180A
Maule MX7 180A · Accident: nose over/nose down during landing
From Sacramento International Airport (SMF) to Live Oak, CA
Event
- NTSB case
- GAA17CA168
- 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
- N600XX
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sacramento International Airport (SMF), Sacramento, CATo Live Oak, CA
- Aircraft age
- About 22 years (built 1995)
- 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 · landing roll
- 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
- Nose over/nose down
- 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
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the tailwheel-equipped airplane reported that, while on base for his private grass airstrip, he noticed he was high, so he added flaps to increase his descent. He added that, on final, the airspeed was a little fast and during the landing, he flared the airplane "a little high." After touchdown, the pilot applied the brakes, but the airplane did not respond, so he applied "a little more brake"; subsequently, the airplane nosed over and came to rest inverted.
The airplane sustained substantial damage to both wings and the empennage.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
The pilot reported as a safety recommendation that he should have performed a go-around instead of attempting to "salvage the landing."
Probable cause
The pilot’s failure to maintain a stabilized approach and his subsequent incorrect brake application during the landing roll, which resulted in a nose-over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA168
- Event ID
- 20170302X33223
- Case number
- GAA17CA168
- 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: 3b6d2821f3e9aae08e4feae081810e6a5417927f2ab781b4460aefb90db70779; retrieved 2026-09-16T05:03:52.722Z.