FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN93LA040 · Maule M-6-235

9 Apr 1993 · Englewood, CO, United States

Maule M-6-235 · Accident: loss of control on ground/water during landing

From Centennial Airport (APA) to Centennial Airport (APA)

Report a problem

Event

NTSB case
DEN93LA040
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
0
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-6-235

Aircraft type
Maule M-6
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
N56509
Operator
Meine, William F. · private individual
Onboard fatalities
Unknown
Route
From Centennial Airport (APA)To Centennial Airport (APA)
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

  • Pilot in command › Compensation for wind conditions, improper
  • Pilot in command › Directional control, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

PRIOR TO THE FIRST LANDING ON RUNWAY 17L, ATIS REPORTED THE WIND TO BE FROM 180 DEGREES AT SEVEN KNOTS. PRIOR TO HIS SECOND LANDING, THE CONTROL TOWER TOLD THE PILOT THE WIND WAS FROM 050 DEGREES AT SIX KNOTS. THEY REQUESTED THAT HIS THIRD LANDING BE MADE TO A FULL STOP. THE PILOT SAID THAT DURING THE THIRD LANDING ROLLOUT, THE RIGHT WING LIFTED AND HE CORRECTED WITH FULL RIGHT AILERON AND FULL LEFT RUDDER WITH BRAKE, BUT COULD NOT MAINTAIN DIRECTIONAL CONTROL. THE LEFT WING CONTACTED THE RUNWAY AND THE LEFT MAIN LANDING GEAR COLLAPSED. THE PILOT ESTIMATED THE WINDS WERE THEN FROM THE SOUTHWEST AT 15 KNOTS. THE OFFICIAL WIND RECORDED ONE MINUTE AFTER THE ACCIDENT WAS 220 DEGREES AT 15 KNOTS.

Probable cause

THE PILOT'S IMPROPER COMPENSATION FOR WIND CONDITIONS AND HIS FAILURE TO MAINTAIN DIRECTIONAL CONTROL. FACTORS WERE: A CROSSWIND AND TAILWIND COMPONENT.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN93LA040
Event ID
20001211X12119
Case number
DEN93LA040
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. 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: e5d1a054e608355af4c8dd5f963dece75a1a6b58309023044743d65b165dce25; retrieved 2026-09-23T02:12:25.321Z.