FTW93IA242 · Canadair CL-600-2B16 CL-600-2B1
Canadair CL-600-2B16 CL-600-2B1 · Incident: airframe, component or system failure en route
From ALN · Alton, MO to an unrecorded destination
Event
- NTSB case
- FTW93IA242
- 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
- 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
Canadair CL-600-2B16 CL-600-2B1
- Aircraft type
- Canadair CL-600
- 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
- N392PT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From ALN · Alton, MOTo 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
- 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
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Flt control syst, rudder control › Fractured
- Flt control syst, rudder control › Stress corrosion
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE CREW EXPERIENCED AN UNCOMMANDED YAW TO THE RIGHT WHILE IN CRUISE FLIGHT AT FL410 WITH THE AUTO PILOT ENGAGED. A NORMAL LANDING WAS MADE WITHOUT INCIDENT AT THE INTENDED DESTINATION. EXAMINATION OF THE AIRPLANE'S RUDDER CONTROL REVEALED THAT THE SHAFT PORTION OF THE RUDDER QUADRANT WAS FRACTURED. METALLURGICAL EVALUATION OF THE FRACTURED SURFACE REVEALED THAT THE SEPARATION OF THE SHAFT PORTION WAS THE RESULT OF STRESS CORROSION CRACKING THAT INITIATED FROM OPPOSITE SIDES OF THE SHAFT AND PROGRESSED INWARD UNTIL ABOUT 60% OF THE SHAFT CROSS SECTION CRACKED DUE TO POOR CHOICE OF MATERIAL, IMPROPER RADIUS, AND EXCESSIVE TORQUE ON THE SHAFT NUT.
Probable cause
THE FRACTURE OF THE RUDDER QUADRANT DUE TO STRESS CORROSION. A FACTOR WAS THE MANUFACTURER'S IMPROPER SELECTION OF MATERIAL.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW93IA242
- Event ID
- 20001211X13141
- Case number
- FTW93IA242
- 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, damage. 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: d39f785777b03584fe34267dcd24b80f6db748055acf44c5f0bd87e4f83d53fc; retrieved 2026-09-23T01:44:21.364Z.