Com Air Saab-Fairchild SF-340A incident
Saab-Fairchild SF-340A · Incident: airframe, component or system failure en route
From CVG · Cincinnati, OH to Toronto Pearson International Airport (YYZ)
Event
- NTSB case
- NYC92IA035
- 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
- Incident
- 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
- 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
- Charter & commuter
- 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
Saab-Fairchild SF-340A
- Aircraft type
- Saab Fairchild SF-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
- N146CA
- Operator
- Com Air
- Onboard fatalities
- Unknown
- Route
- From CVG · Cincinnati, OHTo Toronto Pearson International Airport (YYZ), Toronto
- 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 135: Air Taxi & Commuter
- 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 · descent
- 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
- Minor
Cause areas
- Manufacturer › Inadequate quality control
- Reduction gear assembly, propeller shaft › Failure, total
- Reduction gear assembly, propeller shaft › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLIGHT CREW DETECTED VIBRATION COMING FROM THE RIGHT PROPELLER AND MADE A DECISION TO SHUT THE ENGINE DOWN. DURING THE SHUTDOWN PROCESS THE PROPELLER SEPARATED FROM THE AIRPLANE. EXAMINATION OF BOTH PORTIONS OF THE FAILED PROPELLER SHAFT REVEALED THE SHAFT FAILED DUE TO FATIGUE. METALLURGICAL EXAMINATION FOUND A SLAG INCLUSION JUST BELOW THE FRACTURE SURFACE. THIS DEFECT OCCURRED DURING THE MELTING OF THE ORIGINAL INGOT.
Probable cause
A FATIGUE FRACTURE ON THE PROPELLER SHAFT, THAT ORIGINATED AT A SUBSURFACE SLAG INCLUSION, WHICH REMAINED IN THE MATERIAL USED TO MANUFACTURE THE SHAFT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC92IA035
- Event ID
- 20001212X18510
- Case number
- NYC92IA035
- 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: 4394ad60bf45d422f96734328e86a9a27ac07eae9a8efce0b29f71b97bed66ce; retrieved 2026-09-18T18:50:20.281Z.