Simmons Airlines Short Brothers SD3-60 incident
Short Brothers SD3-60 · Incident: airframe, component or system failure on approach
From Chicago O'Hare International Airport (ORD) to Dane County Regional Truax Field (MSN)
Event
- NTSB case
- CHI88IA129
- 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
- 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
Short Brothers SD3-60
- Aircraft type
- Short Brothers SD3
- 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
- N383MQ
- Operator
- Simmons Airlines
- Onboard fatalities
- Unknown
- Route
- From Chicago O'Hare International Airport (ORD), Chicago, ILTo Dane County Regional Truax Field (MSN), Madison, WI
- 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
- Approach · IFR initial approach
- 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, wing flap control cable/rod › Chafed
- Manufacturer › Inadequate surveillance, insufficient staff
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE ON A STABILIZED FINAL APPROACH, THE PILOT EXPERIENCED AN UNCOMMANDED RIGHT ROLL WHEN THE FLAP SETTING WAS INCREASED FROM FIVE TO FIFTEEN DEGREES. THE CONDITION WAS ALLEVIATED WHEN THE FLAPS WERE RESET TO FIVE DEGREES. POST FLIGHT INSPECTION REVEALED THAT THE RIGHT OUTBOARD FLAP POSITION SIGNALLING CABLE HAD FAILED. INSPECTION OF THE OPERATOR'S FLEET FOUND TWO ADDITIONAL AIRCRAFT WITH CHAFFED/FRAYED FLAP POSITION SIGNALLING CABLES. ALL CHAFFED/FRAYED CABLES WERE INSTALLED ON AIRCRAFT WHICH THE OPERATOR HAD PURCHASED AS A SERIES. ON THIS SERIES OF AIRCRAFT THE FLAPS AND CONTROL RIGGING WERE INSTALLED BY THE VENDOR WHICH MANUFACTURES THE WINGS, RATHER THAN THE MANUFACTURER OF THE AIRFRAME, AS IS NORMALLY THE CASE.
Probable cause
FAILURE OF THE RIGHT OUTBOARD FLAP POSITION SIGNALLING CABLE DUE TO CHAFFING INITIATED BY IMPROPER INSTALLATION/RIGGING BY A MANUFACTURER'S VENDOR.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI88IA129
- Event ID
- 20001213X25894
- Case number
- CHI88IA129
- 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: 17f5a7a6218dc1126cd9600587965cd9f3669fdcf4c2a698c17b9109671cb73b; retrieved 2026-09-18T19:21:34.173Z.