Cirrus SR22 accident near Martinsville, Virginia, October 12, 2023
On October 12, 2023 at about 2:47 am local time, a 2023 Cirrus SR22, registered N253BC, was substantially damaged in an accident during initial climb near Martinsville, Virginia (Blue Ridge airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 12, 2023 · about 2:47 am local time
- Place
- Martinsville, Virginia · Blue Ridge · map
- Type
- Accident
- Injuries
- No one was hurt; 4 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cirrus SR22 T, built 2023 · all SR22s on the register
- Registration
- N253BC · registry record · serial 9143
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
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
- Flight instrument malf/fail during initial climb
- Collision during takeoff/land during initial climb defining event
The NTSB's findings
- Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Climb rate › Not attained/maintained
- Personnel issues › Task performance › Planning/preparation › Weight/balance calculations › Pilot
- Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 758 hours in all; 260 in this make and model; 55 in the last 90 days; 18 in the last 30 days; 716 as pilot in command
- Last flight review: May 18, 2023
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
Passenger
- Seat: rgt
- Injury: no injuries
Passenger
- Seat: rear
- Injury: no injuries
Passenger
- Seat: rear
- Injury: no injuries
The aircraft
- Airframe total time: 121 hours
- Last inspection: 100-hour inspection, October 11, 2023; 5 hours since
- Maximum gross weight: 3,600 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental Motors TSIO-550-K (piston); 105 hours total
The flight
- Destination: GOK Guthrie OK
- Flight plan: none
- Runway 31, 5,002 ft by 100 ft
Weather at the time
- Light: night
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 54°F (12°C), dew point 52°F (11°C)
- Altimeter: 29.96 inHg
- Observation at 10:35 pm from MTV
Weather report (METAR): KMTV 120235Z AUTO 00000KT 10SM CLR 12/11 A2996 RMK AO2 T01200105
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
12 documents, released by the NTSB on February 11, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 13 pages | View Download |
| 2 | Memorandum of Record - Pilot Interview (Multiple) | PDF, 8 pages | View Download |
| 3 | Investigation Photographs | PDF, 8 pages | View Download |
| 4 | Cockpit Displays - Specialist's Factual Report | PDF, 12 pages | View Download |
| 5 | Cockpit Displays - Specialist's Factual Report - Attachment 1 | PDF, 1 page | View Download |
| 6 | Cockpit Displays - Specialist's Factual Report - Attachment 2 | data file | Download |
| 7 | Cockpit Displays - Specialist's Factual Report - Attachment 3 | data file | Download |
| 8 | Aircraft Systems - Specialist's Factual Report | PDF, 14 pages | View Download |
| 9 | Excerpts from FAA Pilot's Handbook of Aeronautical Knowledge (FAA-H-8083-25C) | PDF, 2 pages | View Download |
| 10 | Mtv Takeoff Minimums | PDF, 1 page | View Download |
| 11 | Statement of Party Representatives to NTSB Investigation | PDF, 1 page | View Download |
| 12 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 4 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N253BC the same tail number, which may have belonged to a different aircraft at the time
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
