FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25LA068 · Cirrus Design Corp SR22T

3 Jan 2025 · Lubbock, TX, United States Narrative disagrees

Cirrus Design Corp SR22T · Accident: loss of control on ground during takeoff

From an unrecorded airport to Addison Airport (ADS)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN25LA068
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 SR22T

Aircraft type
Cirrus SR22
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
N725DC
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Addison Airport (ADS), Addison, TX
Aircraft age
About 3 years (built 2022)
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
Takeoff
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
Loss of control on ground
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability

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

NTSB narrative

The pilot reported that during the takeoff roll, at 50 knots, he felt a quick shake/wiggle and the airplane turned hard left due to a left main landing gear tire failure. The pilot stated that he reduced engine power and applied right rudder pedal control input as much as possible, but the airplane continued to pull left. The airplane exited the left side of the runway and impacted trees. The airplane came to rest on its left side and a postcrash fire ensued that destroyed the airplane. The postcrash fire precluded any examination to determine the cause of the accident.

Probable cause

The loss of directional control during the takeoff roll for undermined reasons that resulted in an impact with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN25LA068
Event ID
20250103199504
Case number
CEN25LA068
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: 74dc9e1fe9348775d56817e1759339917169afaa718ca345b12c2e1b332b4c50; retrieved 2026-09-16T19:34:46.259Z.