CHI00LA218 · Yakovlev YAK 52
Yakovlev YAK 52 · Accident: overrun during landing
From Kay Air Airport (20II) to an unrecorded destination
Event
- NTSB case
- CHI00LA218
- 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
- 0
- 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
Yakovlev YAK 52
- Aircraft type
- Yakovlev YAK-52
- 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
- N6223X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Kay Air Airport (20II)To not recorded
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Overrun
- 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
- Pilot in command › Brakes(normal), not available
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said that upon landing, "... the brakes seemed to work at first but began to loose effectiveness half way into the roll-out." The pilot said that he then aborted the landing and "...attempted to troubleshoot the problem with the aircraft checklist but the loss of braking effectiveness is not a covered item." The pilot said that he, "...evaluated going to another airport but decided against an asphalt runway. I decided to land in the taller weeds that are parallel to runway 09 at 20II.... During the landing roll the aircraft was slowed by the action of the weeds but the pneumatic braking action was weak and insufficient." The aircraft impacted the trees at the end of the landing run. A postaccident examination of the aircraft revealed that the brake handle was not properly adjusted in the front cockpit and there was not enough travel in the handle to properly engage the brakes. No other anomalies were found that could be associated with a preexisting condition. An airport located about 8 nautical miles and 353 degrees magnetic from the accident airport has three runways all exceeding 7,600 feet long with the longest being 11,200 feet long.
Probable cause
the brakes not available to the pilot. Factors were the improperly serviced brake system, the improper adjustment of the brakes by maintenance personnel, the trees, and the pilot's decision not to use the available alternate airport.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI00LA218
- Event ID
- 20001212X21407
- Case number
- CHI00LA218
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2000-07-24.
- API snapshot SHA-256: 1dd6d96964ddfa039976826fad01f3a904a6838d2d9e6ed9d6d1c33c78d91841; retrieved 2026-09-22T12:39:39.697Z.