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

Maule MX7-180A accident near Elko, Nevada, June 30, 2013

On June 30, 2013 at about 6:45 pm local time, a Maule MX7-180A, registered N5839R, was substantially damaged in an accident during landing (landing roll) near Elko, Nevada (Elko Regional airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A flat main landing gear tire during the landing roll for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.

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

What the record shows

Date
June 30, 2013 · about 6:45 pm local time
Place
Elko, Nevada · Elko Regional · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Maule MX7-180A · all MX7-180As on the register
Registration
N5839R · registry record · serial 20042C
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported that during landing, the airplane's left main landing gear tire went flat, which resulted in the left wingtip contacting the ground and substantially damaging the left aileron. The pilot reported that the tire was good during his preflight inspection. Postaccident examination of the tire revealed no evidence of a failure to identify the reason why the tire went flat.

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

What happened, in order

  1. Sys/Comp malf/fail (non-power) during landing (landing roll) defining event
  2. Dragged wing/rotor/float/other during landing (landing roll)
  3. Runway excursion during landing (landing roll)

The NTSB's findings

  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • Aircraft › Aircraft systems › Landing gear system › Tube › Not specified

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land; instrument: airplane; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 1,895 hours in all; 34 in this make and model
  • Last flight review: June 25, 2012
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 478 hours
  • Last inspection: annual inspection, April 13, 2013
  • Maximum gross weight: 2,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360-C4F (piston); 0 hours total

The flight

  • Departed from: MYL Mccall ID at 3:30 pm
  • Destination: EKO Elko NV
  • Flight plan: none
  • Runway 05, 7,211 ft by 150 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 97°F (36°C), dew point 41°F (5°C)
  • Altimeter: 30.11 inHg
  • Observation at 6:56 pm from EKO

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.