FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA05MA085 · Lockheed P-3B

20 Apr 2005 · Chico, CA, United States

Lockheed P-3B · Accident: in flight collision with terrain/water while maneuvering

From Chico Regional Airport (CIC) to Chico Regional Airport (CIC)

Report a problem

Event

NTSB case
SEA05MA085
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
3 · 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
General aviation
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 P-3B

Aircraft type
Lockheed P-3
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
N926AU
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chico Regional Airport (CIC), Chico, CATo Chico Regional Airport (CIC)
Aircraft age
Not recorded
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
Part 137: Agricultural
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
Maneuvering
First occurrenceThe 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
In flight collision with terrain/water
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Flightcrew › Clearance, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

Terrain clearance was not maintained while maneuvering for undetermined reasons. Mountainous terrain was a factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA05MA085
Event ID
20050425X00501
Case number
SEA05MA085
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-04-21.
  • API snapshot SHA-256: dd046e39129f58bbf8505184bbdf07b865c2c81808db991736d7de64ff0b9ea4; retrieved 2026-09-20T18:04:29.863Z.