Cirrus Design CORP SR22 accident near Ashland, Ohio, September 7, 2026
On September 7, 2026 at about 4:55 pm local time, a 2006 Cirrus Design CORP SR22, registered N521LM, was substantially damaged in an accident during landing (landing roll) near Ashland, Ohio (Ashland County airport). It was a personal 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).
Preview. This page is not yet listed for search engines.
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 October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 7, 2026 · about 4:55 pm local time
- Place
- Ashland, Ohio · Ashland County · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cirrus Design CORP SR22 NO SERIES, built 2006
- Registration
- N521LM · registry record · serial 2243
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On September 7, 2026, about 1255 eastern daylight time, a Cirrus Design Corp SR22, N521LM, was substantially damaged when it was involved in an accident near Ashland, Ohio. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot stated that during landing at Ashland County Airport (3G4), Ashland, Ohio, the airplane’s right brake did not operate. The left brake operated normally, and the airplane began to veer to the left. He kept the airplane on the centerline of the runway utilizing rudder controls; however, when the airplane slowed down it departed the left side of the runway and contacted two runway lights, which resulted in substantial damage to the wing and firewall. Examination of the airplane by an FAA inspector revealed that the right brake disc was circumferentially fractured. The brake disc 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
- Runway excursion during landing (landing roll)
- Sys/Comp malf/fail (non-power) during landing (landing roll)
- Loss of control on ground during landing (landing roll) defining event
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The aircraft
- Airframe total time: 1,962 hours
- Last inspection: annual inspection, March 5, 2026
- Maximum gross weight: 3,400 lb
- Seats: 4
- Landing gear: fixed
The flight
- Departed from: OXB Ocean City MD at 3:00 pm
- Flight plan: IFR
- Runway 01, 3,501 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 060° at 7 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 75°F (24°C), dew point 55°F (13°C)
- Altimeter: 30.20 inHg
- Observation at 12:52 pm from MFD, 13 miles away
Weather report (METAR): METAR KMFD 071652Z 06007KT 10SM CLR 24/13 A3020 RMK AO2 SLP220 T02390128 $
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flig | 1 |
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA26LA333.