Cessna 340A accident near Boise, Idaho, October 12, 2023
On October 12, 2023 at about 8:50 am local time, a 1981 Cessna 340A, registered N682JS, was substantially damaged in an accident during taxi (to runway) near Boise, Idaho (Boise Air Terminal/Gowen Field). It was a positioning flight under general aviation rules (Part 91). No one was hurt; 1 person was 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 directional control while taxiing, which resulted in impact with a fence.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 12, 2023 · about 8:50 am local time · cases in 2023
- Place
- Boise, Idaho · Boise Air Terminal/Gowen Field · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 340A, built 1981 · all 340As on the register
- Registration
- N682JS · registry record · serial 340A1237
- Damage
- Substantial damage
- Flight
- Positioning flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
While taxiing for departure in night visual meteorological conditions, the airplane drifted left of the taxiway centerline and the left wingtip impacted a fence, resulting in substantial damage and a postimpact fire when the left wingtip fuel tank was breached. Although the pilot reported that the right brake failed while attempting to stop, review of surveillance video footage indicated that the airplane was traveling at a relatively constant speed with no noticeable change in speed or direction before impact with the fence. Examination of the airplane’s brake system, nose wheel steering system, wheels, and tires revealed no evidence of any failures or malfunctions that would have precluded normal operation. Based on the available information, it is likely that the pilot failed to maintain directional control while taxiing, which resulted in impact with the fence.
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
- Ground collision during taxi (to runway) defining event
The NTSB's findings
- Personnel issues › Psychological › Attention/monitoring › Monitoring environment › Pilot
- Environmental issues › Physical environment › Object/animal/substance › Fence/fence post › Awareness of condition
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instrument: airplane; instrument: helicopter; rotorcraft: helicopter
- Flight time: 4,560 hours in all; 240 in this make and model; 121 in the last 90 days; 25 in the last 30 days; 3,890 as pilot in command
- Last flight review: May 23, 2023
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 12,085 hours
- Last inspection: approved inspection programme, October 12, 2023
- Maximum gross weight: 6,290 lb
- Seats: 2
- Landing gear: retractable
- Engine 1: Continental TSIO-520-NB (piston); 1,230 hours total
- Engine 2: Continental TSIO-520-NB (piston); 5,026 hours total
- Fire on the ground
- Operator: Western Airlines Lc
The flight
- Destination: SFF Spokane WA
- Flight plan: IFR
Weather at the time
- Light: night
- Wind: from 320° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 45°F (7°C), dew point 39°F (4°C)
- Altimeter: 29.91 inHg
- Observation at 2:53 am from KBOI, 1 miles away
Weather report (METAR): METAR KBOI 120853Z AUTO 32005KT 10SM CLR 07/04 A2991 RMK AO2 SLP126 T00670044 53014
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on February 26, 2025. 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 | Airframe Examination Summary Report | PDF, 6 pages | View Download |
| 3 | Airport Surveillance Video (Courtesy of Airport Operations) | ASF file | 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
- N682JS on the register today · the tail number may have moved to another aircraft since
- Cessna 340 706 registered today · the model family and its accident history
- Cessna 72,677 aircraft on the register
- Engine: Continental TSIO-520-NB 52 aircraft carry this series today · as the NTSB recorded it
- Engine: Continental TSIO-520-NB 52 aircraft carry this series today · as the NTSB recorded it
- Boise Air Trml/Gowen Field · nearest airport
- Felts Field · bound for
- Accidents and incidents in Idaho 1,535 since 1982 · 287 in the last ten years
- Idaho 4,201 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR24LA013.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.
