# Incident 20181108022419I: Cessna 172N, Greensboro, NC, November 8, 2018

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 8, 2018, 15:41 local time
- Place: Greensboro, NC
- Airport: Piedmont Triad International
- Damage: Minor damage
- Phase of flight: Takeoff: Departure Roll
- Operating rules: General operating rules (Part 91)
- Location: 36.1013° N, 79.9411° W: Placed by OpenAirDocs at PIEDMONT TRIAD INTL (GSO), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.1013&lon=-79.9411&mi=10
- Aircraft: N5730J, registered now (https://openairdocs.org/aircraft/N5730J) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 440 total, 282 in this make and model, 14 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20181108022419I

## Narrative

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

A BRAKE TEST HAD BEEN DONE ON THE RAMP BEFORE TAXIING AND THAT THEY HAD COMPLETED THE RUN UP HOLDING SHORT OF RUNWAY 5L WITH NO PROBLEMS WITH THE BRAKES. ONCE THEY WERE CLEARED ON TO THE RUNWAY THEY TAXIED TO THE EDGE OF THE PAVEMENT TO PERFORM A SHORT FIELD TAKEOFF. WHEN HE APPLIED THE RIGHT BRAKE TO ALIGN THE AIRCRAFT WITH THE CENTERLINE, HE GOT NO RESPONSE. HE NOTIFIED HIS INSTRUCTOR WHO WAS SITTING IN THE LEFT SEAT. HE APPLIED HIS RIGHT BRAKE TO TURN THE AIRCRAFT AND ALSO GOT NO RESPONSE. AT THIS POINT THE PILOT TOOK THE POWER TO IDLE AND THEY WORKED TO STOP THE AIRCRAFT AND ATTEMPTED TO AVOID HITTING ANY LIGHTS. THEY DID END UP HITTING A RUNWAY END IDENTIFIER LIGHT. THEY INFORMED TOWER OF THEIR ISSUE AND THAT THEY NEEDED TO SHUT DOWN TO BE ABLE TO TURN THE AIRCRAFT AND GET IT BACK ON THE RUNWAY. THEY THEN PROCEEDED TO TAXI BACK TO THE RAMP VERY SLOWLY AS THEY DID NOT HAVE ANY RIGHT BRAKE. ONCE THEY GOT BACK ON THE RAMP THEY SHUT DOWN AND NOTICED A CHIP IN THE PROPELLER AND THAT IT WAS BENT. IT WAS ALSO NOTED THAT THE RIGHT MAIN TIRE WAS COVERED IN BRAKE FLUID.

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.