The U.S. aircraft register, updated daily
Accidents · NTSB DEN00LA158 · Final report

Maule MX-7-235 accident near Broomfield, Colorado, August 29, 2000

On August 29, 2000 at about 5:00 pm local time, a Maule MX-7-235, registered N111KD, was substantially damaged in an accident near Broomfield, Colorado (Jeffco Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

the pilot's failure to maintain directional control during landing roll. A contributing factor was the crosswind.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 29, 2000 · about 5:00 pm local time · cases in 2000
Place
Broomfield, Colorado · Jeffco Airport · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Maule MX-7-235 · all MX-7-235s on the register
Registration
N111KD · registry record · serial 10049C
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

During the landing roll on runway 29L, the left wing lifted, and the airplane ground looped to the right. The airplane departed the right side of the runway, and the left main gear collapsed. The recorded wind at the time of the accident was 350 degrees at 10 knots, or a 9 knot direct crosswind. The pilot stated that "more diligence on landing, quicker response to divergence of [the] aircraft" could have prevented the accident.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 2,109 hours in all; 1,012 in this make and model; 26 in the last 90 days; 19 in the last 30 days; 2,084 as pilot in command
  • Medical certificate: Class 3 (valid medical--no waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 1,204 hours
  • Last inspection: annual inspection, July 28, 2000; 23 hours since
  • Maximum gross weight: 2,500 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-540-W1A5D (piston); 0 hours total

The flight

  • Departed from: LXV Leadville CO at 3:20 pm
  • Destination: BJC CO
  • Flight plan: none
  • Runway 29L, 7,000 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 350° at 10 knots
  • Visibility: 20 statute miles
  • Sky: broken clouds at 20,000 ft; scat at 3,000 ft
  • Temperature: 163°F (73°C), dew point 135°F (57°C)
  • Altimeter: 30.00 inHg
  • Observation at 4:54 pm from BJC

Injuries

FatalSeriousMinorNone
Crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/DEN00LA158.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.