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

Lockheed P2V 5F accident near Pocatello, Idaho, August 6, 2017

On August 6, 2017 at about 2:00 am local time, a 1954 Lockheed P2V 5F, registered N410NA, was substantially damaged in an accident during enroute (climb to cruise) near Pocatello, Idaho (Pocatello Rgnl airport). It was a firefighting flight under public-use (government) rules. No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

Maintenance personnel's failure to secure hardware, which resulted in an uncommanded upward deflection of the left elevator and aft movement of the control yoke and inhibited the flight crew from adjusting the airplane's pitch attitude in flight. Contributing to the accident was the lack of maintenance oversight, which should have identified the unsecured hardware before flight.

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

What the record shows

Date
August 6, 2017 · about 2:00 am local time
Place
Pocatello, Idaho · Pocatello Rgnl · map
Type
Accident
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Lockheed P2V 5F H, built 1954 · all P2V 5Fs on the register
Registration
N410NA · registry record · serial 131482
Damage
Substantial damage
Flight
Firefighting flight · public-use (government) rules

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

The company dispatched the accident airplane to a fire as part of an exclusive contract with the United States Forest Service and under the direction of the Bureau of Land Management. During the airplane's climb, the airline transport pilot, who was acting as pilot-in-command, adjusted the trim to reduce nose-down pressure and subsequently observed an uncommanded aft movement of the control yoke and simultaneous increase in the airplane's pitch attitude. The flight crew attempted to regain pitch control by adjusting the trim wheels, but the airplane continued to maintain a pitch-up attitude. Using coordinated inputs, the flight crew was able to land the airplane without incident. A postlanding examination revealed that the variable camber, or varicam, was damaged during the event. This secondary control surface is directly connected to the elevators and provides a primary structural load path for all elevator loads; thus, any damage to the varicam was considered substantial. Postaccident examination revealed that maintenance personnel had failed to secure the drive stop coupling bolts with lockwire and that one of the bolts had backed out of its bolt hole. Because the varicam likely did not display any deformation before takeoff, as it would have been inspected after the previous flight, the bolt likely backed out sometime during the takeoff. When the flight crew adjusted the varicam trim during the initial climb, the absence of this bolt prevented a section of the drive shaft from rotating, allowing only a portion of the varicam to move. This resulted in the deformation of the left side varicam and subsequent upward deflection of the left elevator, which is hinged to the varicam. The resulting feedback in the cockpit was an uncommanded aft movement of the control yoke, which placed the airplane in a pitch-up attitude that could not be corrected by flight control inputs from the cockpit.     The mechanic responsible for installing the lockwire was under stress due to family issues at the time of the varicam was last serviced. The company's task cards indicated that the mechanic failed to lockwire the drive stop coupling bolts to the drive stop, despite noting that the work had been completed by stamping the card with his designation. This omission should have been detected by either the facility's lead mechanic or the quality assurance (QA) inspector through the required inspection item (RII) process. However, the lead mechanic seldom oversaw inspections and most likely did not attempt to review this mechanic's work and others' work, as the investigation revealed 7 additional RII oversights. Further, the QA inspector, whose main duty was to review any work that had been stamped RII by the lead mechanic, failed to notice that the critical flight control areas had not been annotated as RIIs. Although the company retrains its RII staff biennially, the QA inspector did not appear to understand his role in the RII process, as he was reported to have given approvals without verifying if the work qualified as an RII. While the mechanic failed to secure the drive stop coupling with lockwire, the lead mechanic and the QA inspector's lack of oversight contributed to the omission that ultimately resulted in the varicam failure.

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 enroute (climb to cruise) defining event

The NTSB's findings

  • factor Organizational issues › Support/oversight/monitoring › Oversight › Oversight of maintenance › Maintenance provider
  • cause Personnel issues › Task performance › Maintenance › Repair › Maintenance personnel
  • cause Aircraft › Aircraft systems › Flight control system › Elevator tab control system › Failure

Pilot

  • Certificate: airline transport pilot, flight instructor, commercial pilot, flight engineer
  • Ratings: multi-engine land; single-engine land; instructor: glider; instrument: airplane; rotorcraft: glider
  • Flight time: 18,200 hours in all; 2,900 in this make and model; 200 in the last 90 days; 75 in the last 30 days; 15,000 as pilot in command; 650 on instruments
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 3,000 hours in all; 240 in this make and model; 150 in the last 90 days; 85 in the last 30 days; 2,600 as pilot in command
  • Last flight review: March 28, 2017
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 8,486.7 hours
  • Last inspection: approved inspection programme, July 10, 2017; 34 hours since
  • Maximum gross weight: 80,000 lb
  • Seats: 3
  • Landing gear: retractable
  • Engine 1: Westinghouse J34-WE-36A (piston); 441 hours total
  • Engine 2: Curtis Wright R-3350-32WA (piston); 6,337 hours total
  • Engine 3: Curtis Wright R-3350-32WA (piston); 6,598 hours total
  • Engine 4: Westinghouse J34-WE-36A (piston); 2,428 hours total
  • Operator: Neptune Aviation Services INC

The flight

  • Departed from: PIH Pocatello ID at 2:00 am
  • Destination: PIH Pocatello ID
  • Flight plan: none
  • Runway 21, 9,060 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 200° at 10 knots
  • Visibility: 6 statute miles
  • Sky: overcast at 4,200 ft
  • Temperature: 79°F (26°C), dew point 28°F (-2°C)
  • Altimeter: 29.92 inHg
  • Observation at 1:53 am from PIH, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew3

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

6 documents, released by the NTSB on August 10, 2018. 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.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.