FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Skyway Airlines Flight 1233

7 Jun 2003 · Milwaukee, WI, United States

Beech 1900D · Incident: airframe, component or system failure during initial climb

From General Mitchell International Airport (MKE) to Marquette Sawyer Regional Airport (SAW)

Report a problem

Event

NTSB case
CHI03IA153
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
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
Airline
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

Beech 1900D

Aircraft type
Beechcraft 1900
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
N901SK
Onboard fatalities
Unknown
Route
From General Mitchell International Airport (MKE), Milwaukee, WITo Marquette Sawyer Regional Airport (SAW), Gwinn, MI
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 121: Air Carrier
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
Initial climb
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

  • Flt control syst, aileron control › Failure

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The flight crew of the incident aircraft reported lateral control problems shortly after takeoff, noting that about 45 degrees of right control wheel deflection was required to maintain straight flight. They noted no other anomalies and seemed to have full flight control authority. However, as a precaution, the flight crew elected to return and land at the departure airport. The crew reported that the landing was normal with the exception of the required control wheel offset. A post incident examination of the aileron control system revealed a 360º fracture in the silver-brazed joint between the drive sprocket and its mating shaft of the left-hand aileron control sprocket assembly. The failure of the brazed joint allowed both control wheels to be rotated approximately 45 degrees from neutral without a corresponding aileron control surface response. NTSB metallurgical examination of the left-hand sprocket assembly revealed that it was not brazed according to the referenced specifications. Specifically, the examination noted that the braze filler material had been introduced from both ends of the joint, resulting in a lack of penetration of about 20 percent of the total joint area. The applicable specification states, "the filler metal shall be introduced at one edge...and shall flow by capillary action to fill the interstice." The NTSB's review of the incident aircraft's maintenance records showed that a flight data recorder (FDR) functional check was completed the night before the incident flight. The roll control parameter, which is designed to measure the aileron surface position, was one of the parameters checked. To verify the accuracy of this parameter, the left control wheel is rotated either clockwise or counterclockwise until the ailerons contact their respective up or down stops. When the stops are contacted, the control wheel is held in position and the FDR roll control parameter value is checked against an approved maintenance manual limit. The control wheel is then rotated in the opposite direction and the FDR parameter is verified. The mechanic who conducted the functional check reported that the FDR functional check was routine. NTSB analysis of available recorded FDR data, incident flight and over 83 flights before the incident flight, showed that the maximum values recorded for the FDR roll control parameter prior to the functional check were 14.6 degrees aileron trailing edge down (TED) and 23.4 degrees aileron trailing edge up (TEU). The recorded aileron TED value was not in the range required by the approved operators B1900D maintenance inspection procedures document. The analysis also showed that, during the FDR functional check, the maximum values recorded for the roll parameter exceeded the maximum values recorded prior to the incident by 1.9 degrees in the aileron TED direction and 1.0 degree in the aileron TEU direction. This was the only time that both FDR values for the roll control parameter were in the TED range required by the functional check. The aircraft manufacturer and the NTSB tested the aileron control system on an exemplar Beechcraft 1900D aircraft in Wichita. The purpose of the test was to determine the amount of tangential force, applied to the control wheel, required to change the FDR roll control parameter value by 1.9 degrees in the aileron TED direction. Results of the testing showed that an additional tangential force of 80 pounds applied to the control wheel, after it was rotated such that an aileron was resting against its control surface stop, increased the roll parameter value by 0.7 degrees in the aileron TED direction and 1.3 degrees aileron TEU. Additional force was not applied to the control wheel because the limit load for the aileron control system is 80.4 pounds. The airplane manufacturer provided a Beechcraft 1900D Engineering report that documented tests that were conducted on the aileron control system to demonstrate compliance with the Code of Federal Regulations. Test data show that the aileron system did not yield while applying a limit tangential load of 80.4 pounds to the control wheel or fail when an ultimate tangential load of 120.6 pounds was applied to the control wheel. The aileron control system, including the brazed joint on the sprocket assembly, met all Federal Aviation Administration airworthiness standards for commuter-category aircraft. The investigation concluded that the failed sprocket assembly significantly reduced the pilots' control of the ailerons because the failure affects pilot input from both control wheels.

Probable cause

Failure of the aileron sprocket assembly at the sprocket-to-shaft braze joint. Contributing factors were the improper braze procedure used by the part manufacturer at the time of fabrication which resulted in an inferior quality joint and the inadequate quality control (inspection) criteria which failed to identify the improperly brazed joint. An additional factor was the improper inspection procedure utilized by the operator's maintenance personnel, during which excessive force was applied to the control wheel in order to obtain acceptable flight data recorder readings during the functional check.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI03IA153
Event ID
20030609X00820
Case number
CHI03IA153
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: 5f94e70691827f9a2d673395ebd8c8800ff8b959a40b31dcf104b728c272259a; retrieved 2026-09-18T15:47:19.997Z.