Lockheed P-3 Orion

After landing at Bagram AFB, the crew encountered difficulties to decelerate properly. Unable to stop within the remaining distance, the aircraft overran, lost its right main gear and came to rest, bursting into flames. There were no injuries among the occupants and the aircraft was damaged beyond repair.

Prior to the accident flight, the air tanker airplane had flown 9 times on the day of the accident, for a total flight time of 5 hours and 46 minutes. The purpose of the flights was to provide recurrent training for pilots scheduled to conduct fire-fighting operations for the United States Department of Agriculture Forest Service (USFS) during the upcoming fire season. Pilots aboard the airplane during the earlier flights reported no mechanical problems with the airplane. As was the mission for other flights that day, the accident flight, the tenth flight, was a training flight to conduct practice drops of water over an area of rugged mountainous terrain located north of the airport. Aboard the flight were the captain, the copilot, and the company's Chief Pilot, who was providing flight instruction. The Chief Pilot had been on board all the flights that day. Radar data indicated that the flight departed the airport and proceeded about 10.5 nautical miles to the north where it began maneuvering in a manner consistent with the conduct of practice water drops. The data showed the airplane entering and then following a right-hand racetrack pattern oriented northeast-southwest, during which it appeared that practice drops were being made on the southwest leg. During the last minute of the flight, the airplane was on the northeast leg of the racetrack pattern, flying up a valley that was oriented northeast-southwest with uphill being to the northeast. The airplane's flight path was initially near the middle of the valley. During the last 36 seconds of the flight, the airplane's flight path began to deviate towards the rising terrain on the eastern side of the valley. The last two radar hits show the airplane at an altitude of less than 100 feet above ground level. The airplane had completed approximately 1.75 circuits of the racetrack when the data ended with the airplane at 2,900 feet msl, heading northeast. The initial impact point was located about 2,150 feet northwest of the last radar data point at an elevation of about 2,450 feet msl, indicating the airplane entered a left descending turn and completed about 90 degrees of turn between the last radar hit and the impact. No distress calls were received from the airplane. According to local authorities, witnesses observed a "fire ball" at the time of the accident. Examination of the wreckage site revealed that the airplane impacted on about a 304 degree magnetic heading in a 40 degree left bank with the left wingtip striking the ground first. The airplane was severely fragmented and a severe post crash fire burned most of the structure and surrounding vegetation. Remnants of the entire airplane were accounted for at the wreckage site. There was no evidence of pre-existing structural failures or impact with foreign objects in any of the wreckage. All four of the engines and propellers were found at the wreckage site. The engines did not have any indications of an uncontainment, case rupture, or pre-impact in-flight fire. All four engines had damage to the compressor and/or turbine rotors that was consistent with engine operation. The cockpit engine instrumentation gages indicate that all four engines were running at about 2,200 shaft horsepower at impact. Review of the airplane's maintenance records did not reveal any chronic issues with the airplane nor any system/component anomalies that would have contributed to the accident. The airplane was equipped with neither a cockpit voice recorder (CVR) nor a flight data recorder (FDR) and Federal Aviation Regulations did not require the airplane to be so equipped. The reason for the in-flight collision with terrain could not be determined.

Crashed in unknown circumstances in the sea off Pasni while completing a maritime patrol flight. All 21 occupants were killed.

After touchdown at Chania-Souda Airport, the four engine aircraft went out of control, veered off runway, lost its undercarriage and came to rest. All 26 occupants escaped uninjured while the aircraft was written off.

While completing a maritime survey flight off Masirah Island, the crew encountered technical difficulties when the propeller detached from the engine n°4 that caught fire. Shortly later, the engine n°3 lost power then engine n°1 & 2 also lost power and failed. The aircraft lost height but the crew was able to regain control at 2,500 feet and eventually ditched the aircraft 8 km offshore. All 11 occupants were quickly rescued while the aircraft sank and was lost.

Belly landed at Iwo Jima Airport and was damaged beyond repair. There were no casualties.

Air tanker N924AU had been dispatched from its base in Santa Barbara, CA to Missoula, MT to support fire suppression efforts involving a number of large fires in the Northern Region. The flight departed in VFR conditions at 16:05 PDT. While still in the area controlled by the Oakland FAA Air Route Traffic Control Center (ARTCC), the crew requested and received an Instrument Flight Rules (IFR) clearance. They were assigned an altitude of 23,000 feet. The Orion proceeded uneventfully and was handed off to the Approach Controller at Missoula (MSO). MSO Approach did not have, at that time, terminal radar equipment that covered their entire area of responsibility. At first contact with MSO Approach, the Orion was 26 miles southeast of the Missoula International Airport and descending to 12,000 feet. In the course of several exchanges between the Orion and the MSO Approach Controller, it was disclosed and confirmed that the Orion’s flight crew did not have the approach plate (or chart) depicting the published approach procedure for the VOR-DME Bravo (B) approach, which was the approach in use for aircraft arriving from the south. Clearance was nevertheless offered and accepted and the controller provided the information as the Orion crew began to execute the VOR-DME B approach. At this time, the cloud bases at the MSO Airport were at about 7,900 feet and other aircraft making instrument approaches there were descending through 8,000 feet, cancelling their IFR flight plans and making visual approaches to the airport for landing. Since the Orion’s crew was able to monitor these radio communications/transmissions on the same frequency, they were probably counting on doing the same. At this time, there were very strong winds and moderate to severe turbulence reported at altitudes above 8,000 feet that increased with altitude in the MSO area. In addition to turbulence, the Orion crew contended with effects of flying at high altitudes, using oxygen in an unheated and un-pressurized aircraft for more than two hours. At some point in the initial phase of the approach, some confusion as to what heading to fly apparently occurred and the airtanker turned back toward the south, away from MSO. By this time the controller had authorized descent to 8,600 feet on an approximate heading of 200 degrees magnetic. MSO Approach received notification by Salt Lake City ARTCC (Center) that this airtanker was west of the course consistent with the approach procedure and subsequent notification that the airtanker had disappeared off Center’s radar screen. Repeated attempts to contact the Orion crew failed and MSO Approach notified the County Sheriff’s office, the Forest Service, and other agencies that the aircraft was missing and presumed down. Search and rescue attempts were not able to detect an Emergency Locator Transmitter (ELT) signal. The mishap site was located the following day.
Source: https://www.fs.usda.gov/managing-land/fire by Candy S. Rock Fitzpatrick.