CEN14LA202 · Nanchang CJ6 - A
Nanchang CJ6 - A · Accident: aerodynamic stall/spin during an emergency descent
From Tuscola Area Airport (CFS) to Maple Grove Airport (65G)
Event
- NTSB case
- CEN14LA202
- 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
- Visual Meteorological Cond
Nanchang CJ6 - A
- Aircraft type
- Nanchang CJ6
- 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
- N594T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tuscola Area Airport (CFS), Caro, MITo Maple Grove Airport (65G), Fowlerville, MI
- Aircraft age
- About 31 years (built 1983)
- 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
- Emergency descent
- Defining eventThe 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
- Aerodynamic stall/spin
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot was conducting a personal cross-country flight with a pilot-rated passenger on board. A witness reported hearing the engine "sputter" and seeing the propeller slow as the airplane began descending toward an open field with the landing gear extended. Another witness, who was watching the airplane fly eastbound at low altitude, reported that it suddenly pitched down and impacted terrain in an approximate 45-degree, nose-down attitude, indicative of a stall. Based on the evidence, it is likely that the pilot was conducting a forced landing to the field due to a loss of engine power and subsequently failed to maintain adequate airspeed and exceeded the airplane's angle-of-attack, which resulted in the aerodynamic stall. An examination of the dry, flat field showed that it was an adequate emergency forced landing area.
A postaccident examination of the airframe, engine, and propeller revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. Weather conditions at the time of the accident were conducive to carburetor icing at glide and cruise power. Although the carburetor heat control was found in the "on" position, it is possible that the pilot delayed the application of carburetor heat, which likely resulted in the formation of carburetor ice and the loss of engine power.
An examination of damage to the airplane's structure showed that both the front seat and rear seat cockpit areas remained substantially intact and had provided a protective shell around both occupants during the crash sequence. Both pilot seats were equipped with a five-point lap belt and shoulder harness system. Evidence at the scene showed that the front seat pilot had been ejected from his seat during the crash sequence and had impacted the front cockpit instrument panel; however, he remained inside the cabin area. Examination of the front seat's lap belt and shoulder harness system latch, which was found unfastened, did not allow for a determination of whether the latch was unfastened, was fastened and failed, or whether it separated at the time of impact. The passenger in the rear seat remained restrained by his lap belt during the crash sequence; however, he impacted the rear cockpit instrument panel due to the failure and complete separation of his shoulder harness fitting. It is likely that the lack of adequate restraint for both occupants contributed to the severity of their injuries.
Probable cause
The pilot’s failure to maintain adequate airspeed during an off-airport forced landing after a loss of engine power due to carburetor icing and his exceedance of the airplane’s critical angle-of-attack, which resulted in an aerodynamic stall. Contributing to the accident was the pilot’s delayed application of carburetor heat while operating in conditions conducive to carburetor icing. Contributing to the severity of both occupants’ injuries was the lack of adequate restraint.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14LA202
- Event ID
- 20140419X00946
- Case number
- CEN14LA202
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 9e4f5656b5654c41cb4d7d5ca983476c4b7a33ada2cedffa289e2444b45adf41; retrieved 2026-09-14T16:13:18.943Z.