Chataqua Airlines Flight 4376
British Aerospace JETSTREAM 3101 JETSTREAM · Incident: near collision between aircraft while taxiing
From General Mitchell International Airport (MKE) to Indianapolis International Airport (IND)
Event
- NTSB case
- CHI00IA062
- 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
British Aerospace JETSTREAM 3101 JETSTREAM
- Aircraft type
- British Aerospace JETSTREAM 3101
- 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
- N842JS
- Operator
- Chataqua Airlines
- Onboard fatalities
- Unknown
- Route
- From General Mitchell International Airport (MKE)To Indianapolis International Airport (IND), Indianapolis, 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
- Taxi
- 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
- Flightcrew › Atc clearance, not followed
Approximate · Estimated position: the centre of Milwaukee, WI, the place the record names. Not the accident site.
NTSB narrative
After receiving a taxi clearance, which included holding short of runway 1L, the crew of Chataqua Flight 4376 proceeded to taxi across runway 1L, without clearance, resulting in a near collision with a departing Sun Country Boeing 727-200. The First Officer of Chataqua Flight 4376 reported that he was handling radio communications and had received the taxi clearance, which included the hold-short limitation, and read-back the clearance to ground control. According to the captain, contributing factors to the incident were crew fatigue, the cold temperature of the cockpit, and the windows being obscured with de-icing fluid.
Probable cause
the hold-short clearance not being followed by the flightcrew, which resulted in a near collision with the departing Boeing 727-200.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI00IA062
- Event ID
- 20001212X20331
- Case number
- CHI00IA062
- 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: 350a970b5e4cfe80eb12ffde056169eb58d367a15f371858722d0b213929d067; retrieved 2026-09-18T16:49:57.139Z.