FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN02LA020 · Maule M-5-235C

13 Jan 2002 · Grand Junction, CO, United States

Maule M-5-235C · Accident: airframe, component or system failure during landing

From Grand Junction Regional Airport (GJT) to an unrecorded destination

Report a problem

Event

NTSB case
DEN02LA020
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 M-5-235C

Aircraft type
Maule M-5
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
N382X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Grand Junction Regional Airport (GJT), Grand Junction, COTo not recorded
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
Airframe, component or system failure
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, steering system › Failure
  • Landing gear, tailwheel › Disconnected

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 said that during a touch and go landing, he heard a "bang." The left rudder pedal went to the floor, and the airplane ground looped to the right. The left wing was bent up for the outboard 12 feet of the wing. Postaccident examination of the airplane's left tail wheel steering cable revealed that a swaged attachment had separated.

Probable cause

the failure of the tail wheel left steering cable. A contributing factor was the pilot's loss of aircraft control (not possible) and the subsequent inadvertent ground loop.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN02LA020
Event ID
20020123X00098
Case number
DEN02LA020
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: 2b3c333b5569fd5cd7a1c7e9365b05d7d22da9b27e3957c0f538ca59c00ab9cc; retrieved 2026-09-22T11:11:59.128Z.