The U.S. aircraft register, updated daily
Accidents · NTSB ERA25LA353 · Preliminary: the investigation is not finished

Cessna 525C accident near Mayfield, Kentucky, September 18, 2025

On September 18, 2025 at about 9:40 pm local time, a 2013 Cessna 525C, registered N577RT, was substantially damaged in an accident during landing (landing roll) near Mayfield, Kentucky (Mayfield Graves County). It was a positioning flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 18, 2025 · about 9:40 pm local time · cases in 2025
Place
Mayfield, Kentucky · Mayfield Graves County · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 525C, built 2013 · all 525Cs on the register
Registration
N577RT · registry record · serial 525C0133
Damage
Substantial damage
Flight
Positioning flight · general aviation rules (Part 91)

The NTSB's narrative preliminary · quoted from the NTSB record

On September 18, 2025, about 1640 central daylight time, a Cessna 525C, N577RT, was substantially damaged when it was involved in an accident near Mayfield, Kentucky. The airline transport pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 repositioning flight. According to the pilot, the airplane had just completed maintenance at the St. Louis Regional Airport (ALN), St. Louis, Illinois, and the purpose of the flight was to return it to Mayfield Graves County Airport (M25), Mayfield, Kentucky, where it was based. The pilot reported that the preflight inspection, taxi, takeoff, and flight to M25 were uneventful, with no anomalies observed. During the initial descent to M25, the pilot reported that he deployed the speed brakes to begin slowing the airplane and to assist with the descent. The pilot set up for a straight-in, visual approach for runway 19, a 5,002-ft-long, 100-ft-wide, asphalt runway. While on approach, the speed brakes remained deployed and when the airplane's speed was below 200 knots indicated airspeed (IAS), the pilot extended the landing gear. When the airplane's speed was below 160 knots IAS, the pilot stowed the speed brakes and configured the airplane for landing. The pilot further stated that while he configured the airplane for landing “later than intended,” the airplane was still fully configured and stabilized for a visual approach to land at M25. The pilot reported that the airplane touched down on the runway centerline and that he deployed the ground spoilers and pressed firmly on the brakes; however, he observed no braking action as the airplane continued to roll down the runway. The pilot applied greater force to the brakes; however, the airplane began to veer to the right, and there was still no observed slowing of the airplane. The pilot determined there was insufficient runway for a go-around and decided to continue to roll down the runway with the engines at idle, continuing to press firmly on the brakes, correcting the airplane back toward the runway centerline, and applying downward force to the yoke. The airplane rolled off the end of the runway, went through the airport’s perimeter fence, crossed a road, and impacted a house. Initial postaccident examination of the airplane by a Federal Aviation Administration inspector revealed the airplane sustained substantial damage to the left wing and to the fuselage. The airplane was retained for further examination.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Runway excursion during landing (landing roll) defining event

The aircraft

  • Airframe total time: 1,810.5 hours
  • Last inspection: continuous airworthiness programme, September 18, 2025
  • Maximum gross weight: 17,230 lb
  • Seats: 10
  • Landing gear: retractable
  • Operator: Stonecrest Capital LLC

The flight

  • Departed from: ALN Alton IL at 8:03 pm
  • Flight plan: IFR
  • Runway 19, 5,002 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 93°F (34°C), dew point 55°F (13°C)
  • Altimeter: 29.98 inHg
  • Observation at 3:35 pm from M25, 12 miles away

Weather report (METAR): METAR KM25 181935Z AUTO VRB03KT 10SM CLR 34/13 A2998 RMK AO2 T03390125=

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA25LA353.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.