SkyWest Airlines Bombardier Inc CL-600-2D24 incident
Bombardier Inc CL-600-2D24 · Incident: wrong surface or wrong airport during takeoff
From an unrecorded airport to Detroit Metropolitan Wayne County Airport (DTW)
Event
- NTSB case
- OPS25LA054
- 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
- Ongoing
- 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-2D24
- 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
- N833SK
- Operator
- SkyWest Airlines
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Detroit Metropolitan Wayne County Airport (DTW), Romulus, MI
- Aircraft age
- About 6 years (built 2019)
- 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
- 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
- Wrong surface or wrong airport
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On July 16, 2025, about 1542 eastern daylight time (EDT), SkyWest Airlines (SKW) flight 3751, a Bombardier CL-600-2D24, N833SK, departed from a closed runway at MBS International Airport (MBS), Freeland, Michigan. The flight continued without further incident to its intended destination of Detroit/Wayne County International Airport (DTW), Romulus, Michigan. The 2 flight crewmembers, 2 cabin crewmembers, and 61 passengers deplaned at the gate without any injuries. The flight was operated as a Title 14 Code of Federal Regulations Part 121 scheduled domestic passenger flight. The National Transportation Safety Board (NTSB) was notified by the Federal Aviation Administration (FAA) and, in response, began an incident investigation. History of Flight According to SKW, the incident flight’s dispatch release was 20 pages in length and indicated a departure time of 1533. The release also indicated an 18-minute taxi out at MBS and an estimated time of arrival at DTW of 1622. According to the captain, he flew in from DTW as a dead-heading crewmember and met the crew at the gate. Prior to departure the first officer, who was to be the pilot flying (PF), conducted the threat briefing. Both pilots discussed the storms in the vicinity and decided that if they received good takeoff data, they would perform the departure from runway 14 and that would keep them clear of the line of storms. The flight crew read the taxiway closures provided to them from the dispatcher with the flight release, and the captain highlighted the applicable ones on the airport diagram. The crew received the flight’s takeoff data for runway 14, and considering the potential for windshear, the crew agreed to use normal takeoff performance numbers. The MBS air traffic control tower (ATCT) was closed via a notice to airmen (NOTAM) at the time the flight was pushed back from the gate. After completing the engine start checklist, the first officer contacted Great Lakes approach control to obtain their air traffic control clearance to DTW. The flight crew reported they made the appropriate advisory transmissions on the MBS common traffic advisory frequency (CTAF) as they taxied to runway 14 via taxiway “C” and taxiway “A.” During the taxi out to runway 14 the crew reported there “were no visible cues indicating a closure of the taxiways or runways.” As the flight was holding short of runway 14, the first officer contacted Great Lakes approach control and informed the controller that they were number one at runway 14 and ready for departure. The controller issued the flight a release of “fly runway heading maintain 4,000.” The flight crew reported that “were no obstructions or airport personnel present” at the time of their departure. According to ADS-B data, the flight became airborne about 1542:39. The flight crew stated that the flight was uneventful and there was no indication they had departed from a closed runway. According to ADS-B data, the flight landed at DTW about 1607. A review of the NOTAMS for MBS revealed that there were 18 NOTAMs in effect at the time of the incident. One of the NOTAMS specified that runway 14/32 was closed from July 16, 2025, beginning at 0600 until July 16, 2025, at 1800. On page 14 of the flight’s dispatch release, under the section titled “Origin Airport NOTAMS,” the NOTAMs were broken down into six sections. Three of those sections were titled “Aerodrome/RWY/FICON NOTAMS,” “Taxiway and Airport Lighting NOTAMS,” “Radio/Communication NOTAMS.” There were five NOTAMS under “Aerodrome/RWY/FICON NOTAMS” section, which included the runway 14/32 closure NOTAM, five NOTAMS under the “Taxiway and Airport Light NOTAMS” section, and one NOTAM under the “Radio/Communication NOTAMS” section. Airport Information MBS was located about 9 miles to the northwest of Saginaw, Michigan at an elevation of 668.2 ft msl. The airport had two paved landing surfaces, 05/23 and 14/32. Runway 05/23 was 8,002 ft long and 150 ft wide. Runway 14/32 was 6,399 ft long and 150 ft wide. The FAA Chart Supplement provided that the MBS ATCT operated daily from 0700 until 0000. At the time of the incident, the ATCT was closed via NOTAM from July 16, 2025, at 0957 until July 16, 2025, at 2300. NOT FOR NAVIGATION
Figure 1: MBS Airport Diagram (Source: Jeppesen)
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record OPS25LA054
- Event ID
- 20250724200629
- Case number
- OPS25LA054
- 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: investigation status, coordinates, 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: 9293e1bae084dc0acdbd1f9088c830b6eec7a6fb9a541cc4aea16b46a89e22ca; retrieved 2026-09-16T20:08:08.252Z.