Aviation Crash Map

Lockheed P2V 5F N410NA

6 August 2017 · Pocatello, Idaho, United States · No injuries

Summary

On 6 August 2017 at about 02:00 local time, a Lockheed P2V 5F registered N410NA, operated by Neptune Aviation Services Inc, was involved in an accident near Pocatello, Idaho, United States. 3 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 02:00
Classification
Accident
Location
Pocatello, Idaho, United States
Nearest airport
Pocatello Rgnl (PIH)
Coordinates
42.9058, -112.5908
Aircraft
Lockheed P2V 5F
Registration
N410NA
Category
Airplane
Year built
1954
Engines
4
Operating rule
Public Use
Purpose of flight
Fire Fighting
Phase of flight
Not recorded
Route
Pocatello → Pocatello
Aircraft damage
Substantial
Weather
VMC
Light
Night
NTSB number
WPR17LA180

People

Nobody was injured.

On board Died Serious Minor Uninjured
3 0 0 0 3

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.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full 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.

Quoted verbatim from the NTSB record.

Other Lockheed P2V accidents

Date Aircraft Location Operator Outcome Died
3 Jun 2012 Lockheed P2V-7
N14447
Modena, Utah, United States Neptune Aviation Services Inc Fatal 2
26 Jun 2010 Lockheed P2V-5
N1386C
Broomfield, Colorado, United States (USDA) Forestry Service No injuries -
25 Apr 2009 Lockheed P2V-7
N442NA
Stockton, Utah, United States Neptune Aviation Services Inc Fatal 3
2 Sep 2008 Lockheed P2V-7
N4235T
Reno, Nevada, United States Neptune Aviation Services Inc. Fatal 3
3 Oct 2003 Lockheed P2V
N299MA
East Highlands, California, United States - Fatal 2
29 Jul 1994 Lockheed P2V-7
N918AP
Missoula, Montana, United States Usfs Unknown -

All 8 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
8 May 2017 Piper PA 18A
N245KW
Coeur D'alene, Idaho, United States - Minor injuries -
5 Aug 2017 Champion 7ACA
N1227G
Nampa, Idaho, United States William Snethen No injuries -
4 Aug 2017 Rans S9
N519TB
Athol, Idaho, United States - Serious injuries -
20 Mar 2017 Swearingen SA226
N158WA
Boise, Idaho, United States - No injuries -
25 Mar 2017 Cessna 182
N52743
Mackay, Idaho, United States Avcenter Inc. Minor injuries -
8 Jul 2017 Champion 7KCAB
N5195X
Cottonwood, Idaho, United States - No injuries -

All 170,864 records in United States