LOCKHEED P2V-7 near Reno, NV — 2008-09-02
- Date
- 2008-09-02
- Location
- Reno, NV, USA
- Airport
- RTS
- Aircraft
- LOCKHEED P2V-7
- Registration
- N4235T
- Category
- Airplane
- Highest injury
- Fatal
- Fatalities
- 3
- Phase of flight
- Takeoff roll
Probable cause
The failure of the flight crew to maintain airspeed above in-flight minimum control speed (Vmca) after losing power in the left jet engine during initial climb after takeoff. Contributing to the accident was the crew's inadequate cockpit resource management procedures, the failure of the captain to assume command of the airplane during the emergency, the flight crew's failure to carry out the jet engine fire emergency procedure, and the failure of the crew to jettison the retardant load.
Contributing factors
Contributing to the accident was the crew's inadequate cockpit resource management procedures, the failure of the captain to assume command of the airplane during the emergency, the flight crew's failure to carry out the jet engine fire emergency procedure, and the failure of the crew to jettison the retardant load.
NTSB narrative
Just after the airplane's landing gear was retracted during takeoff for a retardant drop mission, a ball of fire was observed coming out of the left jet engine before the airplane rolled steeply to the left and descended into the terrain. Prior to takeoff, the captain said he would make the takeoff and provided a takeoff briefing concerning the runway to be used and his intentions should an emergency develop. Shortly thereafter, the captain informed the co-pilot that this would actually be his (the co-pilot's) takeoff. On the cockpit voice recorder, the co-pilot stated "Same briefing (sound of laughter)". The co-pilot did not give an additional takeoff briefing beyond the one given by the captain and the captain did not ask the co-pilot to give one. During the initial climb, the captain said he detected a fire on the left side of the airplane and the co-pilot responded that he was holding full right aileron. At no point did either pilot call for the jettisoning of the retardant load as required by company standard operating procedures, or verbally enunciate the jet engine fire emergency checklist. Recorded data showed that the airplane's airspeed then decayed below the minimum air control speed, which resulted in an increased roll rate to the left and impact with terrain. The 11th stage compressor disc of the left jet engine failed in fatigue, which caused a catastrophic failure of the compressor section and the initiation of the engine fire. Metallurgical examination of the fracture identified several origin points at scratches in the surface finish of the disk. The scratches were too small to have been observed with the approved inspection procedures used by the company. A review of the FAA sanctioned Approved Aircraft Inspection Program, revealed no shortcomings or anomalies in the performance or documentation of the program. A post-accident examination of the airframe and three remaining engines revealed no anomalies that would have precluded normal operations.
Analysis
- Primary failure mode
- Engine power loss
- First missed decision gate
- Crew could have aborted takeoff upon engine fire indication.
NTSB coding
Evidence available
- CVR
- Photos
- 43 docket documents
Docket documents43
- Cockpit Voice Recorder 12 - Specialist's Summary Report of Investigationcvr
- Aircraft Performance 13 - Airplane Performance Studyform
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- Release of Aircraft Wreckage, NTSB Form 6120.15form
- Release of Aircraft Wreckage, NTSB Form 6120.15form
- Record of Interview with Tanker 09 Crew Chiefinterview
- Statement of Party Representatives to NTSB Investigationinterview
- Witness Statementsinterview
- Accident Site Mapsother
- Excerpts from NATOPS Flight Manualother
- Neptune P-2V Normal & Emergency Procedures Checklistsother
- Pilot Training Record - Copilotother
- Pilot Training Records - Captainother
- Record of Conversation (VP of Operations)other
- USFS (Party Status Correspondence)other
- USFS Contract Excerpts (Emergency Load Drop)other
- Image 1. Accident site looking North.photos
- Image 10. Number one gas jet engine compressor blades.photos
- Image 11. View 1 of number one gas jet engine.photos
- Image 12. View 2 of number one gas jet engine.photos
- Image 13. View 3 of number one gas jet engine.photos
- Image 14. Number two gas jet engine.photos
- Image 15. Aft fuselage and center wing section.photos
- Image 16. Empennage components.photos
- Image 17. Left aileron.photos
- Image 18. Right outboard wing section.photos
- Image 19. Radial engine power control quadrant.photos
- Image 2. Accident site looking East.photos
- Image 3. Accident site looking South.photos
- Image 4. Accident site looking West.photos
- Image 5. Accident site overhead view.photos
- Image 6. Number one gas jet engine compressor.photos
- Image 7. Number one gas jet engine 11th stage compressor disc with mating shaft.photos
- Image 8. Number one gas jet engine 11th stage compressor disc (mating piece).photos
- Image 9. Number one gas jet engine fuel cutoff valve in "open" position.photos
- Maintenance Records 11 - Factual Report of Group Chairmanreport
- Materials Laboratory 15 - Factual Report 09-001report
- Materials Laboratory 15 - Factual Report 09-022 Exemplar Discsreport
- Structures 7 - Factual Report of Group Chairmanreport
- Toxicological Report - Captainreport
- Toxicological Report - Copilotreport
- Weather Reportreport
- Wreckage Diagramswreckage
Related mishaps
- DIAMOND AIRCRAFT IND INC DA 40 NG
2025-05-07 · Sanford, NC
- CESSNA 172A
2025-03-16 · Fairbanks, AK
- CESSNA 172C
2025-02-20 · Argyle, NY
- ZENITH Zodiac CH601
2024-12-08 · Columbia, IL
- CESSNA 172
2024-09-11 · Englewood, CO
- PIPER PA-28R-201T
2024-08-04 · Sacramento, CA