Simmons Airlines Short Brothers SD360 incident
Short Brothers SD360 · Incident: near collision between aircraft during takeoff
From Chicago O'Hare International Airport (ORD) to South Bend International Airport (SBN)
Event
- NTSB case
- CHI89IA054
- 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 SD360
- Aircraft type
- Short Brothers SD360
- 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
- N366MQ
- Operator
- Simmons Airlines
- Onboard fatalities
- Unknown
- Route
- From Chicago O'Hare International Airport (ORD)To South Bend International Airport (SBN), South Bend, IN
- 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
- Takeoff · rejected takeoff
- 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
- Near collision between aircraft
- 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
- Pilot in command › Atc clearance, misread
Approximate · Estimated position: the centre of Chicago, IL, the place the record names. Not the accident site.
NTSB narrative
THE LOCAL CONTROLLER POSITIONED SIMMONS 4058 ON RWY 9L FIRST, AND THEN POSITIONED SIMMONS 4158 (THIS AIRPLANE) ON RWY 4L. HE THEN RETURNED TO SIMMONS 4058, STATED THE RWY NUMBER, & CLEARED IT FOR TAKEOFF. BEFORE SIMMONS 4058 HAD A CHANCE TO REPLY, SIMMONS 4158 (THIS AIRPLANE) ACKNOWLEDGED THE CLEARANCE. SIMMONS 4058 QUERIED THE CLEARANCE. REALIZING THE CONFUSION, AND SEEING SIMMONS 4158 (THIS AIRPLANE) MOVING, THE CONTROLLER CANCELED SIMMONS 4058 TAKEOFF CLEARANCE. SIMMONS 4058 REPLIED 'WE THOUGHT THAT WAS GONNA HAPPEN'. A PILOT 'SLOWDOWN' WAS TAKING PLACE AT THE TIME, AND THE CONTROLLERS STATED THAT PILOTS WERE TAXIING MORE SLOWLY THAN USUAL AND APPEARED TO GET LOST OR CONFUSED ON THE GROUND MORE OFTEN. THE CREW OF SIMMONS 4158 VEHEMENTLY DENIED PARTICIPATION IN THE UNION-RELATED WORK SLOWDOWN. THE SAFETY BOARD HAS ISSUED RECOMMENDATIONS ADDRESSING SIMILAR FLIGHT CALL SIGN CONFUSION.
Probable cause
THE PIC FOLLOWED A CLEARANCE INTENDED FOR ANOTHER AIRPLANE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI89IA054
- Event ID
- 20001213X27859
- Case number
- CHI89IA054
- 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: local date, investigation status, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1989-03-08.
- API snapshot SHA-256: 0d7002f4e1fe26627dc0907bef7ff639920610be896b42449422d4db6dd2cb2e; retrieved 2026-09-18T19:13:34.051Z.