WPR19LA117 · Nanchang CJ 6 A
Nanchang CJ 6 A · Accident: runway excursion during landing
From Auburn Municipal Airport (AUN) to Nevada County Airport (GOO)
Event
- NTSB case
- WPR19LA117
- 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
- Unknown
- 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
Nanchang CJ 6 A
- Aircraft type
- Nanchang CJ-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
- N621JM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Auburn Municipal Airport (AUN), Auburn, CATo Nevada County Airport (GOO), Grass Valley, CA
- Aircraft age
- About 30 years (built 1989)
- 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
- Defining eventThe 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
- Runway excursion
- 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
- Aircraft › Aircraft systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During the landing roll, the pilot applied left rudder and lightly depressed the brake handle to exit the runway. About 30° into the left turn, the brakes failed, and the airplane exited the asphalt taxiway surface. Due to obstructions ahead and the downsloping terrain, the pilot applied right rudder and engine power to realign the airplane with the runway. Shortly thereafter, the airplane overran the departure end of the runway and traveled downslope while airborne. The airplane then touched down and impacted a dirt berm before it collided with a fence, nosed over, and came to rest inverted, sustaining substantial damage to the fuselage and both wings. Examination of the airplane revealed that the brake control cable was fractured near the cable thimble and was separated from the brake control handle. The fracture surfaces of the separated cable were consistent with a fatigue fracture. Six of the seven strands of wires exhibited relatively flat fracture surfaces normally oriented to the wire axis, consistent with a progressive fracture mechanism, such as a fatigue fracture. Only one strand and a few of the remaining individual wires showed evidence of minor elongation at the fracture location. It is likely that the cable completely failed during the landing roll when the pilot depressed the brake handle.
Probable cause
A loss of brake control due to fatigue fracture of the brake control cable, which resulted in the separation of the cable from the brake handle.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19LA117
- Event ID
- 20190420X95256
- Case number
- WPR19LA117
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 445bafdd82dbe95404b82d0f6856d0968f03bb7acc272253c1f4b25b1a13cacf; retrieved 2026-09-16T08:47:31.650Z.