LAX04FA002 · Lockheed P2V
Lockheed P2V · Accident: in flight encounter with weather while maneuvering
From Prescott Regional Airport - Ernest A. Love Field (PRC) to San Bernardino International Airport (SBD)
Event
- NTSB case
- LAX04FA002
- 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
- 2 · 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
- Instrument Meteorological Cond
Lockheed P2V
- 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
- N299MA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo San Bernardino International Airport (SBD), San Bernardino, CA
- 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 91: General Aviation
- 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 encounter with weather
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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
- Pilot in command › Altitude/clearance, not maintained
- Pilot in command › In-flight planning/decision, inadequate
- Pilot in command › VFR flight into imc, continued
- Pilot in command › Weather evaluation, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The fire tanker airplane was on a cross-country positioning flight and collided with mountainous terrain while maneuvering in a canyon near the destination airport. Witnesses who held pilot certificates were on a mountain top at 7,900 feet and saw a cloud layer as far to the south as they could see. They used visual cues to estimate that the cloud tops were around 5,000 feet mean sea level (msl). They noted that the clouds did not extend all the way up into the mountain canyons; the clouds broke up near the head of some canyons. When they first saw the airplane, they assumed that it came from above the clouds. It was proceeding north up a canyon near the edge of clouds, which were breaking up. They were definitely looking down at the airplane the whole time. They saw the airplane make a 180-degree turn that was steeper than a standard rate turn. The wings leveled and the airplane went through one cloud, reappeared briefly, and then entered the cloud layer. It appeared to be descending when they last saw it. About 2 minutes later, they saw the top of the cloud layer bulge and turn a darker color. The bulge began to subside and they observed several smaller bulges appear. They notified local authorities that they thought a plane was down. Searchers discovered the wreckage at that location and reported that the wreckage and surrounding vegetation were on fire. The initial responders reported that the area was cloudy and the visibility was low. Examination of the ground scars and wreckage debris path disclosed that the airplane collided with the canyon walls in controlled flight on a westerly heading of 260 degrees at an elevation of 3,400 feet msl. The operator had an Automated Flight Following (AFF) system installed on the airplane. It recorded the airplane's location every 2 minutes using a GPS. The data indicated that the airplane departed Prescott and flew direct to the Twentynine Palms VORTAC (very high frequency omni-directional radio range, tactical air navigation). The flight changed course slightly to 260 degrees, which took it to the northeast corner of the wilderness area where the accident occurred. At 1102:57, the data indicated that the airplane was at 11,135 feet msl at 204 knots. The airplane then made three left descending 360-degree turns. The third turn began at 6,010 feet msl. At 1116:57, the last recorded data point indicated that the airplane was at an altitude of 3,809 feet heading 256 degrees at a speed of 128 knots.
Probable cause
the pilot's inadequate in-flight planning/decision and continued flight into instrument meteorological conditions that resulted in controlled flight into mountainous terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04FA002
- Event ID
- 20031009X01699
- Case number
- LAX04FA002
- 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: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 2512056d97edeb974fff05544ba12f4fdb0c835bc16688df12441df1126c8d20; retrieved 2026-09-20T18:55:17.485Z.