The U.S. aircraft register, updated daily
Accidents · NTSB ERA23LA147 · Final report

Eurocopter Deutschland GMBH EC 135 P2+ accident near Franklin, North Carolina, March 9, 2023

On March 9, 2023 at about 11:57 pm local time, a 2012 Eurocopter Deutschland GMBH EC 135 P2+ (helicopter), registered N558MT, was substantially damaged in an accident during enroute (cruise) near Franklin, North Carolina. It was flown under charter and air-taxi rules (Part 135). 3 people had minor injuries; 1 other was unhurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s improper decision to review an aircraft logbook while enroute, which resulted in controlled flight into terrain.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
March 9, 2023 · about 11:57 pm local time · cases in 2023
Place
Franklin, North Carolina · map
Type
Accident
Injuries
3 people had minor injuries; 1 other was unhurt.
Weather
visual conditions (good weather)
Aircraft
Eurocopter Deutschland GMBH EC 135 P2+, built 2012
Registration
N558MT · registry record · serial 1073
Damage
Substantial damage
Flight
Flight · charter and air-taxi rules (Part 135)

The NTSB's narrative final · quoted from the NTSB record

According to the pilot, prior to the flight, he determined the highest obstacle enroute was 6,100 ft with several 5,000 to 5,500 ft peaks along the route. In addition, he noted that during the flight, the end of evening nautical twilight would occur. After departure, he dialed 5,500 ft into the autopilot and leveled off. He went to don the night vision goggles and noted that they were on the copilot seat on top of an aircraft logbook. He went to move the logbook to the pilot door compartment, where it was typically stowed for flight, and decided to check the flight times against the times that maintenance was due. At that point, he noticed the cloud ceiling was lowering and dialed in 5,000 ft into the autopilot, then “went back heads down” to continue his review of the logbook. Then, the flight nurse asked for an updated estimated time enroute, and when the pilot looked up, he saw the helicopter was approaching a tree covered peak. He applied aft cyclic in order to climb; however the tail boom struck several trees, resulting in the vertical stabilizer separating from the tail boom. The pilot subsequently performed a forced landing to a road, which resulted in substantial damage to the fuselage and tail boom. The pilot reported no preimpact mechanical malfunctions or failures with the helicopter that would have precluded normal operation.

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

  1. Controlled flight into terrain or object (CFIT) during enroute (cruise) defining event

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Decision related to condition
  • Personnel issues › Task performance › Workload management › Task allocation › Pilot
  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › Pilot

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land; instrument: airplane; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 4,723 hours in all; 1,867 in this make and model; 3,992 as pilot in command
  • Last flight review: March 1, 2023
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 6,067.7 hours
  • Last inspection: approved inspection programme, February 23, 2023
  • Maximum gross weight: 2,950 lb
  • Seats: 7
  • Landing gear: fixed
  • Engine 1: Pratt & Whitney PW206B2 (turboshaft); 5,665 hours total
  • Engine 2: Pratt & Whitney PW206B2 (turboshaft); 10,120 hours total
  • Operator: Med-Trans Corporation

The flight

  • Departed from: 5NC4 Murphey NC at 11:44 pm
  • Destination: NC95 Asheville NC

Weather at the time

  • Light: night
  • Visibility: 10 statute miles
  • Sky: overcast at 5,000 ft
  • Temperature: 54°F (12°C), dew point 32°F (0°C)
  • Altimeter: 30.16 inHg
  • Observation at 7:15 pm from K1A5, 4 miles away

Weather report (METAR): METAR K1A5 100015Z AUTO 00000KT 10SM OVC050 12/00 A3016 RMK AO2 T01171001=

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers3

Photographs from the investigation 2 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

3 documents, released by the NTSB on June 7, 2023. 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.

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

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA23LA147.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.