# Incident 20180614025139I: Cessna 340, Lousville, KY, June 14, 2018

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 14, 2018, 12:15 local time
- Place: Lousville, KY
- Damage: No damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Aircraft: N456JM, registered now (https://openairdocs.org/aircraft/N456JM) (OpenAirDocs)
- Registry model: Cessna 340 (registry code 2076404, https://openairdocs.org/model/cessna-340) (OpenAirDocs)
- Registry engine: Continental TSIO-520 series (registry code 17040, https://openairdocs.org/engine/continental-tsio-520-series) (OpenAirDocs)
- Reported make and model: CESSNA 340
- Reported engine: CONT MOTOR TSIO-520 SER
- People aboard: 3
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20180614025139I

## Narrative

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

THE PILOT STATED THAT THE PREVIOUS FLIGHT WAS A SHORT FLIGHT TO LEBANON SPRINGFIELD AIRPORT (6I2), TO FILL UP WITH GAS.  DURING GROUND OPS THERE, THERE WAS ONE INSTANCE WHERE THE LEFT BRAKE "FADED" SLIGHTLY, BUT RECOVERED WHEN HE "PUMPED" THE PEDAL ONCE.  HE REPORTED NORMAL BRAKING AFTER THAT AND DID NOT SUSPECT TOTAL BRAKE FAILURE AT THAT TIME.

DURING THE LANDING ROLL AT KLOU ON RWY 06, AFTER TOUCHDOWN, WHEN THE PILOT BEGAN BRAKING, HE DISCOVERED THAT THE LEFT BRAKE WAS INOPERATIVE WITH NO PEDAL BACK PRESSURE.  BRAKING ON THE LEFT SIDE DID NOT RECOVER EVEN BY "PUMPING" THE BRAKE. HE BEGAN HEAVY BRAKING USING ONLY THE RIGHT BRAKE AND MAINTAINING DIRECTIONAL CONTROL WITH LEFT RUDDER AND NOSE WHEEL STEERING.  TOWARD THE END OF THE AVAILABLE RUNWAY (3469 FT FROM DISPLACED THRESHOLD), THERE WAS INSUFFICIENT DIRECTIONAL CONTROL AVAILABLE TO REMAIN ON THE PAVEMENT AND THE PLANE BRIEFLY EXITED THE RIGHT SIDE OF THE RUNWAY.  HE WAS ABLE TO RECOVER BACK TO THE PAVED RUNWAY SURFACE, BUT STILL HAD A SLIGHT EXCESS OF SPEED ABOVE NORMAL TAXI SPEED.  HE ATTEMPTED THE RIGHT TURNOFF AT THE END OF THE RUNWAY ONTO TAXIWAY H.  DURING THIS TURN THE PLANE EXITED THE TAXIWAY ON THE LEFT (EAST) SIDE BRIEFLY.  HE WAS THEN ABLE TO REGAIN CONTROL AS THE SPEED HAD SLOWED TO NORMAL.  DURING THE EXCURSION FROM THE TAXIWAY, THE PLANE STRUCK A BLUE TAXIWAY LIGHT WITH THE LEFT WHEEL OR GEAR DOOR.

THE PILOT REPORTED THE EXCURSION TO GROUND CONTROL AND SUGGESTED THEY SEND SOMEONE TO CHECK THE TAXI LIGHT, SINCE HE COULD NOT TELL FOR SURE WHETHER HE HAD HIT THE LIGHT OR NOT.  HE WAS ABLE TO TAXI THE AIRCRAFT BACK TO THE EAST T HANGERS BY USING A VERY SLOW SPEED AND ONLY THE RIGHT BRAKE.

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.