Socata TBM-850 accident near Salem, Ohio, May 19, 2011
On May 19, 2011 at about 12:43 pm local time, a Socata TBM-850, registered N1UL, was substantially damaged in an accident during approach (VFR pattern final) near Salem, Ohio (Salem Airpark airport). It was a business flight under general aviation rules (Part 91). 1 person was seriously injured; 3 others were unhurt. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain a stabilized glide path which resulted in the airplane touching down short of the runway.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 19, 2011 · about 12:43 pm local time · cases in 2011
- Place
- Salem, Ohio · Salem Airpark · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person was seriously injured; 3 others were unhurt.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Socata TBM-850
- Registration
- N1UL · registry record · serial 564
- Damage
- Substantial damage
- Flight
- Business flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that he flew an instrument approach and was clear of clouds about 650 feet above ground level when he proceeded visually to the airport. About 1/2 mile from the runway, he thought the airplane was too high, but a few seconds later the airplane felt like it had an excessive rate of descent. His attempts to arrest the rate of descent were unsuccessful, and the left main landing gear struck the ground about 120 feet prior to the runway threshold. The recorded data downloaded from the airplane's non-volatile memory showed that the airplane's airspeed varied from about 71 - 81 knots indicated airspeed (IAS) during the 10 seconds prior to ground impact. The data also indicated that there was about a 3 - 5 knot tailwind during the final landing approach. The airplane's stall speed with the airplane in the landing configuration with landing flaps was 64 knots IAS at maximum gross weight. The pilot reported that there was no mechanical malfunction or system failure of the airplane.
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
- Miscellaneous/other during approach (VFR pattern final) defining event
- Attempted remediation/recovery during approach (VFR go-around)
- Collision with terrain or object (not controlled flight into terrain) during approach (VFR go-around)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Contributed to outcome
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 932 hours in all; 76 in this make and model; 55 in the last 90 days; 28 in the last 30 days; 879 as pilot in command
- Last flight review: October 31, 2010
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 187 hours
- Last inspection: 100-hour inspection, February 25, 2011
- Maximum gross weight: 7,395 lb
- Seats: 6
- Landing gear: retractable
- Engine: Pratt & Whitney Canada PT6A-66D (turboprop); 0 hours total
The flight
- Departed from: VPZ Valparaiso IN at 11:22 am
- Destination: 38D Salem OH
- Flight plan: IFR
- Runway 10L, 3,404 ft by 50 ft
Weather at the time
- Light: daylight
- Wind: from 200° at 5 knots
- Visibility: 2.5 statute miles
- Sky: overcast at 500 ft; not recorded
- Temperature: 54°F (12°C), dew point 52°F (11°C)
- Altimeter: 29.96 inHg
- Observation at 12:26 pm from YNG, 20 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on June 29, 2011. 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, 9 pages | View Download |
| 2 | Witness Statement | PDF, 1 page | View Download |
| 3 | Gps-a Approach Plate | PDF, 1 page | View Download |
| 4 | GPS Plots on A Map (7 Plots) | PDF, 7 pages | View Download |
| 5 | Garmin GPS Data Download (40 Sec) | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N1UL on the register today · the tail number may have moved to another aircraft since
- Engine: Pratt & Whitney Canada PT6A-66D 322 aircraft carry this series today · as the NTSB recorded it
- Salem Airpark · nearest airport
- Porter County Regional · departed from
- Accidents and incidents in Ohio 1,884 since 1982 · 253 in the last ten years
- Ohio 8,534 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN11LA345.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
