# Incident 19990603032669I: Sngyng MIG17UTI, Charlottesville, VA, June 3, 1999

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 3, 1999, 10:00 local time
- Place: Charlottesville, VA
- Airport: Charlottesville-Albemarle
- Damage: Minor damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 38.1396° N, 78.4523° W: Placed by OpenAirDocs at CHARLOTTESVILLE-ALBEMARLE (CHO), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.1396&lon=-78.4523&mi=10
- Aircraft: N17HQ, registered now (https://openairdocs.org/aircraft/N17HQ) (OpenAirDocs)
- Registry model: Poland Mig17 LIM 6 (registry code 05624S2, https://openairdocs.org/model/poland-mig17-lim-6) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: SNGYNG MIG17UTI
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 20,000 total, 150 in this make and model
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990603032669I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) ON JUNE 3, 1999, THE PILOT OF N17HQ, A MIG-17, SENSED THE BRAKES STARTING TO FADE DURING LANDING. HE ELECTED TO VEER OFF THE RUNWAY ONTO THE GRASS, INSTEAD OF RUNNING OFF THE END OF THE RUNWAY.  THE AIRCRAFT STOPPED WITH NO DAMAGE TO THE AIRCRAFT AS A RESULT OF THE LANDING.  THE INCIDENT WAS CAUSED BY IMPROPERLY SEATED BRAKES AND THE PILOT'S FAILURE TO DO A PROPER BRAKE CHECK.  DURING A SUBSEQUENT INSPECTION OF THE AIRCRAFT, A HOLE, A BURNED AREA 18 INCHES LONG AND 4 INCHES WIDE IN THE SKIN AND SUPPORTING STRUCTURE, WAS FOUND UNDER THE TAIL OF THE AIRCRAFT.  THIS DAMAGE IS CAUSED BY A FIRE IN FLIGHT AND HAD NO RELATION TO THE BRAKING PROBLEM.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.