# NTSB ERA24LA191: Socata TBM 850, N228CH, Raleigh, NC, April 24, 2024

- Type: NTSB accident investigation
- Classification: Accident · Serious injuries · Class 3 · Limited · Final report
- Date: April 24, 2024, 10:10 local (14:10 UTC)
- Place: Raleigh, NC
- Coordinates: 35.870384, -78.778245 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=35.8704&lon=-78.7782&mi=10
- Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping)
- Defining event: [Initial climb: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241)
- Highest injury: Serious injuries
- Injuries: 1 serious, 1 minor
- Status: Completed, report May 13, 2026
- Report: Approved by Office Director
- Investigation class: Class 3
- NTSB office: Eastern Region Aviation
- Parties: BEA France, Daher, FAA/FSDO
- NTSB case key (mKey): 194143
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA24LA191
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/194143/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=194143
- Page: https://openairdocs.org/ntsb/ERA24LA191

## Probable cause

The pilot’s decision to continue an unstabilized approach, which resulted in a bounced landing, and his failure to maintain proper airspeed and climb attitude after aborting the landing, which led to the airplane exceeding its critical angle of attack and resulting in an aerodynamic stall.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Socata TBM 700, 6 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=8682000), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Socata TBM 700, 21 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=8682000), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Socata TBM 700, 4 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=8682000), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md)
- [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Socata TBM 700, 9 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=8682000), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md)
- [Performance/control parameters: angle of attack](https://openairdocs.org/ntsb-findings/01062042): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Socata TBM 700, 3 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md?model=8682000), [All aircraft, 990 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Socata TBM 700, 5 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=8682000), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md)
- [Landing-aborted after touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Socata TBM 700, 5 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=8682000), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md)
- [Initial climb: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241) (defining event); cases with it: [Socata TBM 700, 6 cases](https://openairdocs.org/ntsb-events/241/sequence.md?model=8682000), [All aircraft, 1,529 cases](https://openairdocs.org/ntsb-events/241/sequence.md)

## Analysis

The pilot executed an approach that, based on the passenger’s description, was not stabilized, and the airplane touched down twice during landing. The propeller blades made contact with the runway, and the pilot decided to abort the landing because he did not think he could stop the airplane on the runway. During the subsequent takeoff and initial climb, the pilot made a tight left turn about 100 ft above ground level to avoid traffic on an intersecting runway, and the airplane entered an aerodynamic stall and impacted the ground. Postaccident examination of the airplane revealed no preimpact malfunction or deficiency that would have precluded normal operation. Although the right main landing gear was found in the stowed position and its wheel axle and gear door showed scraping marks, an airport surveillance video showed that all three landing gear appeared to be in the down position during the airplane’s takeoff after the aborted landing.

## Factual narrative

On April 24, 2024, about 1010 eastern daylight time, a Socata TBM 850, N228CH, was substantially damaged when it was involved in an accident near Raleigh, North Carolina. The airline transport pilot was seriously injured, and the passenger received minor injuries. The airplane was operated by Medical Air, Inc. as a Title 14 Code of Federal Regulations Part 91 business flight. The accident occurred following an aborted landing on runway 32 at Raleigh-Durham International Airport (RDU). According to the passenger, the airplane was “rolling” and “tobogganing…as if we were descending a hill on the snow” during the final approach. He said the airplane touched down twice, after which the pilot appeared to “turn and roll the airplane left as if to take off again.” He added that the pilot made no announcements and that there was no communication between them from runway contact to the accident site. The passenger stated that, in the bank, “it felt as if the plane lost power” but that he couldn’t detect if the engine had stopped. The pilot reported that he was “not clear on all that occurred” but remembered seeing dust from when the propeller contacted the runway. He was concerned that he would not be able to stop on the runway and would collide with another airplane on the intersecting runway, so he aborted the landing. He said that, once the airplane was airborne, he made a tight left turn to avoid this traffic and the airplane stalled. The pilot said his last thought was to “unload the wing and try to flatten contact with the ground.” Airport surveillance video captured the airplane on final approach in the area consistent with the touchdown zone of runway 32. As the airplane approached the surface, it was temporarily blocked from view by a VOR antenna. Both the view obscuration and the low resolution of the video precluded determining any details about the airplane’s configuration. After the airplane came back into view, a plume consistent with dust or smoke bloomed around the propeller and briefly enveloped the fuselage as it continued just above the surface for about 1,500 ft before it transitioned to a climb attitude and banked left. During the left bank, all three landing gear appeared to be in the down position. The airplane stopped its climb about 100 ft above ground level and slowed while the left bank steepened to nearly 90° as the airplane descended to ground contact. Review of surveillance videos and photographs revealed that the airplane impacted the ground with its left wing tip and nose almost simultaneously. The airplane rotated an additional 45°, coming to rest upright. The propeller separated from the engine and the leading edges of each of the four blades displayed gouging and chordwise scratching near the tips. The airplane sustained substantial damage to the fuselage, empennage, and both wings. The nosewheel had separated from the airframe. The left main landing gear had separated from the wing, and the right main landing gear wasfound stowed in the right wing. The back side of the right main landing gear wheel axle and the aft lower edge face of the landing gear door showed scrape marks. The airplane was equipped with a Garmin GDU 1060 Electronic Flight Instrument System (EFIS) that recorded numerous flight parameters. The unit recorded the entire flight starting at 0930 and ending at 1009:18, but the impact was not recorded. A review of the last minute of data revealed that the airplane first touched down on the runway at 1008:50 at 80 kts indicated airspeed (KIAS), then initiated a climbing left turn at 1009:15 at 65 KIAS before the data ended 3 seconds later. The airplane was equipped with a Shadin Engine Trend Monitor that capable of tracking and recording certain engine performance parameters, such as “Logon,” “Engine Start,” “Take-Off,” “Power Check Report,” “Landing Report,” and “Engine Off Log,” as well as engine parameter exceedances. The accident flight’s data file was about 22 minutes long and contained only the “Logon,” “Engine Start,” “Take-off,” and “Power Check Report” parameters. No “Landing Report,” “Engine Off Log,” nor “Exceedance Report” was recorded. At the time of the accident flight’s “Power Check,” the engine was operating normally. Postaccident examination of the airplane revealed no malfunction or deficiency that would have precluded normal operation.

## Aircraft

- Registration: [N228CH](https://openairdocs.org/deregistered/N228CH-2024-07-16), registration cancelled 2024-07-16, S/N 356, built 2006 (OpenAirDocs)
- Reported make and model: SOCATA TBM 850
- Registry model: [Socata TBM 700](https://openairdocs.org/model/socata-tbm-700) (registry code 8682000) (OpenAirDocs)
- Registry engine: [Pratt & Whitney Canada PT6A-66 series](https://openairdocs.org/engine/pratt-whitney-canada-pt6a-66-series) (registry code 52118, turbo-prop) (OpenAirDocs)
- Category: Airplane
- Serial number: 356
- Year built: 2006
- Airframe hours: 4523
- Engines: Pratt & Whitney PT6A-66D 850 horsepower turbo prop
- Damage: Substantial damage
- Flight: Business, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, August 24, 2023, 122 hours before
- Departed: KILM, Wilmington, NC
- Destination: Same as departure
- Flight plan: IFR
- Airport: RDU, Raleigh-Durham Intl, runway 14/32, 3,570 × 100 ft, asphalt
- Equipment: Stall warning system, ADS-B, Electronic multifunction display, Auto-pilot

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 65; injuries: serious; airline transport; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 16,000 total, 2,500 in this make and model

## Weather

- Conditions: Visual (VMC), Day
- Wind: 290° at 6 knots
- Visibility: 10 statute miles
- Lowest ceiling: 9,000 ft broken
- Temperature: 64 °F, dew point 46 °F
- Altimeter: 30.05 inHg
- Observed at: KRDU, 1 nm away
- METAR: KRDU 241420Z 29006KT 10SM BKN090 BKN200 BKN250 18/08 A3005 RMK T01780083

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20240424004309A](https://openairdocs.org/incident/20240424004309A), Apr 24, 2024: Socata TBM 700, Morrisville, NC, Destroyed. Raleigh/Durham, NC (rdu):tbm 850, aircraft crashed into the overrun area of runway 32. 2 POB transported to the hospital. Pilot was airlifted to duke…

## Docket (13 files)

The files NTSB released with the investigation on May 13, 2026, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=194143. 100 MB in all.

- Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 10 pages, 3.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18789069&FileExtension=pdf&FileName=NTSB228CH%206120_Redacted-Rel.pdf
- NTSB mor - pilot statement (item 2, PDF, 1 page, 73 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20049542&FileExtension=pdf&FileName=NTSB%20MOR%20-%20Pilot-Rel.pdf
- NTSB mor - passenger (item 3, PDF, 1 page, 63 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20051686&FileExtension=pdf&FileName=NTSB%20MOR%20-%20Passenger-Rel.pdf
- Photo array (item 4, PDF, 6 pages, 11.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18804436&FileExtension=pdf&FileName=Docket%20Photo%20Array%20LA191_Redacted-Rel.pdf
- NTSB airplane examination report (item 5, PDF, 4 pages, 120 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20049027&FileExtension=pdf&FileName=NTSB%20AIrplane%20Examination%20Report-Rel.pdf
- Electronic devices - specialist's factual report (item 6, PDF, 9 pages, 813 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18152481&FileExtension=pdf&FileName=ERA24LA191%20Report-Rel.pdf
- Electronic devices - specialist's factual report - attachment 1 (item 7, CSV, 205 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18153196&FileExtension=csv&FileName=Attachment%201-Rel.csv
- Electronic devices - specialist's factual report - attachment 2 (item 8, TXT, 841 B): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18168306&FileExtension=txt&FileName=Attachment%202-Rel.txt
- Security camera video 1 (item 9, MP4, 23.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18152929&FileExtension=mp4&FileName=SecurityCam1_edited-Rel.mp4
- Security camera video 2 (item 10, MP4, 54.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18153328&FileExtension=mp4&FileName=SecurityCam2_edited-Rel.mp4
- Security camera video 3 (item 11, MP4, 6.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18153222&FileExtension=mp4&FileName=SecurityCam3_edited-Rel.mp4
- Security camera still images (item 12, PDF, 4 pages, 7 photos, 389 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18153876&FileExtension=pdf&FileName=ERA24LA191%20Security%20Camera%20Still%20Images-Rel.pdf
- Release of aircraft wreckage, NTSB form 6120.15 (item 13, PDF, 2 pages, 129 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18789259&FileExtension=pdf&FileName=Release%20of%20Aircraft%20Wreckage%2024LA191_Redacted-Rel.pdf

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.