FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN20CA388 · Maule MX7 180A

7 Sept 2020 · Brazoria, TX, United States

Maule MX7 180A · Accident: nose over/nose down during landing

From Pearland Regional Airport (LVJ) to Pearland Regional Airport (LVJ)

Report a problem

Event

NTSB case
CEN20CA388
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
N897DC
Operator
Unknown
Onboard fatalities
Unknown
Route
From Pearland Regional Airport (LVJ), Houston, TXTo Pearland Regional Airport (LVJ), Houston, TX
Aircraft age
About 27 years (built 1993)
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 · aborted after touchdown
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

  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot reported that he was attempting an off-airport landing in a tailwheel-equipped airplane to a location that he had not previously landed. He stated that just prior to touchdown he realized it was not a suitable landing area and he initiated a go-around. During the go-around, the airplane touched down on soft ground and tall grass, which caused the airplane to sink into the ground and nose over. The right lift strut was substantially damaged. The pilot reported no preimpact mechanical anomalies with the airplane that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain airplane control during a go-around from unsuitable terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20CA388
Event ID
20200908X81421
Case number
CEN20CA388
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. 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: b0d0a27b9361d171055378b3c59a11d3f9640c759cf40eb2ee28742be644326b; retrieved 2026-09-16T13:00:42.214Z.