Mikoyan Gurevich MIG 21 UM accident near Reno, Nevada, November 1, 2013
On November 1, 2013 at about 4:40 pm local time, a Mikoyan Gurevich MIG 21 UM, registered N20739, was substantially damaged in an accident during landing (landing roll) near Reno, Nevada (Reno/Stead airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The loss of brake control due to the fracture of the front brake pawl engagement spring, which resulted in a runway overrun.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 1, 2013 · about 4:40 pm local time
- Place
- Reno, Nevada · Reno/Stead · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Mikoyan Gurevich MIG 21 UM NO SERIES · all MIG 21 UMs on the register
- Registration
- N20739 · no longer on the register · serial 3171
- 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, following a normal landing, he applied the brakes and that he then released the brakes as the airplane decelerated to allow for brake cooling. As the airplane passed the 4,000-foot-remaining sign, the pilot reapplied the brakes but noted no braking action. The airplane subsequently overran the departure end of the runway. Postaccident examination of the airplane revealed that the spring that allows the front brakes to engage a brake pawl was fractured, which resulted in the deactivation of the front brake pedals and the subsequent runway overrun.
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
- Runway excursion during landing (landing roll) defining event
The NTSB's findings
- cause Aircraft › Aircraft systems › Landing gear system › Master cylinder/brake valve › Failure
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 2,800 hours in all; 400 in this make and model; 28 in the last 90 days; 1 in the last 30 days; 2,800 as pilot in command
- Last flight review: May 5, 2013
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: frt
- Injury: serious injuries
The aircraft
- Airframe total time: 1,827.2 hours
- Last inspection: approved inspection programme, April 7, 2013; 6.1 hours since
- Maximum gross weight: 20,994 lb
- Landing gear: retractable
- Engine: Tomanski R22F25300 (turbojet); 0 hours total
The flight
- Departed from: RTS Reno NV at 4:15 pm
- Destination: RTS Reno NV
- Flight plan: none
- Runway 14, 9,000 ft by 150 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 41°F (5°C), dew point 30°F (-1°C)
- Altimeter: 30.31 inHg
- Observation at 4:55 pm from KRNO, 11 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
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.