FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24LA007 · Cirrus SR22 T

11 Oct 2023 · Martinsville, VA, United States

Cirrus SR22 T · Accident: collision during takeoff/landing during initial climb

From an unrecorded airport to Guthrie-Edmond Regional Airport (GOK)

Report a problem

Event

NTSB case
ERA24LA007
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
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
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 SR22 T

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
N253BC
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Guthrie-Edmond Regional Airport (GOK), Guthrie, OK
Aircraft age
Built the same year (2023)
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
Initial climb
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
Collision during takeoff/landing
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
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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 had just refueled the airplane and planned to fly a night, visual flight rules, cross-country flight. The pilot used 50% flaps for the normal takeoff; after he established a positive rate of climb, the pilot retracted the flaps. Shortly after retracting the flaps, the primary flight display (PFD) reportedly “blinked off” momentarily and then reappeared with a “Taxiway! Taxiway!” alert, and the multifunction display (MFD) screen was orange, which confused the pilot. He then looked up, saw a large pine tree ahead, and attempted to avoid the tree; however, the airplane impacted trees, resulting in substantial damage to the airplane. After the tree impact, the pilot was able to maintain control of the airplane, return to the departure airport, and land uneventfully. Examination of the PFD and MFD databases revealed no anomalies that would have resulted in a PFD malfunction. Postaccident examination of the airplane and avionics revealed no malfunctions or failures that would have precluded normal operation. Review of onboard data revealed that after retracting the flaps from 50%, the airplane began to descend despite no change in engine power. The descent continued until the recorded airspeed decreased to 0 kts and became unreliable, likely as a result of tree impact damage to the pitot tube. The data further revealed that there was no recorded electrical power loss or loss of engine power throughout the flight. Recorded data revealed that the airplane was over its maximum gross weight at the time of the accident, which likely led to a longer takeoff distance and reduced climb performance. The airplane’s avionics display was capable of providing terrain warnings and alerts. During the accident flight, the airplane was operated within the performance envelope that would trigger a “Too Low, Terrain” caution message, and the terrain would be illuminated amber. The system was also capable of alerting the pilot when the system detected that the airplane was taking off or landing on a non-runway. These alerts will provide a voice alert of “Taxiway” and a visual annunciation of “TWY TAKEOFF” or “TWY LANDING,” respectively. It is likely that when the pilot allowed the airplane to descend, the MFD terrain turned amber in color to alert the pilot of being too low, and the system calculated that the pilot was landing on a non-runway, which then triggered the “TWY LANDING” visual and aural alert. Although the terrain alerting function appears to have operated as designed, the pilot’s lack of understanding of the alerts likely distracted him and led him to interpret their display as an avionics failure.

Probable cause

The pilot’s failure to maintain a positive climb rate after takeoff while distracted by primary flight display anomaly and terrain alerts. Contributing to the accident was the pilot’s decision to take off with the airplane over its maximum gross weight, which reduced its initial climb performance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24LA007
Event ID
20231012193235
Case number
ERA24LA007
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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2023-10-12.
  • API snapshot SHA-256: 1fdeb464055c8acca893f915e088a4c1a5b547a01be11b32493a24c7b164021d; retrieved 2026-09-16T18:12:58.249Z.