# NTSB WPR14LA040: Mikoyan Gurevich MIG 21 UM, N20739, Reno, NV, November 1, 2013 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: November 1, 2013, 09:40 local (16:40 UTC) - Place: Reno, NV - Coordinates: 39.660278, -119.866668 - Nearby events: https://openairdocs.org/map.md?lat=39.6603&lon=-119.8667&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) - Highest injury: Serious injuries - Injuries: 1 serious - Status: Completed, report September 29, 2014 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 88374 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR14LA040 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/88374/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=88374 - Page: https://openairdocs.org/ntsb/WPR14LA040 ## Probable cause The loss of brake control due to the fracture of the front brake pawl engagement spring, which resulted in a runway overrun. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Landing gear system: master cylinder/brake valve](https://openairdocs.org/ntsb-findings/01023243): Aircraft › Aircraft systems · Failure (probable cause); cases with it: [Mikoyan Gurevich MIG 21 UM, 1 case](https://openairdocs.org/ntsb-findings/01023243/cases.md?model=056037S), [All aircraft, 21 cases](https://openairdocs.org/ntsb-findings/01023243/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Mikoyan Gurevich MIG 21 UM, 1 case](https://openairdocs.org/ntsb-events/300/sequence.md?model=056037S), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis 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. ## Factual narrative On November 1, 2013, about 0940 Pacific daylight time, a Mikoyan Gurevich Mig 21 UM, N20739, was substantially damaged during a runway overrun at the Reno-Stead Airport (RTS), Reno, Nevada. The airplane was registered to Migs of Delaware LLC., Wilmington, Delaware, and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91. The commercial pilot, sole occupant of the airplane, sustained serious injuries. Visual meteorological conditions prevailed and no flight plan was filed for the local personal flight that originated from RTS at 0915.In a written statement to the National Transportation Safety Board (NTSB) investigator-in-charge (IIC), the pilot reported that following a normal landing on runway 14 (9,000-foot long and 150-foot wide asphalt runway), he initially applied braking. The pilot released the wheel brakes as the airplane decelerated to allow for cooling. As the airplane crossed the 4,000 foot remaining sign, he reapplied brakes with no braking action noted. He applied the emergency brake, however, did not immediately feel a response. The pilot shut down the engine and retracted the landing gear as the airplane approached the departure end of the runway. Subsequently, the airplane overran the departure end of the runway, traveled down an embankment, and came to rest upright. The pilot added that at the time the brakes failed, the airplane was too slow for an effective drag chute deployment. Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed that the fuselage and wings were structurally damaged. The inspector stated that the emergency brake handle and drag chute both remained in the stowed positions. The airplane was recovered to a secure location for further examination. The inspector reported that the accident airplane brake system features control levers for the front seat (student or solo position) and rear seat (instructor position) that are stacked on a pivot point with only the rear seat brake levers physically actuating the pneumatic brake valve. The front seat lever engages the rear seat lever with a pawl. Spring tension holds the pawl in the engaged position, however, can be disengaged if the rear seat pilot elects to override the front seat pilot. The inspector reported that he coordinated with the pilot's mechanic to look at the airplane further; however, the mechanic disassembled the brake system prior to his arrival. The inspector stated that examination of the accident airplane revealed that a spring that holds the pawl in place and engaged was fractured and separated, which allowed the pawl to become disengaged. The disengaged pawl resulted in the deactivation of front brakes. Review of the Pilot's Flight Operating Instructions for the airplane stated, in part, "….if upon depressing the braking lever, the aircraft fails to get braked or one of the wheels gets sharply braked, proceed as follows: (a) release the braking lever, immediately deploy thedrag chute and retract the flaps." The instructions further state "…after deployment of the drag chute, shut down the engine and use the emergency braking system." ## Aircraft - Registration: [N20739](https://openairdocs.org/deregistered/N20739-2016-01-22), registration cancelled 2016-01-22, S/N 3171 (OpenAirDocs) - Reported make and model: MIKOYAN GUREVICH MIG 21 UM (NO SERIES) - Registry model: [Mikoyan Gurevich MIG 21 UM](https://openairdocs.org/model/mikoyan-gurevich-mig-21-um) (registry code 056037S) (OpenAirDocs) - Registry engine: [Amateur-built UNKNOWN ENG](https://openairdocs.org/engine/amateur-built-unknown-eng) (registry code 99999) (OpenAirDocs) - Category: Airplane - Serial number: 3171 - Airframe hours: 1827.2 - Engines: Tomanski R22F25300 13613 lbs thrust turbo jet - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Joesph Gano - Registered owner: Migs Of Delaware LLC - Airworthiness certificate: Special, Experimental (Special) - Last inspection: AAIP, April 7, 2013, 6.1 hours before - Departed: RTS, Reno, NV - Destination: RTS, Reno, NV - Airport: RTS, Reno/Stead, runway 14, 9,000 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 71; injuries: serious; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, without waivers/limitations; last flight review May 5, 2013; seat: front; restraint: 4-point; flight hours: 2,800 total, 400 in this make and model, 2,800 as pilot in command, 28 in the last 90 days, 1 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 41 °F, dew point 30 °F - Altimeter: 30.31 inHg - Observed at: KRNO, 11 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20131101022729A](https://openairdocs.org/incident/20131101022729A), Nov 1, 2013: Mikoyan Gurevich MIG 21 UM, Reno, NV, Substantial damage. During rollout after landing on runway 14, the brakes failed to actuate on the second application. The aircraft proceeded 1000 feet off the end of the runway,… ## Docket (5 files) The files NTSB released with the investigation on May 20, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=88374. 1.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 753 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40412456&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Pilot Statement (item 2, .PDF, 135 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40412457&FileExtension=.PDF&FileName=Pilot%20Statement-Redacted.PDF - FAA Inspector’s Statement (item 3, .PDF, 13 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40412458&FileExtension=.PDF&FileName=FAA%20Inspector%E2%80%99s%20Statement-Master.PDF - Pilot's Flight Operating Handbook Instructions (item 4, .PDF, 290 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40412459&FileExtension=.PDF&FileName=Pilot%27s%20Flight%20Operating%20Handbook%20Instructions-Redacted.PDF - FAA Correspondence with Mechanic (item 5, .PDF, 35 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40412460&FileExtension=.PDF&FileName=FAA%20Correspondence%20with%20Mechanic-Redacted.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.