The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB WPR26LA302 · Preliminary: the investigation is not finished

Cessna 208B accident near Salmon, Idaho, August 9, 2026

On August 9, 2026 at about 8:20 pm local time, a 2013 Cessna 208B, registered N247JP, was substantially damaged in an accident during approach (VFR pattern base) near Salmon, Idaho (Lemhi County airport). It was flown under charter and air-taxi rules (Part 135). No one was hurt; 9 people were on board or involved. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

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

What the record shows

Date
August 9, 2026 · about 8:20 pm local time
Place
Salmon, Idaho · Lemhi County · map
Type
Accident
Injuries
No one was hurt; 9 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 208B, built 2013 · all 208Bs on the register
Registration
N247JP · registry record · serial 208B5047
Damage
Substantial damage
Flight
Flight · charter and air-taxi rules (Part 135)

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

On August 9, 2026, at 1420 mountain daylight time, a Cessna 208B airplane, N247JP, was substantially damaged when it was involved in an accident near Salmon, Idaho. The pilot and eight passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 135 on-demand air taxi flight. The pilot reported that, after an uneventful flight from the departure airport, he joined the downwind leg of the traffic pattern for runway 17. While turning onto the base leg, he extended the wing flaps in preparation for landing and subsequently heard a loud “pop.” Immediately thereafter, the airplane made an aggressive, uncommanded roll to the left and banked to about 45°. The pilot attempted to regain lateral control by applying right aileron. He moved the control yoke to the full right aileron position and adjusted the aileron trim to the full right setting. The airplane touched down normally, and the pilot taxied it to the ramp without further incident. Following the landing, a company mechanic examined the flight control systems and found substantial damage to the left wing spar. A preliminary examination identified a loose flap bolt that allowed the lower portion of the aft bellcrank to move freely. The aft bellcrank was designed to attach to the airplane with a bolt secured to an anchor nut assembly on its lower surface (see figure 1). The hardware will be retained for further examination. Figure 1: Diagram showing the location of the loose bolt

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. Flight control sys malf/fail during approach (VFR pattern base) defining event

The aircraft

  • Airframe total time: 7,229 hours
  • Last inspection: 100-hour inspection, July 27, 2026; 30 hours since
  • Maximum gross weight: 8,842 lb
  • Seats: 12
  • Landing gear: retractable
  • Operator: Gem Air LLC

The flight

  • Departed from: BOI Boise ID at 9:35 pm
  • Runway 17/3, 5,510 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 210° at 5 knots
  • Visibility: 7 statute miles
  • Sky: clear
  • Temperature: 90°F (32°C), dew point 54°F (12°C)
  • Altimeter: 29.94 inHg
  • Observation at 4:00 pm from KSMN

Weather report (METAR): METAR KSMN 102156Z AUTO 21005KT 7SM CLR 32/12 A2994 RMK AO2 SLP101 T03220117

Injuries

FatalSeriousMinorNone
Flig1
Passengers8

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number WPR26LA302.