FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17LA180 · Lockheed P2V 5F H

5 Aug 2017 · Pocatello, ID, United States

Neptune Aviation Services Lockheed P2V 5F H · Accident: flight control system malfunction/failure en route

From Pocatello Regional Airport (PIH) to Pocatello Regional Airport (PIH)

Report a problem

Event

NTSB case
WPR17LA180
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Government
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Lockheed P2V 5F H

Aircraft type
Lockheed P2
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N410NA
Onboard fatalities
Unknown
Route
From Pocatello Regional Airport (PIH), Pocatello, IDTo Pocatello Regional Airport (PIH), Pocatello, ID
Aircraft age
About 63 years (built 1954)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Public Aircraft
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · climb to cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Flight control system malfunction/failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17LA180
Event ID
20170806X05027
Case number
WPR17LA180
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2017-08-06.
  • API snapshot SHA-256: ef2bd857ab4a5a263dbfa2308c8593ff37b261ecffc5623b07e27b981170f2fe; retrieved 2026-09-16T05:40:00.821Z.