DFW07CA015 · Maule M5
Maule M5 · Accident: loss of control on ground/water during landing
From 3R5 · New Braunfels, TX to New Braunfels, TX
Event
- NTSB case
- DFW07CA015
- 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 M5
- Aircraft type
- Maule M5
- 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
- N32CX
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 3R5 · New Braunfels, TXTo New Braunfels, TX
- 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 · landing roll
- First occurrenceThe 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/water
- 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
- Landing gear, main gear attachment › Corroded
- Landing gear, main gear attachment › Deteriorated
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot was returning to the airport in the tail-wheeled airplane. He reported that he executed a normal approach to runway 17 for a full- stop landing. He stated that the wind at the time of the landing was reported as 250 degrees at 8 knots. During the landing roll, the airplane drifted to the left side of the runway. stated that he made a "slight correction with right rudder," but the airplane's right wing "continued down and the aircraft [began] to turn hard right." He attempted to regain directional control by adding power, but the right main landing gear collapsed, and the right wing and the propeller contacted the ground. The airplane ground looped which, resulted in structural damage to the right wing. Examination of the landing gear by an aircraft mechanic revealed that the right landing gear strut attachment point was corroded and cracked.
Probable cause
The failure of the right main landing gear attachment during the landing roll, which resulted in a ground loop. A contributing factor was a crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW07CA015
- Event ID
- 20061228X01852
- Case number
- DFW07CA015
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 9504f299efd9e884c153c6cdaf9a376203445fd9fd93dad70dd832cedd16d9a9; retrieved 2026-09-22T04:17:25.567Z.