FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX07FA012 · Piper PA-42

18 Oct 2006 · Prescott, AZ, United States

Piper PA-42 · Accident: airframe, component or system failure while maneuvering

From Prescott Regional Airport - Ernest A. Love Field (PRC) to an unrecorded destination

Report a problem

Event

NTSB case
LAX07FA012
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
5 · 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

Piper PA-42

Aircraft type
Piper PA-42
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
N121CS
Onboard fatalities
Unknown
Route
From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo not recorded
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
Airframe, component or system failure
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 › Clearance, 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 pilot of a MiG 21 and the pilot of a Piper PA-42 Cheyenne III met just prior to the flight to discuss the flight in which the Cheyenne pilot would be taking aerial photos of the MiG. The two pilots established a minimum altitude of 2,500 to 3,000 feet agl and 200 knots as their minimum airspeed. The pilots did not establish a minimum separation distance, as it was not intended to be a formation flight. The MiG pilot reported that after takeoff the aircraft experienced a problem with the landing gear retraction. The pilot recycled the landing gear and a successful gear retraction was indicated. The MiG pilot notified the Cheyenne pilot of the situation and the Cheyenne pilot indicated that they would join up with the MiG, look it over and check-out the landing gear, and let the MiG pilot know what they saw. The MiG pilot flew at 9,000 feet msl in a 30-degree right hand turn at 200 knots (about 90 percent power set) with approach flaps selected (approximately 25 degrees) until the Cheyenne met up with the MiG. The MiG pilot reported that he observed the Cheyenne meet up with him at his 5 o'clock position about 300-400 feet behind him and about the same altitude. In this position, the Cheyenne was in the direct path of the high velocity jet core exhaust from the MiG. The MiG pilot looked forward and when he looked back, he could not see the Cheyenne. The Cheyenne pilot then contacted the MiG pilot and made a comment about the right landing gear or gear door, but the statement was not completed. The MiG pilot did not hear back from the Cheyenne pilot. The MiG pilot then observed smoke rising from the desert terrain and notified air traffic control. The airport manager that was monitoring the conversation between the two aircraft stated that he heard the Cheyenne pilot indicate that he would "drop down and go underneath and let you know how it looks." Wreckage documentation noted that the main wreckage was located in an inverted position on flat terrain. The T-tail, which consisted of the upper half of the vertical stabilizer, horizontal stabilizer, and elevator had separated in flight and was located about 1/2 mile south of the main wreckage. Inspection of the upper portion of the aft vertical spar displayed a right bend and twist at the point of separation. No evidence of pre-existing cracks, corrosion or wear was noted to the material. Inspection of the MiG aircraft found no evidence of contact between the two aircraft.

Probable cause

The failure of the pilot following a jet aircraft to maintain adequate separation from the high velocity jet core exhaust. The separation of the T-tail upper section vertical stabilizer of the following aircraft due to contact with the high velocity jet core exhaust was a factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX07FA012
Event ID
20061026X01561
Case number
LAX07FA012
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: 95b345a761c9e534aa97f344e6c8ab9e660f57f064ed396b5579ae6567e855cc; retrieved 2026-09-20T17:01:32.675Z.