FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25LA339 · Cirrus Design Corp SR20

24 Aug 2025 · Charleston, WV, United States

Marshall University Cirrus Design Corp SR20 · Accident: system/component malfunction/failure (non-power) during landing

From Mid Ohio Valley Regional Airport (PKB) to an unrecorded destination

Report a problem

Event

NTSB case
ERA25LA339
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
Unknown
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cirrus Design Corp SR20

Aircraft type
Cirrus SR20
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N241MU
Onboard fatalities
Unknown
Route
From Mid Ohio Valley Regional Airport (PKB), Parkersburg, WVTo not recorded
Aircraft age
About 1 year (built 2024)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
System/component malfunction/failure (non-power)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft systems

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The flight instructor reported that he and the student pilot were on the return leg of a cross-country flight. As the student pilot was landing the airplane at their home airport, the touchdown was normal, but the airplane immediately veered left. The flight instructor took control of the airplane and attempted to correct, but the airplane continued off the left side of the runway. The left wing struck a runway sign, resulting substantial damage to the left wing, and the airplane came to rest upright in a grass area off the left side of the runway. Examination of the wreckage by a mechanic and a Federal Aviation Administration inspector revealed a flat spot and gashes on the left main landing gear tire, consistent with the tire being flat upon touchdown.

Probable cause

A flat left main landing gear tire, which resulted in a loss of directional control and runway excursion during landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA25LA339
Event ID
20250910200976
Case number
ERA25LA339
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 5e793359dd91a2cc0d21988201c1639764b9889492120caebaee256a171d8e5e; retrieved 2026-09-16T20:19:29.079Z.