FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Air Wisconsin Airlines Flight 6181

1 Feb 2025 · Chicago, IL, United States

Bombardier Inc CL-600-2B19 · Accident: ground collision while taxiing

From Kalamazoo/Battle Creek International Airport (AZO) to an unrecorded destination

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
DCA25LA120
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
Accident
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
Event fatalities
Unknown
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

Bombardier Inc CL-600-2B19

Aircraft type
Bombardier 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
N420AW
Onboard fatalities
Unknown
Route Possible conflict
From Kalamazoo/Battle Creek International Airport (AZO), Kalamozoo, MITo not recorded
Aircraft age
About 23 years (built 2002)
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 · from runway
Defining eventThe 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
Ground collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

A serious injury was sustained by a tug driver following a collision with the left wing of Air Wisconsin flight 6181, a CRJ-200, during taxi operations at Chicago O’Hare International Airport (ORD). No injuries were reported among the airplane’s crew or passengers. Night visual meteorological conditions (VMC) prevailed at the time of the accident.

Flight 6181 landed at ORD and was initially held at the B Pad for an open gate (see Figure 1). Once cleared, the aircraft proceeded southbound on Taxiway A under a standard clearance. The first officer was actively monitoring both ramp and ground control frequencies during the taxi.

The captain reported first observing the tug on Taxiway B as the tug began crossing at the access road. The tug appeared to be slowing down suggesting an intent to stop. The captain could not recall whether the tug’s headlights were illuminated and believed he saw the vehicle using ambient lighting.

After briefly diverting attention toward the gate area, the captain looked back and recognized an imminent collision with the tug. Braking was initiated immediately by the captain, but the impact occurred shortly thereafter. The captain described the impact as “not that bad” and believed the tug had struck the wingtip. The flight crew then communicated with the flight attendants, followed by dispatch via the Aircraft Communications Addressing and Reporting System (ACARS).

According to the tug driver, while returning from the international terminal, the vehicle approached the service road leading to the L gates. Before entering the road and crossing taxiway B, the tug came to a complete stop at the designated stop sign and the driver observed an airplane taxiing outbound on Taxiway B. The driver checked both directions and waited until the outbound aircraft cleared the taxiway. The driver also verified that no aircraft were approaching from behind or the opposite direction before proceeding to cross the taxiways (A&B).

The driver stated that as the tug was crossing the taxiways, the left wing of flight 6181, approaching on taxiway A, was not visible until the last moment, leaving insufficient time to react. He also noted the absence of a nose-gear light on flight 6181, which may have contributed to the tug driver not detecting the presence of flight 6181 before the collision.

Figure 1. Ground position tracks for flight 6181 with respect to taxiways A & B.

The collision resulted in the tug overturning and trapping the driver, leading to serious injury. Post-flight inspection revealed substantial damage to the leading-edge front spar of the airplane’s left wing. The tug driver emphasized that had he been aware of the airplane’s presence, he would not have entered the intersection.

Figure 2. Damage to the aircraft (Source FAA).

Figure 3. Damage to the tug (Source FAA).

According to the Chicago Department of Aviation (CDA) ground motor vehicle operating regulations manual, dated August 2023, a driver must stop prior to initiating the crossing of the taxiways A, B, and V to determine if the crossing could be accomplished without stopping in the islands between the taxiways. Vehicles on service roads must yield to vehicles crossing taxiways.

Probable cause

The tug driver’s failure to ensure the taxiway was clear of aircraft prior to crossing, resulting in a collision with the left wing of the taxiing aircraft. Contributing to the accident was the limited visibility of the aircraft due to ambient lighting conditions and the absence of the aircraft’s nose-gear light, which reduced the tug driver’s ability to detect the aircraft’s presence in time to avoid the collision.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA25LA120
Event ID
20250207199663
Case number
DCA25LA120
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2025-02-02.
  • API snapshot SHA-256: 16ccfc72c697d858d3f2044fd0aafd499db6456aac2fa7261ed51165d6f55395; retrieved 2026-09-16T19:38:46.413Z.