LAX07LA045 · Nanchang CJ-6A
Nanchang CJ-6A · Accident: airframe, component or system failure while maneuvering
From Falcon Field (FFZ) to an unrecorded destination
Event
- NTSB case
- LAX07LA045
- 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
- 0 · 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
Nanchang CJ-6A
- Aircraft type
- Nanchang CJ-6
- 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
- N8181C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Falcon Field (FFZ), Mesa, 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
- Substantial
Cause areas
- Engine accessories › Failure
- Engine accessories › Seized
- Fuel system, pump › Inoperative
- Lubricating system, oil scavenge pump › Inoperative
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane experienced a loss of engine power and collided with a berm during a forced landing on a private airstrip. The pilot stated that during the flight he experienced problems with the engine's air compressor. Several minutes later he experienced a total loss of power. He opted to perform a forced landing at an abandoned airstrip. While on the landing roll, the airplane encountered a berm and the landing gear collapsed. The compressor and gearbox assembly were examined by a maintenance facility. The accessory gearbox had failed as a result of the air compressor piston seizing. The inhibited movement of the gearbox resulted in the failure of the oil pump, fuel pump, air compressor, and tachometer generator.
Probable cause
The total loss of engine power resulting from the failure of the engine's air compressor due to a seized piston, which resulted in the stoppage of the oil pump, fuel pump, and tachometer generator, in addition to the compressor. The underlying reason for the piston seizure and air compressor failure is undetermined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07LA045
- Event ID
- 20061206X01744
- Case number
- LAX07LA045
- 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: c342c72c0272c268e994a7c855b6e2c2eff3adf899a7dd49dedca6446e6b2980; retrieved 2026-09-22T04:12:46.144Z.