CHI99FA177 · Cessna 340A
Cessna 340A · Accident: airframe, component or system failure en route
From Chicago Executive Airport (PWK) to Pueblo Memorial Airport (PUB)
Event
- NTSB case
- CHI99FA177
- 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
- 0
- 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
Cessna 340A
- Aircraft type
- Cessna 340
- 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
- N1372G
- Operator
- Irwin P. Pochter · private individual
- Onboard fatalities
- Unknown
- Route
- From Chicago Executive Airport (PWK), Wheeling, ILTo Pueblo Memorial Airport (PUB), Pueblo, CO
- 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
- En route · cruise
- 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
- 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
- Tree(s)
- 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 › Airspeed, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight was executing a precautionary landing at the airport due to a reported fuel transfer problem. Witnesses described hearing engine variances and observed the aircraft roll and impact the ground nose first. There was a post crash fire mainly confined to the right wing area. Inspection of the flight control system, engines, and propellers did not reveal any pre-existing anomalies with these systems. The left fuel selector and left fuel pumps passed functional tests. The right fuel selector and right fuel pumps could not be tested due to fire damage.
Probable cause
the pilot not maintaining flying speed. Factors to the accident were the fuel transfer problem of unknown origin.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI99FA177
- Event ID
- 20001212X18928
- Case number
- CHI99FA177
- 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. 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: 5837fa12413b198832c431cf6686b1d40d8437e0a916bd0ab7cac9c84b23eaa9; retrieved 2026-09-20T22:03:46.726Z.